Resolve Microsoft 365 Domain Verification Failure During Exchange Hybrid Setup
Question details
The user needs to resolve a Microsoft 365 domain ownership verification failure in an Exchange hybrid configuration, where a visible DNS TXT record does not prove ownership and the federation signing certificate may be missing or the domain tied to another tenant.

- Product
- Microsoft 365 / Exchange Online
- Device & OS
- not provided
- Scenario
- An IT administrator is configuring Exchange hybrid between on-premises Exchange and Microsoft 365 and cannot verify domain ownership.
- Observed behavior
- Domain verification fails even though a DNS TXT record is visible; the federation signing certificate is missing or Microsoft 365 reports the domain is already associated with another tenant.
Before making any DNS or tenant changes, confirm which Microsoft 365 tenant currently owns the domain and collect the Hybrid Configuration Wizard logs and Test-OAuthConnectivity results. Do not remove the existing TXT record until tenant ownership is verified.
Confirm Domain Ownership and DNS TXT Record in the Authoritative Zone
Use this first to determine whether the TXT record is in the correct authoritative DNS zone and which Microsoft 365 tenant currently owns the domain.
A visible DNS TXT record does not always resolve an ownership conflict. The domain may be verified in another tenant, or the record may be served from a non-authoritative zone.
Sign in to the Microsoft 365 admin center and go to Settings > Domains to view the domain status and associated tenant.
In your DNS host or registrar portal, open the authoritative DNS zone for the domain and verify that the Microsoft 365 TXT value is present and not only cached.
Run nslookup -type=TXT yourdomain.com from a command prompt and compare the returned value with the value shown in the Microsoft 365 admin center.
If the domain is listed in another tenant, sign in to that tenant and remove the domain or open a Microsoft support case before retrying verification.

Check the Federation Trust, OAuth Configuration, and Federation Signing Certificate on Exchange
Use this step when domain verification passes or to confirm whether a missing federation signing certificate is blocking hybrid setup.
Collect Diagnostics and Open a Microsoft Support Case
Use this when DNS and federation checks are inconclusive or before making disruptive tenant or DNS changes.
Switch to WPS Office as a Free Microsoft Office Alternative
If this Microsoft 365/Exchange hybrid domain verification issue blocks your setup, WPS Office cannot change Microsoft tenant ownership or repair Exchange federation, but it offers a free, lightweight, format-compatible alternative for the document editing side of your work. You can open, edit, and save Microsoft Word, Excel, and PowerPoint files without relying on Exchange hybrid or Microsoft 365 domain verification.
- 1. Download WPS Office: Go to https://www.wps.com and click the Download WPS Office Free button.
- 2. Install and launch: Run the installer, follow the on-screen prompts, then open WPS Office on your Windows or Mac computer.
- 3. Open existing Office files: In WPS Office, click Menu > Open and choose your .docx, .xlsx, or .pptx files from local storage or cloud drives.
- 4. Edit and save in Microsoft formats: Use the familiar ribbon tools to edit, then click Menu > Save As and keep the original Microsoft Office file format.

Frequently Asked Questions
Why does Microsoft 365 say the domain is already associated with another tenant?
This usually means the domain was previously verified in another Microsoft 365 tenant. Check Settings > Domains in each tenant you manage, or use the Microsoft 365 admin center support diagnostics. You must remove or confirm the existing tenant association before the hybrid domain verification can succeed.
Can a visible DNS TXT record prove domain ownership?
Not always. The TXT record might be in a non-authoritative zone, cached, or overridden by an existing tenant association. Verify the record in the authoritative DNS zone at your DNS host and compare it with the exact TXT value shown in Microsoft 365.
What Exchange logs should I collect before opening a Microsoft support case?
Collect the Hybrid Configuration Wizard logs and the full Test-OAuthConnectivity output. Also run Get-FederationTrust in Exchange Management Shell and include the federation trust status and certificate thumbprint.
Is this domain verification failure caused by WPS Office?
No. The issue is in Microsoft 365 tenant ownership and Exchange hybrid configuration. WPS Office is a document editing suite and does not manage Exchange hybrid setup or DNS verification.
Can I still use WPS Office if my Exchange hybrid setup is blocked?
Yes. WPS Office is independent of Exchange hybrid. You can open, edit, and save Microsoft Word, Excel, and PowerPoint files without requiring Microsoft 365 domain verification.




