company rebrand IT dependencies and service impact
Hello Experts,
My client is looking to rename their company and is planning to implement a change in the windows internal domain name.
Can you please look at plan below and advise on following items?
What is the service impact of approach below?
What are the pros and cons ?
Are there any other dependencies or services that might be affected by this change? DNS, Firewall, apps,
At which point there is cutover?
Any other advice or best practices to follow approach below?
Approach to be followed:
You simply add the UPN suffix using AD Domains and Trusts (if you have multiple domains, you have to do this in the forest root).
You can use Powershell to change the UPN suffix on all users if you have a lot of them.
If you already have Email in the O365 and are hybrid, make the UPN suffix match the email domain.
It should already be a domain in Exchange and an accepted domain in Office 365.
ASKER
ASKER
Like a said before, yes they have Azure AD connect to sync users/groups to the cloud. All email is hosted in MS365.
Basically, this is the required change:
Change the name of the email domain in MS365 to something else, and have the users to use this new email address. users will keep old email domain address for archiving purposes but new email domain will be the authoritative email for them.
Change the displayed UPN when users log into their domain. they want to connect using new upn domain/username or newupn@username format
Your thoughts?
Insofar as business impact - I don't know the business and wouldn't care to comment. But LOTS of applications are dependent on the UPN and/or primary email address. You have to evaluate each of them.