'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft 365 MX Record Values That Do Not Match
Question details
The user needs to resolve an issue where Microsoft 365 fails to recognize a newly configured MX record during a Google Workspace email migration, despite TXT and CNAME records verifying successfully.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Migrating email hosting from Google Workspace to Microsoft 365 and verifying domain ownership and routing.
- Observed behavior
- Microsoft 365 displays a mismatch error for the MX record values and fails the domain verification process.
Ensure you have administrator credentials for both your Microsoft 365 Admin Center and the DNS hosting provider where your domain is managed.
Verify and Update MX Records in the Microsoft 365 Admin Center
Compare the required MX record parameters in Microsoft 365 with your DNS host configuration and remove conflicting records to pass verification.
Log in to the Microsoft 365 admin center, navigate to the left navigation pane, click on 'Setup', and then select 'Domains'.
Click on the specific domain you are trying to verify for the email migration to open its settings panel.
Navigate to the DNS records tab. Note the exact required MX value provided by Microsoft 365, paying close attention to the hostname, priority (usually 0), and destination address.
Log in to your DNS hosting provider's portal (e.g., GoDaddy, Cloudflare, etc.). Locate the MX records for your domain and ensure they perfectly match the Microsoft 365 requirements. Delete any old or conflicting MX records from your previous host (like Google Workspace).
Save your changes at the DNS host. Keep in mind that DNS propagation can take anywhere from 15 minutes to 72 hours. Return to the Microsoft 365 admin center later to click 'Verify' again.
Looking for a Lightweight Alternative to Microsoft Office?
While troubleshooting domain setups in Microsoft 365 admin center can be complex, your daily document work shouldn't be. WPS Office offers a free, lightweight, and highly compatible alternative for handling documents, spreadsheets, and presentations without subscription hassles.
Frequently Asked Questions
Why did my TXT and CNAME records verify but not the MX record?
TXT and CNAME records often propagate faster or were entered without conflicting existing records. MX records can conflict with existing mail routing (like old Google Workspace MX records), which must be removed before Microsoft 365 will verify the new ones.
How long does it take for a new MX record to work?
Standard DNS propagation typically takes between 15 minutes to 48 hours. However, in some cases, it can take up to 72 hours for servers globally to recognize the updated MX record and route email properly.
What should the priority be for my Microsoft 365 MX record?
Microsoft 365 usually requires the MX record priority to be set to 0. Always refer to the exact priority value provided in the Microsoft 365 admin center under your domain's DNS settings, as using a different number will cause a mismatch error.
Can I keep my old MX records active while adding Microsoft 365 records?
No. While a domain can technically have multiple MX records for backup routing, keeping the old Google Workspace MX records alongside the Microsoft 365 ones will cause mail delivery confusion and domain verification failures. Remove the old ones once you are ready for the final cutover.
