Use our best practices to test bulk UPN changes. If the userPrincipalName attribute value doesn't correspond to a verified domain in Azure AD, synchronization replaces the suffix with. When you synchronize user accounts from Active Directory to Azure AD, ensure the UPNs in Active Directory map to verified domains in Azure AD. Learn more: Add your custom domain name using the Azure portal.įor example, if you add and change the user UPNs and email to reflect that, the result is: a process for when you update a User Principal Name (UPN) of a user, or for your organization. If you create the user account in the domain, the default UPN is: However, you can add more UPN suffixes by using Active Directory domains and trusts. In most cases, you register this domain name as the enterprise domain. In Active Directory, the default UPN suffix is the domain DNS name where you created the user account. During initial synchronization from Active Directory to Azure AD, ensure user emails are identical to their UPNs. becomes recommend you change user UPN when their primary email address changes.Therefore, change user UPN when their primary email address changes. Sign-in pages often prompt users to enter an email address, when the value is their UPN.
It addresses UPN-change planning, and recovering from issues that might result from changes.įor developers, we recommend you use the user objectID as the immutable identifier, rather than UPN or email addresses. This article assumes the UPN is the user identifier.
0 kommentar(er)
