Use Non-Routable Domains with Microsoft 365 and Azure AD Connect
Question details
Plan Microsoft 365 sign-in identities for an organization that uses a non-routable internal domain.

- Product
- Microsoft 365, Microsoft Entra Connect Sync (formerly Azure AD Connect), and AD FS
- Device & OS
- not provided
- Scenario
- The organization uses an internal domain such as .loc and wants to synchronize identities for Microsoft 365 sign-in.
- Observed behavior
- The desired configuration uses a verified, routable domain suffix for cloud sign-in while retaining the internal domain where appropriate.
Identify the internal AD domain, current user principal name (UPN) suffixes, and a public domain your organization controls. Check whether the environment uses AD FS, multiple forests, or custom sign-in mappings before changing user identities.
Use a Verified Public Domain Suffix for Microsoft 365 Sign-In
Use this approach to plan cloud sign-in names without necessarily renaming the internal AD domain.
A non-routable suffix such as .loc cannot be verified as a public Microsoft 365 domain. The internal AD domain name and users' sign-in UPN suffixes can be different.
Changing UPNs can affect existing sign-ins and applications. Validate the synchronization and federation design before making changes, especially in multi-forest or AD FS environments.
In the Microsoft 365 admin center, go to Settings > Domains and select Add domain. Follow the verification prompts to add the requested DNS record for a domain your organization controls.
Open Active Directory Domains and Trusts, right-click Active Directory Domains and Trusts, and select Properties. Add the verified public domain under Alternative UPN suffixes.
In Active Directory Users and Computers, open a pilot user's Properties > Account and review the User logon name suffix. Coordinate any change to the verified suffix with your identity administrator and assess application dependencies first.
Review the UPN mapping in Microsoft Entra Connect Sync and test the pilot account's synchronized identity and Microsoft 365 sign-in. If AD FS is in use, validate the federation configuration before applying changes broadly.

Review Complex Hybrid Identity Designs with Microsoft Administrators
Use expert guidance when trusts, multiple forests, custom mappings, or AD FS make the sign-in design environment-specific.
Work with Office Files in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface and support for common Office formats, making it easy to move document work from Microsoft Office. It does not configure Microsoft 365 identity synchronization or AD FS.

Frequently Asked Questions
Do I have to rename my internal .loc domain?
Not necessarily. You can retain the internal AD domain and add a verified public domain as an alternative UPN suffix in Active Directory Domains and Trusts.
Can I use a .loc suffix for Microsoft 365 sign-in?
A .loc suffix is not a verifiable public Microsoft 365 domain. Plan sign-in names with a public domain that you control and verify under Settings > Domains in the Microsoft 365 admin center.
Does adding a UPN suffix change existing user accounts?
No. Adding an alternative suffix makes it available for selection; it does not automatically update users. Review each planned change in Active Directory Users and Computers and assess its effects before rollout.
What should I check if the organization uses AD FS?
Review the federation configuration and Microsoft Entra Connect Sync UPN mapping before changing sign-in names. Test a pilot identity and consult Microsoft documentation or an experienced identity administrator.




