Every SharePoint site and OneDrive account in a Microsoft 365 tenant sits under one onmicrosoft.com domain: contoso.sharepoint.com, contoso-my.sharepoint.com, and so on. Adding a second onmicrosoft.com domain to the tenant, which happens routinely after a rebrand or a tenant-to-tenant migration, doesn’t touch that URL prefix automatically. You have to change SharePoint domain assignment deliberately, and it’s a PowerShell operation, not a toggle in the admin center.
It’s also disruptive by design: new sites and OneDrive accounts get blocked while it runs, existing ones may be briefly unreachable, and for most tenants it’s something you get to do exactly once.
What Actually Changes, and What Doesn’t
Renaming updates SharePoint and OneDrive URLs only. Email addresses, user principal names, Microsoft Entra ID display names, and individual site collection paths beneath the domain are untouched. If the actual goal is changing how users sign in or what their email looks like, this cmdlet isn’t the tool. That’s a separate domain and UPN change entirely.
Old URLs don’t die immediately after the switch. Microsoft redirects the previous SharePoint and OneDrive URLs to the new domain for one year, which is enough runway to update hardcoded links in scripts, bookmarks, and third-party integrations without a hard cutover.
Confirm You’re Eligible First
A few conditions rule this out before you get anywhere near the PowerShell cmdlet:
- GCC, GCC High, and DoD tenants can’t use this feature at all, regardless of size.
- Multi-geo tenants aren’t eligible for a standard rename.
- Standard rename tops out at 10,000 total sites: SharePoint sites, OneDrive accounts, and SharePoint Embedded containers combined. Past that, you need Advanced Tenant Rename, covered below.
- It’s a one-time operation on the standard tier. There’s no repeating this every time the organization renames itself again.
- The management shell needs Windows PowerShell 5.1, not PowerShell 7, and it doesn’t run on macOS. Cross-platform admins have flagged this repeatedly as a real gap, and there’s no workaround beyond running it from a Windows machine.
Add the New onmicrosoft.com Domain
- Sign in to the Microsoft 365 admin center.
- Go to Settings > Domains, then select your existing onmicrosoft.com domain.
- Under Overview, select Add onmicrosoft.com domain, type the new domain name, and confirm.
A tenant can hold up to five onmicrosoft.com domains total, and a domain you add here can’t be removed afterward, so double-check the spelling before confirming. Leave the fallback domain setting alone at this point; switching it before the rename completes isn’t part of the supported sequence, and it’s easy to fix at the very end instead.
Schedule the Rename
This is the step that actually changes the SharePoint domain. Everything before it was setup, and everything after it is verification. It runs through the SharePoint Online Management Shell, installed separately from Microsoft Graph PowerShell:
Install-Module -Name Microsoft.Online.SharePoint.PowerShell
Connect-SPOService -Url "https://sysarticle-admin.sharepoint.com"Code language: JavaScript (javascript)Scheduling requires at least 24 hours’ lead time, and Microsoft recommends picking a genuinely low-traffic window, a weekend rather than just an off-peak weekday hour, since new site and OneDrive creation is blocked tenant-wide for the duration:
$scheduledDateTime = (Get-Date).AddHours(25)
Start-SPOTenantRename -DomainName "mysysarticle" -ScheduledDateTime $scheduledDateTime -Confirm:$falseCode language: PHP (php)Expect the job itself to take anywhere from several hours to a few days once it starts, scaling with how many sites and OneDrive accounts the tenant actually has. This isn’t something to schedule the night before a go-live and assume will finish by morning.
Advanced Tenant Rename for Larger Tenants
Tenant rename went generally available with no site count ceiling in October 2025, splitting into two tiers. Standard rename is what’s described above, capped at 10,000 sites. Advanced Tenant Rename removes that cap entirely, but it requires a SharePoint Advanced Management (SAM) license assigned to every user in the tenant, not just the admin running the command.
The advantage beyond scale: Advanced Tenant Rename lets you prioritize up to 4,000 sites for earlier processing, so the sites people actually need first thing Monday morning aren’t waiting behind tens of thousands of others in the queue.
Set-SPOTenantRenameSitePrioritization -SiteUrl "https://sysarticle.sharepoint.com/sites/finance"
Get-SPOTenantRenameSitePrioritizationCode language: JavaScript (javascript)Prioritization only works after the rename has already been scheduled with Start-SPOTenantRename, and the window to adjust it closes two hours before the scheduled start. Plan the priority list before you schedule, not after.
Check Status and Set the New Fallback Domain
Get-SPOTenantRenameStatusThis returns a job status of Queued, In Progress, or Success, along with counts of sites renamed versus still pending. Waiting for a clean Success rather than assuming it finished overnight matters here; checking too early just means reading a Queued or In Progress status and drawing the wrong conclusion from it.
Once status shows Success and you’ve spot-checked a few OneDrive and SharePoint links for the new domain, go back to Settings > Domains, select the new onmicrosoft.com domain, and set it as the fallback domain from its Overview tab. This is the step the source guidance and Microsoft’s own documentation both stress doing last, not alongside adding the domain. Setting it as fallback too early isn’t part of the tested sequence.
References
Microsoft: Change Your SharePoint Domain Name https://learn.microsoft.com/en-us/sharepoint/change-your-sharepoint-domain-name
Microsoft: Start-SPOTenantRename (Microsoft.Online.SharePoint.PowerShell) https://learn.microsoft.com/en-us/powershell/module/microsoft.online.sharepoint.powershell/start-spotenantrename
Microsoft: Set-SPOTenantRenameSitePrioritization https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenantrenamesiteprioritization
Learn more: Microsoft 365 Intune Remote Help Now Supports Unattended Windows Access
