You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I added support for excluding resources on Assert-M365DSCBlueprint, New-M365DSCDeltaReport and Compare-M365DSCConfigurations on #3262 I missed that I was only excluding them from the source (tenant) but not from the destination (blueprint) which means that if a certain policy was in both the source and destination, and then excluded in one of the cmdlets mentioned above, it would still appear as a drift that it was missing from the source and present in the destination. Check drift below where I have a policy of type IntuneDeviceConfigurationCustomPolicyWindows10 in both tenant and blueprint and by excluding it then it appears as drift.
The fix is to check if there are any resources to be excluded then exclude them from both source and destination.
The text was updated successfully, but these errors were encountered:
ricmestre
changed the title
Assert-M365DSCBlueprint: ExcludeResources parameter not working as it should
Compare-M365DSCConfigurations: ExcludeResources parameter not working as it should
Dec 5, 2023
ricmestre
changed the title
Compare-M365DSCConfigurations: ExcludeResources parameter not working as it should
Compare-M365DSCConfigurations: ExcludedResources parameter not working as it should
Dec 5, 2023
Description of the issue
When I added support for excluding resources on Assert-M365DSCBlueprint, New-M365DSCDeltaReport and Compare-M365DSCConfigurations on #3262 I missed that I was only excluding them from the source (tenant) but not from the destination (blueprint) which means that if a certain policy was in both the source and destination, and then excluded in one of the cmdlets mentioned above, it would still appear as a drift that it was missing from the source and present in the destination. Check drift below where I have a policy of type IntuneDeviceConfigurationCustomPolicyWindows10 in both tenant and blueprint and by excluding it then it appears as drift.
The fix is to check if there are any resources to be excluded then exclude them from both source and destination.
Microsoft 365 DSC Version
1.23.1129.1
Which workloads are affected
other
The DSC configuration
N/A
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: