Fix Error AADSTS50107: GoDaddy to Microsoft 365 Migration
Question details
The user needs to resolve intermittent sign-in failures and authentication errors after moving business email from GoDaddy to Microsoft 365.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Migrating a hosted email domain from GoDaddy's syndicated environment to a direct Microsoft 365 tenant.
- Observed behavior
- Users experience intermittent sign-in and Office application failures accompanied by Error AADSTS50107, which states that the requested federation realm object does not exist.
Ensure you have global administrator access to your new Microsoft 365 Admin Center and the login credentials for your domain's DNS hosting provider before making changes.
Update Microsoft 365 DNS Records at Your Host
Updating your DNS records ensures that Microsoft 365 can properly authenticate your domain and route emails, clearing the federation realm mismatch.
When migrating away from GoDaddy, the domain must be properly defederated and the DNS records strictly updated to point to Microsoft's standard servers.
Log in to your DNS hosting provider's dashboard (e.g., GoDaddy) and navigate to the 'DNS Management' or 'DNS Settings' page for your domain.
Locate and delete the old GoDaddy syndicated MX and TXT records that are interfering with the new Microsoft 365 setup.
Click 'Add New Record' to input the required MX, TXT, and CNAME records exactly as provided in the Setup > Domains section of your Microsoft 365 Admin Center.
Return to the Microsoft 365 Admin Center, go to Settings > Domains, select your domain, and click 'Check Health' to ensure the DNS changes have propagated.
Retain Current Website Hosting Settings
You can fix your email migration DNS issues without disrupting your active website hosting by only modifying specific mail records.
Contact Microsoft Support for Defederation
If the automated system continues to return AADSTS50107 errors or refuses working passwords, manual backend intervention is required to complete defederation.
Avoid Cloud Migration Hassles with WPS Office
If you are frustrated by complicated server migrations, federation errors, and locked-out user accounts, WPS Office offers a straightforward, offline-capable productivity suite that doesn't rely on complex cloud domain setups.
Frequently Asked Questions
What causes error AADSTS50107 after migrating from GoDaddy to Microsoft 365?
This error occurs because the domain was previously part of GoDaddy's syndicated Office 365 environment. When migrating to a direct Microsoft 365 tenant, the domain must be completely "defederated." If Azure Active Directory still looks for the old GoDaddy federation realm, it returns the AADSTS50107 error.
Will I lose my business emails if the migration system returns an error?
Your emails are generally safe. Error AADSTS50107 is an authentication and sign-in issue, not a data deletion issue. As long as your MX records are pointed correctly, incoming emails will queue or arrive at the new server, waiting for you to regain login access.
Do I have to migrate my website to Microsoft to fix this DNS issue?
No. You can leave your website hosted with its current provider. You only need to manage the DNS records (specifically MX, TXT, and mail-related CNAME records) at your DNS hosting provider to route email correctly to Microsoft 365.
