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
Now that IntuneSettingCatalogCustomPolicyWindows10 is finally working with ConvertTo-DSCObject I was able to test it, and found a small problem when getting it through my internal tests which is when the export is done the ResourceInstanceName ends up with the Id instead of its Name like most other policies (which use DisplayName instead of Name as key and therefore show up correctly).
The issue is with the order of the conditions in the function Get-M365DSCExportContentForResource and fixing this is just a matter of hoisting the condition looking for the key Name right to just before the condition for the key Id.
Description of the issue
Now that IntuneSettingCatalogCustomPolicyWindows10 is finally working with ConvertTo-DSCObject I was able to test it, and found a small problem when getting it through my internal tests which is when the export is done the ResourceInstanceName ends up with the Id instead of its Name like most other policies (which use DisplayName instead of Name as key and therefore show up correctly).
The issue is with the order of the conditions in the function Get-M365DSCExportContentForResource and fixing this is just a matter of hoisting the condition looking for the key Name right to just before the condition for the key Id.
Microsoft 365 DSC Version
1.24.207.2
Which workloads are affected
other
The DSC configuration
Verbose logs showing the problem
N/A
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: