Setting up and managing device configurations using Intune
Based on the documented Cloud Policy behavior, Not configured in a higher-priority policy does not provide a supported exemption from a lower-priority policy that configures the setting.
Key points:
- Cloud Policy uses priority when conflicting policy settings exist The documented rule is that if a user is a member of multiple Microsoft Entra groups with conflicting policy settings, the highest priority setting is applied, where 0 is the highest priority.
- The documentation only describes precedence for conflicting configured settings It does not state that a higher-priority policy with Not configured suppresses a lower-priority configured value.
- Tenant scope is a valid Cloud Policy scope
The Cloud Policy audit schema defines these scopes:
- Tenant = applies to all users in the tenant
- User = applies to users in configured Microsoft Entra groups
- What the observed behavior indicates In the described test, the tenant policy is configured and the user-scoped policy is Not configured for that setting. The tenant value continues to apply and Outlook remains locked. That behavior is consistent with the available documentation because there is no documented exclusion model where Not configured in a user policy cancels a configured tenant policy.
- Changing priority is unlikely to create an exception Setting the user-scoped policy to Priority 0 and the tenant policy to Priority 1 would only help if the user-scoped policy had a conflicting configured value. Since this setting exposes only Enabled and Not configured, there is no documented opposite value to override the tenant configuration.
- Supported exception mechanism for this setting is not documented No provided documentation describes a supported way to exempt specific users from a tenant-scoped Microsoft 365 Apps Cloud Policy for a setting that only offers Enabled and Not configured.
- Why the setting is locked on some devices
Cloud Policy settings are written under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Cloud\Office\16.0and take precedence over Group Policy, preference settings, and locally applied policy settings. That explains the greyed-out Outlook UI when the policy is applied.
For the specific questions:
- Does Not Configured in a User-scoped Cloud Policy allow evaluation to continue to the lower-priority Tenant policy?
The documented behavior and the observed result indicate yes for this scenario: the lower-priority tenant policy still applies when the higher-priority user policy is Not configured. - If the User policy is Priority 0 and Tenant is Priority 1, would the User policy suppress the Tenant setting?
Not based on documented behavior. With only Enabled and Not configured available, there is no documented conflicting value that would override the tenant setting. - Is there a supported way to provide exceptions for specific users while keeping the Tenant policy as default?
No supported exception method is described in the provided documentation for this setting. - Has anyone successfully implemented an exclusion/override scenario for this setting?
No such supported implementation is described in the provided documentation. - Is there a supported way to exempt specific users when the setting only supports Enabled and Not Configured?
No documented supported way is provided.