Several modules have Managedidentity instead of ManagedIdentity

[fxlite]

Details of the scenario you tried and the problem that is occurring

E.g. EXOOrganizationConfig, but this occurs in several of the EXO resources.

Verbose logs showing the problem

Suggested solution to the issue

For example, Line 1184 in MSFT_EXOOrganizationConfig.psm1 contains:

$SetValues.Remove('Managedidentity') | Out-Null

Which should be:

$SetValues.Remove('ManagedIdentity') | Out-Null

Due to hashtable keys being case sensitive, this does not remove ManagedIdentity from the splat on Line 1196, and the Set-TargetResource fails with "A parameter cannot be found that matches parameter name 'ManagedIdentity'."

The DSC configuration that is used to reproduce the issue (as detailed as possible)

Start-DSCConfiguration -Path <pathToCompilledEXOOrganizationConfigMOF> -Wait -Force

The operating system the target node is running

Version of the DSC module that was used ('dev' if using current dev branch)

1.22.1026.1

[mlhickey]

Hashtable keys are case-insensitive, the issue is more likely that it's not being correctly passed to begin with. Will try to investigate this resource over the weekend/early next week,

[andikrueger]

@mlhickey thanks for the further investigation.

I marked my current PR as draft.

[fxlite]

Thanks for the input. This is a good resource regarding case sensitivity in hashtables, depending on how they're initialized. I figured this was relevant, as when I altered the module myself, the parameter error disappeared...

[fxlite]

Yeah, but the hashtable isn't getting initialized literally like you have the module unless I'm mistaken. For example:

[mlhickey]

I agree if they were being created that way, but here they are not. In this case it's being copied from $PSBoundParameters at line 1691:

$ValuesToCheck = $PSBoundParameters

Function to test against PSBoundParameters seems to bear out case-insensitivity:

Regardless, it was a typo on my part and should be rationalized regardless for sake of good coding.

@andikrueger - assume you did a case-sensitive search/replace across all resources and not just the EXO?