Microsoft 365 Message Center Archive

MC1173930 - Microsoft SharePoint and OneDrive: General availability of tenant rename with no scale limitations

Message ID

MC1173930

View in Message Center

Service

SharePoint Online
Microsoft OneDrive

Published

Oct 16, 2025

Tag

Feature update
User impact
Admin impact

Summary

SharePoint Online Tenant Rename is now generally available without site count limits, enabling domain name changes for all tenants starting October 16, 2025. It supports business continuity, Microsoft 365 integrations, and requires SAM licenses for tenants with over 10,000 sites. Vanity domains and Multi-Geo are unsupported.

More information

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 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.