IntuneSettingCatalogCustomPolicyWindows10: RoleScopeTagIds are set to "Default"

[adrian-haeusser]

Description of the issue

Hello,

I was asked to open a new issue specifically for the resource IntuneSettingCatalogCustomPolicyWindows10 relating to the issue described in #6727, as there is already an existing Pull Request for the other resources within that issue.

The issue regarding the IntuneRoleScopeTag always being set to "Default" (ID = 0) seems to persist for this resource as well when using M365DSC to create new or updating existing resources. There is also no drift reported under ParametersNotInDesiredState in the Event Log either, despite the deviation.

Microsoft 365 DSC Version

V1.25.1203.2

Which workloads are affected

Intune

The DSC configuration

IntuneSettingCatalogCustomPolicyWindows10 'Example'
        {
            Description           = "";
            Ensure                = "Present";
            Name                  = "Setting Catalog Test";
            Platforms             = "windows10";
            RoleScopeTagIds       = @("1");
            Technologies          = "mdm";

            ApplicationID = "";
            TenantID = "";
            CertificateThumbprint = "";
        }

Verbose logs showing the problem

Environment Information + PowerShell Version

PSVersion: 5.1.17763.8024

[FabienTschanz]

Tested this with the changes from the PR and I was able to successfully deploy and update custom policies without issues.