We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When generating a delta between source and destination for the AADGroup resource, assigned licenses do not seem to be evaluated properly.
1.24.131.2
Azure Active Directory
AADGroup "AADGroup-Users" { AssignedLicenses = @(MSFT_AADGroupLicense { DisabledPlans = @() SkuId = 'ENTERPRISEPREMIUM' } MSFT_AADGroupLicense { DisabledPlans = @() SkuId = 'EMSPREMIUM' } MSFT_AADGroupLicense { DisabledPlans = @() SkuId = 'POWER_BI_STANDARD' }
AADGroup "AADGroup-Users" { AssignedLicenses = @(MSFT_AADGroupLicense { DisabledPlans = @() SkuId = 'ENTERPRISEPREMIUM' } MSFT_AADGroupLicense { DisabledPlans = @() SkuId = 'EMSPREMIUM' }
I would expect the delta to show the missing POWER_BI_STANDARD license only. But instead it doesn't match the ENTERPRISEPREMIUM.
POWER_BI_STANDARD
ENTERPRISEPREMIUM
### Verbose logs showing the problem _No response_ ### Environment Information + PowerShell Version _No response_
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
Thanks for the additional information. This looks like some sorting needs to be added to the compare function.
Successfully merging a pull request may close this issue.
Description of the issue
When generating a delta between source and destination for the AADGroup resource, assigned licenses do not seem to be evaluated properly.
Microsoft 365 DSC Version
1.24.131.2
Which workloads are affected
Azure Active Directory
The DSC configuration
Source
Destination
I would expect the delta to show the missing
POWER_BI_STANDARD
license only. But instead it doesn't match theENTERPRISEPREMIUM
.The text was updated successfully, but these errors were encountered: