Others

Fix SharePoint Online Tenant Rename Error -757 with Exchange Domain

Anum MushtaqAnum Mushtaq Oct 14, 2026 869 views

Question details

The user is trying to rename a SharePoint Online tenant but encounters error -757 because the target domain is already bound to Exchange Online.

How to Resolve SharePoint Online Tenant Rename Error -757
Product
SharePoint Online
Device & OS
not provided
Scenario
Attempting to change the SharePoint Online tenant name using an onmicrosoft.com custom domain.
Observed behavior
The tenant rename process is rejected and fails with error -757 due to an existing Exchange Online domain association.
Before you start

Ensure you have Global Administrator privileges in your Microsoft 365 tenant and carefully review Microsoft's official prerequisites for renaming a SharePoint domain before proceeding.

Solution 1Recommended

Verify Domain Eligibility and Consult Microsoft Support

SharePoint tenant renaming has strict prerequisites. A domain currently utilized by Exchange Online is often blocked from being used as the new SharePoint tenant name.

When you attempt to rename your SharePoint Online tenant to a new onmicrosoft.com domain, Microsoft's backend system checks for existing associations. If the domain is already actively routing mail or associated with Exchange Online, the system automatically rejects the rename operation with error -757 to prevent severe routing and data conflicts.

1
Check current domain usage

Log into the Microsoft 365 Admin Center, navigate to 'Settings', and then 'Domains'. Check if your target onmicrosoft.com domain is currently bound to Exchange Online services.

2
Review Microsoft prerequisites

Consult the latest Microsoft documentation regarding SharePoint tenant renames to confirm whether your specific domain routing configuration is supported for a rename operation.

3
Contact Microsoft Support

Because domain unbinding and tenant renaming involve backend infrastructure, open a support ticket in the Microsoft 365 Admin Center or post in the Microsoft Q&A SharePoint community for specialized technical assistance.

Verify Domain Eligibility and Consult Microsoft Support
Support Limitation: Tenant renaming and onmicrosoft.com domain management are backend Microsoft 365 infrastructure tasks that require Microsoft support intervention and cannot be bypassed via client-side settings.
Free Microsoft Office alternative

Discover a Lightweight, Free Office Alternative

While complex tenant server issues require Microsoft Admin support, your everyday document workflows shouldn't be interrupted. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office, letting you create, edit, and share files effortlessly without relying on complex cloud infrastructures.

  1. 1. Download WPS Office: Visit the official WPS website and download the free installer for your operating system.
  2. 2. Install the Software: Run the installer and follow the simple on-screen instructions to complete the setup in minutes.
  3. 3. Open Your Documents: Launch WPS Office and instantly open your existing Office files with full formatting intact.
Seamlessly open and edit documents downloaded from SharePoint or Exchange Online without format loss.Strict format compatibility with Microsoft Word, Excel, and PowerPoint (.docx, .xlsx, .pptx).Lightweight installation that consumes minimal system resources for fast performance.Built-in PDF editing, merging, and conversion tools completely free of charge.
microsoft office alternative - wps office

Frequently Asked Questions

Can I use the same custom domain for both Exchange Online and SharePoint Online?

Yes, standard custom domains (like yourcompany.com) can typically be used for both Exchange email and SharePoint sites. However, the foundational 'onmicrosoft.com' routing domain has stricter architectural rules during a tenant rename, which often triggers error -757 if it is already tied to Exchange.

What exactly is SharePoint error -757?

Error -757 occurs during the SharePoint Online tenant rename process when the system detects that the target onmicrosoft.com domain name is already strongly associated with another service (usually Exchange Online), preventing the required backend reassignment.

How long does a standard SharePoint tenant rename take?

Once successfully initiated without errors, a SharePoint tenant rename can take anywhere from a few hours to several days to complete, depending largely on the total number of sites, OneDrive accounts, and files in your Microsoft 365 environment.