How to Set Up Microsoft 365 Email with Your Domain

Set up Microsoft 365 email with your own domain in a deliberate sequence: verify ownership, prepare recipients, publish the required DNS records and test delivery before retiring old mail.

Start here: a new domain or existing mail?

If this domain already receives business email, inventory its mailboxes, aliases, shared addresses and existing provider before changing MX records. Adding a domain to Microsoft 365 does not transfer old messages or automatically create all recipient addresses.

You need an appropriate Microsoft 365 service and authorized administration rights. Features and licensing vary. This guide describes a standard setup path, not a promise that every account includes every feature.

1. Verify ownership without moving mail

In the Microsoft 365 admin center, open Settings → Domains → Add domain using an account with the required domain-administration role. Follow the tenant’s verification instructions, typically adding a supplied TXT record at the authoritative DNS provider.

Copy the exact tenant-provided value. Verification proves control; it is not the same as switching mail delivery. If offered automatic DNS setup, review all proposed changes and their effect on existing services before authorizing it.

2. Prepare every receiving address

Create and license the required users and prepare shared mailboxes, aliases, groups and other intended recipients. Test authorized sign-in and mailbox access. Confirm administrative recovery and MFA arrangements before the cutover window.

For a migration, plan historical message transfer separately and keep the old service available. A mailbox that can sign in is not proof that all existing mail or recipient addresses are present.

3. Add the exact service records

Use the DNS values shown for this domain in your tenant, including MX and Autodiscover as required. Do not copy another business’s MX target. Preserve unrelated website and verification records.

Merge authorized senders into one SPF policy rather than adding a second SPF TXT record. Configure DKIM using the domain’s actual selector CNAME values, then plan DMARC after understanding all legitimate senders. See the separate authentication guide for those checks.

4. Make the delivery switch deliberately

After recipients are ready, replace the old MX routing according to the tenant instructions. Do not leave the old server as a casual lower-priority backup: it may accept mail into a mailbox no longer monitored.

If cPanel still hosts the website, confirm its mail routing recognizes an external email provider. Otherwise website-generated mail can be delivered locally instead of following public MX records.

5. Validate both directions

Send from an external mailbox you control to a new business mailbox, reply, and test important aliases. Check Outlook on the web before troubleshooting a desktop app. Confirm website forms still reach their recipient, and inspect authentication in received message headers.

Resolve-DnsName -Name your-domain.example -Type MX
Resolve-DnsName -Name your-domain.example -Type TXT

Expect the intended MX target and a single applicable SPF policy among other TXT records. Cached answers may differ temporarily; compare against authoritative DNS if needed. DNS success alone does not prove mailbox provisioning or delivery.

If the switch fails

Use delivery errors and Microsoft 365 service health to identify the problem. Do not delete accounts or disable MFA as a shortcut. A rollback of MX records also needs a plan for messages already delivered to the new system; preserve and reconcile both sides.

Official references

• Microsoft: Add a Domain
• Microsoft: Create DNS Records at Any DNS Host
• cPanel: Email Routing

Documentation checked 2026-10-18. Examples use reserved names and addresses; replace placeholders only for systems you are authorized to manage. Interfaces and included features depend on your provider and account.