Confirm domain name requirements with System Center Configuration Manager and Microsoft Intune
Applies to: System Center Configuration Manager (Current Branch)
If necessary, take the following steps to satisfy any dependencies external to Configuration Manager:
Each user must have an Intune license assigned to enroll devices. To associate Intune licenses to users, each user must have a user principal name (UPN) that can be publicly resolved (for example, firstname.lastname@example.org) or an alternate login ID configured in Azure Active Directory. Configuring an alternate login ID allows users to sign in with an email address, for example, even if their UPN is in a NetBIOS format (for example, CONTOSO\johndoe).
- If your company uses publicly resolvable UPNs (i.e. email@example.com), no further configuration is required.
- If your company uses a non-resolvable UPN (i.e. CONTOSO\johndoe), you must configure an alternate ID in Azure Active Directory.
Deploy and configure Active Directory Federation Services (AD FS). (Optional)
When you set up single sign-on, your users can sign in with their corporate credentials to access the services in Intune.
For more information, see the following topics:
Deploy and configure directory synchronization.
Directory synchronization lets you populate Intune with synchronized user accounts. The synchronized user accounts and security groups are added to Intune. Failure to enable Directory Synchronization is a common cause of devices not being able to enroll when setting up Configuration Manager MDM with Microsoft Intune.
For more information, see Directory integration in the Active Directory documentation library.
Optional, not recommended: If you are not using Active Directory Federation Services, reset users' Microsoft Online passwords.
If you are not using AD FS, you must set a Microsoft Online password for each user.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.