Moving domain to Microsoft 365, not sure which records exactly are needed
M365 has a fixed bundle: one MX, one SPF, one Autodiscover, a DKIM pair (CNAMEs) and optional Teams SRVs. The M365 domain wizard provides your exact hostnames, copy them literally because every tenant has a different suffix.
Try this first
- 1MX: <yourdomain-tld>.mail.protection.outlook.com priority 0, the only MX (do not keep an old backup MX).
- 2SPF (TXT at apex): v=spf1 include:spf.protection.outlook.com -all (or ~all during transition).
- 3Autodiscover (CNAME): autodiscover.<yourdomain> points to autodiscover.outlook.com.
- 4DKIM: set selector1._domainkey and selector2._domainkey as CNAME to selector1-<tenant>._domainkey.<tenant>.onmicrosoft.com and selector2-... likewise. Then enable DKIM in the Defender portal.
- 5Teams (optional): SRV _sip._tls and _sipfederationtls._tcp, plus CNAMEs lyncdiscover and sip to webdir.online.lync.com and sipdir.online.lync.com.
When to bring us in
If you already have a mail vendor and want a cutover to M365 with DKIM rotation and no mail pause, we plan the cutover with a test mailbox first.
See also
- Domain expires tomorrow and nobody saw the emailAn expired domain doesn't transfer instantly. There's a redemption window, but you pay extra.
- Unsure whether to enable auto-renewDisabling auto-renew only makes sense for domains you'll truly drop. For anything live, just keep it on.
- New registrar asks for auth code, can't find itEPP code or transfer code is the password to move a domain from registrar A to B.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.