The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
Dear @Rick
Yes, it is possible to move forward with Microsoft Entra ID without creating a new domain. The NETBIOS name itself is typically not a blocker for Entra ID integration. What is most important is that users have a routable, verified UPN suffix (for example, username with the domain @company.com) that matches a domain verified in Entra ID. For reference: Microsoft Entra UserPrincipalName population and Plan and troubleshoot UserPrincipalName changes in Microsoft Entra ID
Exchange Server 2019 on-premises can also coexist with Entra ID synchronization and hybrid configurations without requiring a domain rebuild, provided the Active Directory and Exchange environments are healthy and the UPN configuration is aligned with the verified domain in Entra ID.
Before considering a domain migration, it would be helpful to verify:
- The Active Directory DNS domain name
- The NETBIOS name
- The UPN suffix currently assigned to users
- Whether that UPN suffix is verified in Entra ID
I hope the information shared is helpful. If you have any questions, please feel free to reach out. I'm looking forward to your update.
If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in the documentation to enable e-mail notifications if you want to receive the related email notification for this thread.