Public Microsoft 365 evidence we can test
Microsoft 365 is relevant here for Exchange Online DNS, MX, SPF and domain verification. The scanner does not sign in to the account; it compares the public-facing configuration associated with MX, SPF, autodiscover, domain verification so a provider dashboard and the Internet-visible result can be checked against one another.
- MX — Read the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
- SPF — Inspect the single public v=spf1 policy, validate its terms and count DNS-query-causing mechanisms; duplicate policies or excessive lookups can invalidate SPF.
- Autodiscover — Verify autodiscover from the public Internet and compare it with the value the responsible provider says should be live.
- Domain verification — Verify domain verification from the public Internet and compare it with the value the responsible provider says should be live.
Where Microsoft 365 changes normally belong
Microsoft 365 Admin Center for assigned DNS values and the authoritative DNS provider for publication. Before editing that area, verify that Microsoft 365 actually controls the failing layer; a domain may use a different company for authoritative DNS, mail or the origin application.
How to interpret Microsoft 365 detection
MX and SPF can support a Microsoft 365 identification, but signatures are confidence-weighted. If the visible address belongs to a CDN/reverse proxy, the edge provider is reported as the edge and the hidden origin is not guessed. Mail-provider signatures likewise identify public routing, not private account ownership.
Common Microsoft 365 change points
Exchange Online DNS, MX, SPF and domain verification most often breaks after a domain connection, nameserver move, website migration, certificate/HTTPS change or mail-DNS edit. For this provider, compare MX, SPF, autodiscover with the value expected for the exact domain and account before replacing a working setting elsewhere.
Repair Microsoft 365 without widening the incident
Save the current public value, change only the setting tied to the diagnosis, and preserve unrelated working records. If DNS is not authoritative at Microsoft 365, make the DNS edit at the provider named by the active nameservers. If Microsoft 365 owns only hosting or mail, leave the other service layers where they are.
Verify the Microsoft 365 repair
The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. The verification should use the exact hostname/service repaired and should no longer depend on a control-panel “connected” indicator once the public check is available.
What a public scan cannot see inside Microsoft 365
Billing state, private support actions, unpublished incidents, private origin addresses and authenticated account settings are outside a public diagnostic. HostWithShery reports those areas as unknown or a next support step instead of manufacturing certainty from a weak Microsoft 365 signature.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.