Forum Discussion
Impacts of changing default domain in Office 365 tenancy?
In addition to the accurate answers from jcgonzalezmartin, you should know that MS is working a tenant renaming process for this scenario. One of my customers has received some preliminary information about the program. As you can imagine, there are a lot of potential issues, your questions 4 and 5 are just the beginning. I have no idea when this will become widely available, but I would guess that it will be sometime this year.
Deletedmay be able to provide some more details.
- DeletedAug 15, 2018
Thanks for the add Dean_Gross - yes, we've looked into this extensively for six+ months.
I've been focusing on the impacts to SharePoint/OneDrive, while others in my IT department are focusing on AD/Exchange/Skype.
My first suggestion: contact Microsoft support. Microsoft has a process that they are currently refining to allow a tenant to change names. Most organizations will find changing the tenant name to be disruptive, especially large and change sensitive cultures like my company - so don't underestimate the effort.
In fact, changing the SharePoint/OneDrive URLs was too disruptive for us, so we're going to wait until next year to see if Microsoft has a better process.
In the meantime, we've added our new domain as our primary SMTP address, but left the UPN and SIP set to the old address. This can be confusing to users because almost all login prompts ask them to enter their "email address" when the prompt is actually for their UPN. We haven't had but a few calls about this since we added the email addresses a few months ago.
We're currently testing the UPN change, which will change the URL of the user's OneDrive site (among other things). Changing that address will break things like:
- OneNote notebooks that are open in the OneNote desktop app - users will need to notice that their notebooks are no longer syncing.
- Office recently used documents list - the links to recently used documents that are stored in OneDrive will break, because the links will continue to point to the old address. Our testing shows that this isn't 100% of the time, but we haven't tracked down why some users are reporting that their links continue to work.
- Office Pro Plus login issues - I don't have the details here, but some of our people have had trouble with the Office apps not being able to login (if I remember correctly)
- Bookmarks/favorites/etc. - any links that someone saves, including the sharing emails they receive, will no longer work. The permissions are left untouched, but the link in the original sharing email will no longer work.
One of the good things is the OneDrive desktop app - it will "heal" itself after a logout/reboot and doesn't require the user to do anything.
We've decided to proceed with the UPN change because we need to minimize the amount of time that our UPNs don't match what our users consider to be their email addresses. Plus, changing the OneDrive sites won't be as bad as SharePoint because most of our sharing/active documents are in SharePoint. Lastly - we can implement the UPN change over time, giving our help desk more time to deal with issues. When we do the full name change, including changing the base address for SharePoint Online and OneDrive, we'll have to do that in one step and incur a high call volume for help desk.
- Swapnil2091991Feb 05, 2020Copper Contributor
We have done the domain change successfully, all our users are using new domain on all applications. The only problem I am facing is that we are unableto retrive old domain mail boxes sync to 100%.
Inbox does not show previous mails wheras sent items are showing all mails.
Can you help me on this?
- Shane HallJan 31, 2019Copper Contributor
DeletedWe are looking at similar options with our domains. Have you encountered 3rd party utilities that would assist in migrating tenant to tenant?
- DeletedFeb 01, 2019
After my post in August, we found more issues with changing the UPNs for existing user accounts. Given the amount of pain this would have inflicted on our end users, the decision was made to wait for Microsoft to come up with a better process for renaming the tenant/UPNs.
I haven't looked into 3rd party options.