Some MSPs use their corporate tenant as the source of truth for policies. However, when these policies are reassigned back to the corporate tenant, they are recreated instead of being recognized as existing. This leads to a poor user experience, as the MSP must manually identify which version of the policy is being synced.
Prevent configuration, compliance, and conditional access policies from duplicating when assignments are made to the source tenant. (Completed)
Great idea, Hugo!
Are you thinking of some kind of conflict/duplicate recognition (i.e. “I've noticed you have a policy that's named the same, do you want to update or replace the existing policy?” or are you thinking we need to get more granular and look at the name first and then the policy settings to prevent duplicates?
The latter. Something like this - if the policy is deployed to the source tenant, skip republishing.
We're working on an improvement that allows you to easily distinct the source policy from the published policy in this exact scenario.
Very exciting! Thanks, Gido. 🙂
Please sign in to leave a comment.
Comments (4 comments)