The SharePoint Online domain name is not always what you want it to be. This can be because a fantasy name was used when the Microsoft 365 tenant was created, or the organization has a new name in the meantime. Renaming this SharePoint domain was not possible for a long time. The private preview started in spring (2021), but was limited. Now renaming is available in public preview. That's why I decided to change my initial, inappropriate name and documented my approach and experiences here.
Table of Contents
- Add onMicrosoft domain
- Rename SharePoint domain via Azure AD
- Rename a SharePoint domain with PowerShell
- Possible problems
Add onMicrosoft domain
First you have to add a new onMicrosoft in the Azure AD to use the prefix of this later as a SharePoint subdomain. To do this, we navigate with the link https://aka.ms/SPORenameAddDomain in the Azure AD in the Custom domain names.
Attention: With this link it should be possible in the future to adjust the domain name without PowerShell.
- Here we add the desired new domain and immediately receive feedback as to whether it is still available:
Rename SharePoint domain via Azure AD
- Once the domain is added, we open it.
- Here is the link Configure initial domain displayed. To do this, navigate to the link mentioned above.
- In my case, that didn't work yet.
Rename a SharePoint domain with PowerShell
With PowerShell, we can rename the domain relatively easily. The prerequisite is the SharePoint Online module, which can be used with the command
Install-Module –Name Microsoft.Online.SharePoint.PowerShell
can be installed.
The order must begin at least 24 hours after creation and may be a maximum of 30 days in the future.
- I issued the following commands in my case:
(The time zone is UTC)
Code language: PowerShell (powershell)
Connect-SPOService -url https://xxxxxxx-admin.sharepoint.com/ Start-SPOTenantRename -DomainName scloudwork -ScheduledDateTime 2021-12-18T23:00
- We can see the renaming status
Microsoft provides the possible restrictions in its Docs, divided into the categories "Low impact", "Medium impact" and "High impact".
SharePoint Domain rename - Limitations
In my test, most of it worked without any problems and user complaints (family works in the tenant). For me, there were only three points that could have an impact on support costs.
- Power BI datasets (SharePoint Lists) can no longer be synchronized.
Solution: Update the connection to Power BI Desktop, the comparison takes place automatically.
- Recently opened items (Lists, SharePoint, OneNote) no longer work and have to be opened once via the new URL.
- OneDrive links from SharePoint do not work on the mobile devices even after 72 hours.
Below are the error messages. I was able to solve the problem by deleting and re-adding the link. (It works normally in Windows.)
the OneDrive Sync Admin Report allows to centrally monitor possible problems at the users. In my case, however, no errors appeared here.
The SharePoint domain could be renamed with little initial effort. The user impact is also relatively small for such a change. It is also nice that the old URL continues to work with a redirect.
The biggest limitations or potential sources of user queries and thus support costs are the links and recently opened elements that no longer work. From my point of view, this results in the greatest risk that someone will make further edits in the "old" OneNote and not notice that it is no longer synchronized. In the worst case, this could lead to data loss.
Despite the possible errors or limitations, renaming can add value to organizations. I can quickly think of a handful of customers who, for historical reasons, have a wrong company name or one with a strange suffix.