How to Verify a Microsoft 365 Domain Without Changing MX Records
Question details
The user needs to verify a domain in Microsoft 365 during a hybrid deployment without altering existing MX or Autodiscover records to avoid disrupting current mail flow and filtering services.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Setting up a Microsoft 365 hybrid deployment where on-premises Exchange and third-party mail filtering must remain active.
- Observed behavior
- The domain must be verified to proceed with Microsoft 365 configuration, but prematurely changing MX or Autodiscover A records will break the existing on-premises mail flow and third-party filtering.
Ensure you have administrative access to both your Microsoft 365 tenant and your domain's external DNS hosting provider to safely add new DNS records.
Verify the Domain Using a TXT Record
Adding a TXT record allows Microsoft to confirm you own the domain without impacting how your current email is routed or discovered.
During a hybrid migration, it is critical to separate domain verification from mail flow configuration. Microsoft provides multiple ways to verify a domain, but using a TXT record is the safest method. It proves ownership without acting as a routing instruction for email servers or clients.
Log in to the Microsoft 365 admin center, navigate to Settings, select Domains, and click on 'Add domain'. Enter the domain name you want to verify.
When prompted on how you want to verify ownership, select the option to 'Add a TXT record to the domain's DNS records' and copy the TXT value provided (usually starting with MS=).
Log in to your DNS registrar or hosting provider's control panel. Create a new TXT record for your domain (@), paste the MS= value into the destination field, and save the changes.
Return to the Microsoft 365 admin center and click 'Verify'. Once the domain is successfully verified, explicitly choose to skip the steps for setting up MX, CNAME, and Autodiscover records until your migration requires them.
Configure the Hybrid Environment
Use the Hybrid Configuration Wizard to connect your environments while retaining existing mail flow settings.
Manage Your Migration Plans with WPS Office
While managing Microsoft 365 hybrid deployments and DNS settings requires specialized admin portals, planning your migration shouldn't be difficult. WPS Office is a free, lightweight, and highly compatible alternative to Microsoft Office, perfect for creating migration checklists, tracking spreadsheets, and documenting IT procedures without adding to your licensing overhead.

Frequently Asked Questions
What happens if I change my MX record too early during a hybrid migration?
Changing the MX record prematurely will route all incoming emails directly to Microsoft 365. This bypasses your existing third-party mail filters and on-premises Exchange server, which can lead to broken mail flow, missed emails, and disrupted spam filtering.
Can I use an MX record for Microsoft 365 verification instead of a TXT record?
While Microsoft does allow domain verification via MX records, it is highly discouraged in hybrid scenarios. Verifying via MX will immediately alter your mail routing. You should always use a TXT record to maintain your existing mail flow.
When is the right time to update my Autodiscover record to Microsoft 365?
You should only update your public Autodiscover record to point directly to Microsoft 365 once all user mailboxes have been fully migrated to the cloud, or at the final cutover stage defined in your specific migration plan.
What is split-brain DNS and why might I need it for hybrid deployments?
Split-brain DNS allows a domain name to resolve to different IP addresses depending on whether the request originates from inside the internal corporate network or from the external public internet. It is often used in hybrid setups to ensure internal users connect seamlessly to on-premises servers while external services connect to the cloud.




