Microsoft SharePoint and OneDrive: General availability of tenant rename with no scale limitations
Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.
Rollout
- Ends
- 15 Nov 2026
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
- Microsoft's start date
- 16 Oct 2025
- Last changed by Microsoft
- 16 Oct 2025
- First seen here
- 19 Oct 2026
- Versions seen
- 1
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedOrganizations undergoing rebranding, mergers, acquisitions, divestitures, or tenant consolidations often need their SharePoint domain name in URLs to reflect their new identity. The SharePoint Online Tenant Rename feature enables this change. We are announcing general availability of advanced tenant rename with no site count limitation. With this update, the feature is now accessible to all customers, regardless of the total number of sites in the tenant.
When this will happen
General availability begins worldwide on October 16, 2025. Rollout started in early October and is expected to complete by mid-October 2025.
How this affects your organization
- Who is affected: Admins managing SharePoint Online and OneDrive for Business tenants globally.
- What will happen:
- Rename support is now available for all Microsoft 365 tenants, regardless of site count.
- High reliability is maintained across rename operations.
- Business-as-usual continuity is ensured during and after rename.
- Compatible with Microsoft 365 partner scenarios including Microsoft Teams and PowerApps.
- Not supported for vanity domains or Multi-Geo customers.
What you can do to prepare
- Confirm total site count using the SharePoint admin center (SPAC) or PowerShell before scheduling.
- Licensing requirement: Tenants with site count greater than 10,000 must have SAM licenses purchased for all users in the organization.
- Review unsupported features or limitations (such as Hub site limitations, vanity domains, third-party integrations).
- Communicate any impact to site owners using public documentation.
- Validate custom scripts, PowerShell automations, and integrations that rely on the old domain name.
- Learn more: Change your SharePoint domain name | Microsoft Learn
Compliance considerations
No compliance considerations identified, review as appropriate for your organization.
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.