What you’re seeing
- Adding the company domain in the Microsoft 365 admin center ends with a message that it is already in use by another organization.
- Verification fails even after the TXT record has been created exactly as instructed.
- Nobody knows which Microsoft account owns the other tenant, or the person who set it up left years ago.
- Staff who once signed up for a free Microsoft service with their work email now get asked which account to use when they sign in.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- An employee signed up for a free or trial Microsoft service, such as Power BI, with a work address, which quietly created an unmanaged tenant tied to the domain.
- A previous Microsoft 365 subscription, perhaps bought through a hosting company or former IT provider, still holds the domain.
- A tenant created during an abandoned migration or trial was never cleaned up.
- Some resellers manage tenants on the customer's behalf, so the domain remains attached until that provider releases it.
- The domain was removed from the old tenant recently, and the change has not finished processing on Microsoft's side.
Why it matters
Until the domain is freed, you cannot move email to the new tenant, set up branded addresses for staff or finish a migration on schedule. Projects stall and people keep using a system you may not fully control. If the other tenant is owned by a former provider or ex-employee, they may still have access to data or email routing tied to your name. Resolving ownership closes that risk and unblocks the move.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Do we have to get into the old tenant to fix this?
Not always. Unmanaged tenants created by self-service sign-ups can often be taken over by proving domain ownership through DNS.
What if a former IT company owns it?
They can release the domain once asked, and they should hand over any admin access too. An engineer can help prepare that request so nothing is left behind.
How can AskTechGurus help?
A certified US engineer identifies where the domain is attached and works through the release with you in a remote secure session. Pricing starts from $99 and you pay only when it's resolved.