Others

How to Resolve a SharePoint Domain Used by Another Tenant

Anum MushtaqAnum Mushtaq Oct 23, 2026 869 views

Question details

The user needs to associate a custom SharePoint or onmicrosoft.com domain with a new Microsoft 365 tenant, but the domain is locked to an older, restricted tenant.

How to Resolve a SharePoint Domain Used by Another Tenant
Product
Microsoft 365
Device & OS
not provided
Scenario
Setting up a new Microsoft 365 environment and attempting to add an existing domain for email and SharePoint use.
Observed behavior
The system prevents the domain from being added, displaying an error that it is already associated with another restricted or inaccessible tenant.
Before you start

Ensure you have Global Administrator credentials for your new Microsoft 365 tenant and gather valid proof of domain ownership (such as DNS registrar access) before contacting support.

Solution 1Recommended

Open a Service Request with Microsoft Support

This is the most direct method when an old tenant is restricted or inaccessible, requiring Microsoft Support to escalate and manually release the domain.

Because the old tenant is restricted, you will not have the necessary permissions to log in and remove the domain manually. Microsoft Support has specialized escalation paths to verify your domain ownership and forcefully detach it from the old tenant.

1
Log in to the Admin Center

Sign in to the Microsoft 365 Admin Center using the Global Administrator credentials for your new tenant.

2
Navigate to Support

On the left-hand navigation menu, click on 'Support' and then select 'New service request'.

3
Detail the issue

Explain that your domain is tied to an old, restricted tenant that cannot be accessed or deleted, and you need it released for your new tenant.

4
Provide proof of ownership

Work with the assigned support agent to provide DNS TXT records or other requested documentation to prove you own the domain so they can begin the escalation process.

Open a Service Request with Microsoft Support
Support Escalation: Only Microsoft Data Protection or specialized backend support teams can force-remove a domain from a restricted tenant you no longer control.
Free Microsoft Office alternative

Maintain Document Productivity with WPS Office

While resolving Microsoft 365 administration and tenant domain issues can take days, your team's document productivity shouldn't stall. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office for creating, editing, and sharing documents seamlessly during your tenant migration.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installation file for your operating system.
  2. 2. Install the Software: Run the installer and follow the quick on-screen instructions to set up WPS Office on your computer.
  3. 3. Start Creating: Open WPS Office and immediately start working on your existing Word, Excel, and PowerPoint files without formatting issues.
Fully compatible with Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight installation with a familiar UI, minimizing downtime during tenant migrations.Built-in PDF editing tools for comprehensive document management.Free to use, significantly reducing software licensing overhead.
QA img-9

Frequently Asked Questions

Why am I getting an error that my domain is used by another tenant?

This error occurs because the domain you are trying to add is still actively registered in Microsoft's systems to a previous Microsoft 365 or Azure AD tenant. A custom domain can only be associated with one tenant at a time.

How long does it take to free up a domain after deleting an old tenant?

Once an old tenant directory is successfully deleted, it can take up to three days for Microsoft's backend systems to completely release the domain so it can be verified in a new tenant.

Can I force-remove a domain if the old tenant is restricted?

You cannot do this manually. If the old tenant is restricted or you have lost access to it, you must contact Microsoft 365 Support and provide DNS-level proof of domain ownership to have their backend team release it.