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
IntuneDeviceConfigurationScepCertificatePolicyWindows10 works without issues within the boundaries of the same tenant, it can be exported, deleted, redeployed and updated, nevertheless it won't work applying to another tenant and that's because it expects a property called RootCertificateId which is assigned with the Id of a policy of type IntuneDeviceConfigurationTrustedCertificatePolicyWindows10 and of course the target tenant will have different Ids for these policies.
In order to fix this the policy should also have a RootCertificateDisplayName property to which to fallback in case RootCertificateId is not found and therefore try to find the policy by its name instead of the Id.
Description of the issue
IntuneDeviceConfigurationScepCertificatePolicyWindows10 works without issues within the boundaries of the same tenant, it can be exported, deleted, redeployed and updated, nevertheless it won't work applying to another tenant and that's because it expects a property called RootCertificateId which is assigned with the Id of a policy of type IntuneDeviceConfigurationTrustedCertificatePolicyWindows10 and of course the target tenant will have different Ids for these policies.
In order to fix this the policy should also have a RootCertificateDisplayName property to which to fallback in case RootCertificateId is not found and therefore try to find the policy by its name instead of the Id.
Microsoft 365 DSC Version
1.23.1122.1
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: