Forum Discussion
Query Regarding Changing UPN and Email Address with new Domain Name in Exchange Hybrid Environment
Hi Microsoft Tech Community, I'm currently navigating a transition within my organization where we need to change the UPN and Email Address while retaining the old email address as a secondary ad...
Hi,
I think my query was incomplete previously and hence I just edited the Discussion. Actually, our plan is to change the domain name itself. Hence at that time, I think we need to recreate the Outlook Profile and all other Microsoft Teams, OneDrive application as well. I need the confirmation on it.
I think my query was incomplete previously and hence I just edited the Discussion. Actually, our plan is to change the domain name itself. Hence at that time, I think we need to recreate the Outlook Profile and all other Microsoft Teams, OneDrive application as well. I need the confirmation on it.
You'll need to explain the scenario a bit more....Renaming a domain is a pretty big step for not a lot of gain when you can just add an additional UPN suffix and additional SMTP address to Exchange. If that's the way you go, then all the comments above still apply.
I've not ever heard of anyone renaming an AD domain when AAD Connect has been deployed, so that would be interesting.
I've not ever heard of anyone renaming an AD domain when AAD Connect has been deployed, so that would be interesting.
- Hi,
I am writing to seek guidance on minimizing the impact on user end during an upcoming domain change within our Exchange Hybrid environment. Currently, our setup comprises an AD Server, AD Connect, Exchange On-Prem Server, and Exchange Online.
Here are the key details of our environment and the changes planned:
We are operating in an Exchange Hybrid environment with an existing AD Server, AD Connect, Exchange On-Prem Server, and Exchange Online.
While the domain in our AD Server remains unchanged, we are undergoing changes in Username, Email, SMTP address, and M365 Tenant Name due to organizational ownership alterations.
Our internal domain structure is straightforward and not directly correlated with the organization name.
The organization name change will also entail a modification in our public domain.
There has been no migration of the AD Server; however, we will be changing the UPN domain, Email Address prefix, and SMTP address prefix.
Given these circumstances, I am seeking advice on the best approach to execute this transition with minimal impact on the end-user experience. Specifically, I am concerned about the implications for Outlook Profiles, Teams Profiles, OneDrive profiles, and the accessibility of OneDrive/SharePoint shared link URLs.
I would greatly appreciate your expertise and recommendations on the most effective strategy to manage this transition while ensuring a seamless experience for our users.
Thank you in advance for your assistance and insights.- If you're not renaming your on-premises AD, then all the comments above apply. It's as simple as adding an additional UPN suffix to your on prem AD, add and verify the additional domain in your M365 tenant, reconfiguring your users in on-prem AD with the new UPN and primary SMTP addresses, and letting AAD Connect sync the changes through to Entra/EXO. It's a good idea to test/pilot the process with before you do it for everyone.
