💡 Our Technical Review in summary
Microsoft is expanding the SharePoint Online (SPO) Tenant Rename feature to support larger organizations. Previously limited to 100,000 sites, the General Availability (GA) release now allows tenants with up to 500,000 SharePoint sites to change their domain name (e.g., changing prefix.sharepoint.com). This update is specifically designed for large-scale organizations undergoing rebranding, mergers, acquisitions, or divestitures that require their digital identity to match their corporate identity.
#### Impact
- Increased Scalability: Organizations with complex environments can now rename their SharePoint domain if their total site count is 500,000 or fewer.
- Business Continuity: The process is designed to maintain high reliability and “business-as-usual” operations during and after the rename, with minimal disruption to end-users.
- Service Compatibility: The rename process is compatible with core Microsoft 365 services, including Microsoft Teams and PowerApps.
- Technical Limitations: This update does not support tenants with more than 500K sites, Multi-Geo environments, or the use of vanity domains.
- Monitoring: Enhanced telemetry is included to allow IT admins to track the progress of the rename and troubleshoot potential issues in real-time.
#### Action Required
- Verify Site Inventory: Use the SharePoint Admin Center or PowerShell to confirm that the total site count is below the 500,000 threshold before attempting a rename.
- Audit Customizations: Review all custom scripts, PowerShell automations, and third-party integrations for hardcoded URLs that rely on the current domain name.
- Review Documentation: Consult the official Microsoft “Change your SharePoint domain” guide to understand specific limitations regarding Hub sites and third-party app behavior.
- Communication Plan: Draft a communication strategy for site owners and end-users to inform them of the upcoming URL changes and any potential (though minimal) sync disruptions.
- Testing: If applicable, validate the rename process in a test/sandbox tenant environment before applying changes to the production tenant.
Microsoft Official Update
Service: N/A
Category: stayInformed
Severity: normal
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.
Learn more: Change your SharePoint domains | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.
