logo
search
Others

How to Fix SharePoint Domain Rename Errors 757 and 758

Maira MehtabMaira Mehtab Sep 27, 2026 869 views

Question details

The user is attempting to rename a SharePoint domain but encounters PowerShell errors -757 and -758, despite the target domain appearing as verified in the admin tenant.

Product
Microsoft SharePoint
Device & OS
not provided
Scenario
Executing a SharePoint domain rename operation using PowerShell in a Microsoft 365 environment.
Observed behavior
The domain rename process fails, returning error -757 (domain unverified) and error -758 (unsupported characters) even when the domain is already marked as verified in the tenant.
Before you start

Ensure you are logged in with Global Administrator or SharePoint Administrator privileges before checking domain configurations or submitting support tickets in the Microsoft 365 admin center.

Solution 1Recommended

Verify Domain Name Formatting and Submit a Microsoft Support Ticket

Use this solution to rule out simple formatting issues and escalate backend synchronization errors directly to Microsoft Support.

These specific PowerShell errors during a SharePoint domain rename often stem from strict domain naming requirements or backend verification delays within Microsoft 365. Error -758 specifically points to syntax issues, while Error -757 points to verification status.

1
Inspect the Domain for Invalid Characters

Carefully review the target domain name for Error -758. Ensure it does not contain any spaces, hyphens, or other unsupported special characters.

2
Check Verification Status

For Error -757, log into the Microsoft 365 admin center, navigate to Settings > Domains, and confirm the target domain is listed as 'Verified'.

3
Create a Service Request

If the domain name is properly formatted and already verified but the errors persist, navigate to 'Support' > 'Help & support' in the Microsoft 365 admin center. Open a new support ticket requesting a backend investigation for the SharePoint domain rename failure.

Tenant Synchronization Delay: Newly verified domains can sometimes take up to 24 hours to fully synchronize across all Microsoft 365 services. If you recently verified the domain, consider waiting a day before reattempting the rename.
Free Microsoft Office alternative

Enhance Your Productivity with WPS Office

While waiting for Microsoft Support to resolve your SharePoint domain issues, consider using WPS Office for your daily document needs. It is a free, lightweight, and highly compatible alternative to Microsoft Office, ensuring your workflow remains uninterrupted.

  1. 1. Download the Installer: Visit the official WPS Office website and click 'Download WPS Office Free'.
  2. 2. Install WPS Office: Run the downloaded setup file and follow the on-screen instructions to install the application on your computer.
  3. 3. Open Your Documents: Launch WPS Office to immediately open, edit, and save your existing Microsoft Office files without formatting loss.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight installation with fast startup times, minimizing system resource usage.Highly familiar user interface, allowing for a seamless transition with zero learning curve.Built-in PDF editing tools for easy document conversions and annotations.
QA img-9

Frequently Asked Questions

What does SharePoint Error -757 mean?

Error -757 indicates that the target domain is not recognized as verified by the SharePoint backend system, which can happen due to synchronization delays even if it appears verified in the Microsoft 365 admin center.

Why am I getting Error -758 when renaming a SharePoint domain?

Error -758 occurs when the target domain name contains unsupported formatting, such as spaces, hyphens, or other special characters that SharePoint does not accept.

How long does a SharePoint domain rename process take?

Once successfully initiated via PowerShell without errors, the renaming process can take anywhere from a few hours to over 24 hours to complete, depending on the size of your tenant and the number of sites.