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
I'll start by saying great effort on having PR #3990 merged so thank you @NikCharlebois for merging and @MKlingner to create the PR, it solved almost all issues with this resource but also because there seems to be some kind of issue in the Intune backend that automatically, but not always and not on all of my tenants, makes the old template used by IntuneASRRulesPolicyWindows10 to turn itself into the new template which is then used by IntuneSettingCatalogASRRulesPolicyWindows10. This is some weird combo happening in the Intune backend, so not a problem with my code or M365DSC's, which I really don't want to pursue on investigating by opening a ticket since what I really want is to use the newest template, in this case IntuneSettingCatalogASRRulesPolicyWindows10.
@NikCharlebois With that being said there's still a couple of problems here to be ironed out that should have been caught by the integration tests, that's why I was so keen on having them in place, I'll send out a PR to fix these in a bit.
Removing the resource won't work if Identity comes from another tenant, that param might not even be present in the blueprint since it's not required anymore
If Identity doesn't match, again if it comes from another tenant or not present in blueprint, then Test-DSCConfiguration will always report that resource is not in desired state even if it is so that param must be removed from the checks
Description of the issue
I'll start by saying great effort on having PR #3990 merged so thank you @NikCharlebois for merging and @MKlingner to create the PR, it solved almost all issues with this resource but also because there seems to be some kind of issue in the Intune backend that automatically, but not always and not on all of my tenants, makes the old template used by IntuneASRRulesPolicyWindows10 to turn itself into the new template which is then used by IntuneSettingCatalogASRRulesPolicyWindows10. This is some weird combo happening in the Intune backend, so not a problem with my code or M365DSC's, which I really don't want to pursue on investigating by opening a ticket since what I really want is to use the newest template, in this case IntuneSettingCatalogASRRulesPolicyWindows10.
@NikCharlebois With that being said there's still a couple of problems here to be ironed out that should have been caught by the integration tests, that's why I was so keen on having them in place, I'll send out a PR to fix these in a bit.
Microsoft 365 DSC Version
1.23.207.1
Which workloads are affected
other
The DSC configuration
N/A
Verbose logs showing the problem
N/A
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: