Skip to content
home

Move from GoDaddy Microsoft 365 to Your Own Tenant

A lot of small firms bought their email through GoDaddy years ago and later found out their Microsoft 365 isn't fully theirs. Admin settings are missing, some features won't turn on, and support goes through GoDaddy instead of Microsoft. Here's how to take full control without losing a single email, in the order I use with clients.

Quick answer

Leave GoDaddy's Microsoft 365 without losing email or files: why GoDaddy limits admin access, defederation vs a new tenant, and a safe step-by-step order.

Daniel AwokunleDaniel AwokunleUpdated 11 November 2026 6 min read

1. Why GoDaddy Microsoft 365 feels limited

When you buy Microsoft 365 from GoDaddy, GoDaddy creates and manages the tenant for you. It usually has a name like NETORG followed by numbers, and sign-ins are federated to GoDaddy, so GoDaddy controls how users log in.

In practice that means:

  • Limited or no access to parts of the Microsoft 365 admin center and Entra ID.
  • Security features such as Conditional Access, Intune or some Defender settings are hard or impossible to use properly.
  • Licences can only be bought and changed through GoDaddy.
  • Third-party apps and some Power Platform features may not connect cleanly.

None of this is a problem for a two-person office that only needs email. It becomes one when you grow, need proper security, or want SharePoint, Teams and Power Automate working fully.

2. Your two options

  • Defederate the existing tenant: remove GoDaddy's control, keep the same tenant, mailboxes and files, and buy licences directly from Microsoft or another partner. Nothing has to be copied.
  • Move to a brand-new tenant: create a clean tenant you own from day one, then migrate mail, files and Teams across with a migration tool and move your domain over.

Defederation is usually faster and cheaper because the data stays where it is. A new tenant makes sense when the old one is a mess, you're merging companies, or you want a fresh start with a proper structure.

3. Before you touch anything

  1. Make a list of every user, shared mailbox, distribution list and alias.
  2. Note who has admin access today and confirm you can sign in to your domain's DNS settings.
  3. Check how many licences you have and which plan each person is on.
  4. Back up anything critical, especially mailboxes of people who have left.
  5. Pick a quiet time, such as a Friday evening, and tell staff that they may need to reset passwords.

4. Defederation in plain steps

  1. Get a global admin account in the tenant that is not federated through GoDaddy, using the tenant's onmicrosoft.com domain.
  2. Buy new Microsoft 365 licences for the same number of users directly from Microsoft or your new partner, in the same tenant.
  3. Convert your domain from federated to managed sign-in with Microsoft Graph PowerShell, so Microsoft handles logins instead of GoDaddy.
  4. Reset user passwords and have everyone set up multifactor authentication again.
  5. Assign the new licences to each user, then remove the GoDaddy licences.
  6. Remove GoDaddy as a partner with admin rights, then cancel the GoDaddy Microsoft 365 subscription.

The order matters. If licences are removed before new ones are assigned, mailboxes become unlicensed and people lose access until it's fixed.

5. Moving to a new tenant instead

  1. Create the new tenant and set up users, licences and security first.
  2. Plan the SharePoint and Teams structure in the new tenant rather than copying old clutter.
  3. Pre-copy mailboxes and files with a migration tool while staff keep working.
  4. On cutover day, remove the domain from the old tenant, add it to the new one and update the MX, autodiscover and SPF records.
  5. Run a final sync for the last changes, then reconnect Outlook and OneDrive on each device.

Expect a short email interruption during the domain switch. With good planning it's a few hours, done outside working hours.

6. What users will notice

  • A password reset and a new multifactor authentication setup.
  • Outlook, Teams and OneDrive may ask them to sign in again.
  • With a new tenant: a fresh Outlook profile, and phones need the account removed and added again.
  • Email history, calendars and contacts stay, as long as the steps are followed in order.

A one-page note telling staff what to expect cuts support calls a lot.

7. Common mistakes

  • Cancelling GoDaddy before new licences are in place.
  • Forgetting shared mailboxes, aliases and forwarding rules.
  • Leaving old DNS records that still point mail at the old setup.
  • Not telling staff, so password prompts look like phishing.
  • Skipping security: after the move, turn on multifactor authentication and review sharing settings straight away.

8. Is this a DIY job?

For a handful of users with only email, a confident IT person can defederate in an afternoon. Once you have shared mailboxes, SharePoint sites, Teams, phones and a business that can't afford a day without email, it's worth having someone who has done it before plan the order and stay on call for the switch.

Either way, use the move as a chance to fix the setup: the right plan for each person, proper security, and a SharePoint and Teams structure your staff can actually find things in.

Want this done for you?

I build this for clients every week. Book a free 30-minute call and I'll tell you exactly what your team needs.

Free: the Microsoft 365 clean-up checklist

The 12 checks I run before building anything in a client's tenant: security, sharing, files and quick wins. Two pages, PDF.

Used only to send the checklist and the odd useful tip. Never shared or sold.

Daniel Awokunle · replies within a day

Tell me what's slowing your team down.

Thirty minutes, no cost, no pitch deck. You'll leave knowing exactly what to build and what it should cost.

Book a free 30-min call
  1. Step 1

    Free 30-min call

    Show me the problem. I'll tell you what I'd build and how long it takes.

  2. Step 2

    Clear quote

    A fixed price and timeline in writing, usually within a day.

  3. Step 3

    Built and handed over

    Built in your own Microsoft 365, with a walkthrough for your team.