Services
Summary
SharePoint Online Tenant Rename is now generally available for tenants with up to 500K sites, allowing domain name changes during rebranding or mergers. It ensures high reliability, business continuity, and compatibility with Microsoft 365 apps, but excludes vanity domains, Multi-Geo, and tenants over 500K sites.
Details
Introduction
Organizations undergoing rebranding, mergers, acquisitions, divestitures, or tenant consolidations often need their SharePoint domain name in URLs to reflect their new identity. The SharePoint Online (SPO) Tenant Rename feature enables this change. We are announcing General Availability (GA) of Advanced Tenant Rename for tenants with up to 500K SharePoint sites, expanding support beyond the previous 100K site limit.
When this will happen
General Availability (Worldwide): We began rolling out in mid-August 2025 and expect to complete by early September 2025.
This feature will be generally available worldwide starting September 1, 2025.
How this affects your organization
This update allows rename support for tenants with up to 500K total SharePoint sites. It maintains high reliability across rename operations and ensures business-as-usual continuity during and after the rename. It is compatible with top Microsoft 365 partner scenarios such as Microsoft Teams and PowerApps.
Key capabilities include:
- Rename support for tenants with up to 500K total sites.
- High reliability maintained across rename operations.
- Business-as-usual (BAU) continuity ensured during and after rename.
- Compatibility with top Microsoft 365 partner scenarios (Teams, PowerApps, etc.).
- Enhanced telemetry to monitor rename operations and identify issues quickly.
Please note the following limitations for this release:
- Tenant rename for vanity domains is not supported.
- Tenant rename for Multi-Geo customers is not supported.
- Tenant rename for customers with more than 500K sites is not supported.
What you can do to prepare
Admins should:
- Confirm their tenant’s total site count using the SharePoint admin center (SPAC) or PowerShell before scheduling.
- Review unsupported features or limitations (such as Hub site limitations, vanity domains, or third-party integrations).
- Communicate any impact to site owners based on public documentation.
- Validate custom scripts, PowerShell automations, and integrations that rely on the old domain name.
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.