Changing the MDM user scope is not controlled by the Intune Administrator role itself but by tenant‑level configuration and licensing.
From the available information:
- An MDM authority must be set before MDM user scope can be used. This tenant already has MDM authority = Microsoft Intune, so that prerequisite is satisfied.
- Auto‑enrollment behavior is then controlled by the MDM user scope and MAM user scope settings. These determine which users can enroll devices and whether devices are MDM‑enrolled or only managed by MAM/Windows Information Protection.
When the MDM user scope controls are greyed out even for an Intune Administrator, it indicates that the tenant‑wide enrollment configuration is locked at the directory level rather than by Intune RBAC. In this state, only higher‑privileged directory roles (for example, those that can change Microsoft Entra auto‑enrollment and tenant‑wide device settings) can modify the MDM user scope.
To resolve the issue, have a directory admin with sufficient tenant permissions review and update the Windows automatic enrollment settings so that:
- The correct users have a valid Intune license assigned.
- The MDM user scope is set to All or Some (with the appropriate group) in the automatic enrollment configuration.
- The MAM user scope is set appropriately (for example, None for education/corporate scenarios where full MDM enrollment is required).
Once a directory admin updates these tenant‑level enrollment settings, the MDM user scope options will no longer be greyed out for that configuration page, and Intune Administrator can then manage enrollment behavior through policy.
References: