A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
A “full tenant name change” can mean two different things in Microsoft 365, and they are very different in scope and impact:
- Changing the SharePoint/OneDrive domain name (technical URL change)
- Changing the tenant display name (cosmetic name shown in portals)
Only the first one (SharePoint domain rename) is covered in the provided material, so the focus is on that and how it differs from a display-name-only change.
1. SharePoint domain name change
This changes the *.sharepoint.com and *.sharepoint.com-related URLs that SharePoint and OneDrive use. Example:
- Before:
https://contoso.sharepoint.comandhttps://contoso-my.sharepoint.com - After:
https://fabrikam.sharepoint.comandhttps://fabrikam-my.sharepoint.com
Key characteristics:
- It is a URL/domain-level change for SharePoint and OneDrive only.
- It does not change email addresses or the initial
contoso.onmicrosoft.comtenant name. - It is performed using PowerShell and a scheduled rename operation.
- When the rename starts, all sites in the tenant are queued for individual renames; each site is temporarily inaccessible while its URL is being changed.
- A redirect is created at the old address for each site and remains in place for 1 year after the rename.
- The feature is:
- Available in a standard version for tenants with ≤ 10,000 total sites (SharePoint sites, OneDrive accounts, and SharePoint Embedded containers combined).
- Available via Advanced Tenant Rename (part of SharePoint Advanced Management) for tenants with any number of sites, with the ability to prioritize up to 4,000 sites for early execution.
Important constraints and limitations:
- The domain rename feature isn’t available if:
- The organization has Multi-Geo configured now or in the past.
- The organization uses special/government clouds (GCC, GCC High, DoD, etc.).
- The tenant has a historical .de German cloud domain.
- The SharePoint domain is a vanity domain like
teams.contoso.cominstead ofcontoso.sharepoint.com. - The tenant still has alternate URLs, BPOS sites, old SharePoint public sites, or vanity domain configurations.
- Locked sites/OneDrive (LockState = NoAccess) cannot be renamed; locks must be removed first.
- Deleted sites cannot be restored after the domain change; they should be restored beforehand if needed.
- Point-in-time restore to a time before the domain change is not possible.
- Root site replacement (via admin center or
Invoke-SPOSiteSwap) is blocked between scheduling and completion of the rename. - Licensing, admin role, and storage changes do not take effect during the rename; they must wait until after completion.
- The tenant can be renamed only once via this feature. Changing back to the original SharePoint domain is not supported. If additional renames are required, a support request must be submitted using the “Rename a SharePoint Tenant more than once” path.
- Each redirect site consumes 0.15 MB of storage; the tenant must have at least
0.15 MB × number of sitesavailable before renaming.
Advanced Tenant Rename specifics:
- Required when:
- There are more than 10,000 sites, or
- More control over execution order is needed.
- Prerequisites:
- SharePoint Advanced Management licenses must be purchased for all users in the organization.
- No Microsoft 365 Multi-Geo.
- Not using government clouds (GCC, GCC High, DoD).
- Not using vanity domains from earlier MTE offerings.
- Allows prioritizing up to 4,000 sites (SharePoint and OneDrive, excluding root sites) for early execution using PowerShell cmdlets:
-
Set-SPOTenantRenameSitePrioritization– mark specific sites for early rename. -
Remove-SPOTenantRenameSitePrioritization– remove that prioritization.
-
Error codes and scheduling rules (for SharePoint domain rename):
- Rename must be scheduled at least 24 hours in the future and within 30 days; otherwise error code 775 is returned.
- Multi-Geo tenants get error 776 (not supported).
- Tenants with public sites get error 777 until public sites are removed.
- If the tenant exceeds the maximum allowed number of sites, error 780 is returned.
- If the tenant has already been renamed once, error 783 is returned.
2. Tenant display name change
A tenant display name change is a cosmetic change of the organization’s name as shown in portals and some UI surfaces. Based on the provided context, the mechanics of changing the display name itself are not described, but the key distinction is:
- A display name change does not change:
- The
*.onmicrosoft.cominitial domain. - The
*.sharepoint.comor*.sharepoint.comURLs. - Email domains.
- The
- It is generally reversible and can be updated multiple times, unlike the SharePoint domain rename which is effectively one-time.
Summary of differences
| Aspect | SharePoint domain name change | Tenant display name change |
|---|---|---|
| Scope | SharePoint and OneDrive URLs (*.sharepoint.com) |
Organization name shown in UI/portals |
| Impact | Technical URL change, temporary site inaccessibility, redirects created | Cosmetic only; URLs and domains unchanged |
| Availability | Not available for Multi-Geo, special clouds, .de, vanity domains, etc. | Generally available; not constrained by SharePoint domain rules |
| Reversibility | One-time; cannot revert to original domain | Can typically be changed again |
| Tools | PowerShell + SharePoint admin; may require Advanced Tenant Rename | Admin portal settings (not detailed in context) |
| Data/restore impact | No point-in-time restore before rename; deleted sites can’t be restored after | No such impact described |
For a “full tenant name change” in the sense of rebranding:
- A display name change updates how the organization name appears.
- A SharePoint domain rename updates SharePoint/OneDrive URLs and is a separate, more complex, one-time operation with strict prerequisites and limitations.
References: