Active Directory Migration: Fundamentals Pt 5 — userPrincipalName suffix considerations
Change is never easy, but with proper planning and execution, it can be smoother. userPrincipalName (UPN) changes are no different. In this blog post, we will discuss the importance of UPN suffixes, benefits of UPN matching user email address, changing a UPN, as well as adding a UPN suffix. We will also present the relationship between the userPrincipalName suffix and the M365 Tenet as well as provide tips for common issues when UPN names are changed.
What is a userPrincipalName?
The userPrincipalName is an Internet-style login name for a user based on the Internet standard RFC 822. The UPN consists of the user’s logon name plus “@” plus the domain name where the user account resides. This gives the user a unique identity within their domain.
For example, the userPrincipalName “prince@contoso.com” would refer to the Active Directory user account for Prince. Prince’s sAMAccountName may be “Prince” and his email address may be “prince@contoso.com”.
As you can see, in most implementations, the userPrincipalName will match the email address.
The userPrincipalName may be used to sign in to on-premises as well as cloud-based services.
