logo
search
Microsoft Account Errors

Fix Microsoft 365 Domain Not Accepted for Organization

Camila MilosovichCamila Milosovich Oct 1, 2026 869 views

Question details

The user is unable to use a custom domain for aliases and new users in Microsoft 365 despite passing initial DNS verification.

Fix Microsoft 365 Domain Not Accepted for the Organization
Product
Microsoft 365
Device & OS
not provided
Scenario
Setting up a custom domain for a Microsoft 365 organization to create new users and email aliases.
Observed behavior
The domain successfully passes the initial DNS verification but remains unaccepted for creating aliases and users because required DNS records exist in multiple or incorrect DNS zones.
Before you start

Ensure you have administrative access to your domain registrar's DNS settings and the Microsoft 365 admin center before attempting to modify DNS zones.

Solution 1Recommended

Consolidate and Update Authoritative DNS Zones

Verify and update all active DNS zones to ensure Microsoft 365 records are correctly applied to the active zone handling your domain traffic.

When a domain has multiple DNS zones, adding verification records to an inactive zone might pass initial checks but fail full configuration. You must ensure all required Microsoft 365 DNS records are present in the primary, authoritative zone.

1
Identify active DNS zones

Log in to your domain registrar or DNS hosting provider and review all authoritative DNS zones associated with your custom domain.

2
Add required Microsoft 365 records

Insert the specific TXT, MX, and CNAME records provided by the Microsoft 365 setup wizard into the primary active DNS zone that handles your domain's traffic.

3
Allow DNS propagation

Wait for the DNS changes to propagate across the internet. This typically takes anywhere from 15 minutes to 48 hours depending on your TTL settings.

4
Re-verify in Microsoft 365

Return to the Microsoft 365 admin center, navigate to Settings > Domains, and verify the domain configuration again before attempting to add new users or aliases.

Consolidate and Update Authoritative DNS Zones
DNS Propagation Delay: If the domain still shows as not accepted immediately after updating the records, allow more time for the DNS cache to clear globally before retrying the verification.
Free Microsoft Office alternative

Try WPS Office for a Hassle-Free Productivity Experience

Dealing with complex Microsoft 365 admin center setups and domain configurations can be overwhelming. If you just need a powerful, easy-to-use productivity suite for your team without the complex tenant management, WPS Office provides a lightweight alternative.

  1. 1. Download the installer: Visit the official WPS website and download the free WPS Office installer for your operating system.
  2. 2. Install the software: Run the downloaded file and follow the on-screen instructions to complete the quick installation.
  3. 3. Start creating: Open WPS Office to immediately start working on Word, Excel, and PowerPoint files without worrying about complex cloud tenant setups.
Completely free and lightweight office suiteHigh compatibility with Microsoft Office formats like .docx, .xlsx, and .pptxFamiliar user interface with zero learning curveNo complex domain configurations required for basic document management
microsoft office alternative - wps office

Frequently Asked Questions

Why does my domain pass DNS verification but still isn't accepted for users?

This typically happens when the domain has multiple DNS zones. The TXT verification record might be in one zone, but the active routing (MX/CNAME) records needed for creating users and aliases are missing from the primary active zone.

How long does DNS propagation take for Microsoft 365?

DNS propagation can take anywhere from 10 minutes to 48 hours, depending on your domain registrar's Time to Live (TTL) settings and how frequently global servers update their cache.

Can I use my custom domain for emails without adding all DNS records?

No. While a single TXT record can prove ownership of the domain, you must add MX records for email routing and CNAME records for autodiscover to fully utilize the domain for user inboxes and aliases.