Microsoft 365 + email
A mailbox is only one part of the job. Work through ownership, access, domain protection, delivery, retention, recovery, migration, and handover without treating every symptom as a password or Outlook problem.
Start here
Choose the closest outcome. If your problem crosses two paths, begin with the earlier lifecycle stage: foundations before protection, diagnosis before correction, and evidence before change.
Choose and connect
Start here when you are choosing a service or deciding how people should reach an existing mailbox. Ownership, administration, secure sign-in, synchronisation, and exit matter before feature lists and server fields.
Back to the decision mapChoose a mailbox service by deciding who owns the address, who protects the domain, who must administer it, how people will work, and how you could leave—before comparing storage, apps, or promotional prices.
Choose webmail, an email application, or both; add an account through its secure provider sign-in; and diagnose common setup and synchronisation problems without guessing.
Protect and recover
Use this path when the question is domain impersonation, retention, recovery, or backup. It separates controls that are often bundled together in sales language but do very different jobs.
Back to the decision mapUnderstand the continuing work behind DMARC, decide whether to run it yourself or get help, and evaluate providers without buying a dashboard, promise, or policy you cannot safely operate.
Decide whether you need more mailbox space, records retention, legal preservation, deleted-item recovery, or a recoverable point in time—because an archive mailbox solves only some of those problems.
Diagnose the failure
Follow this path when a message did not arrive, Outlook cannot find something, or a recipient looks stale. The aim is to identify the system that failed and make the smallest supported correction.
Back to the decision mapFind the last verified handoff, interpret the complete SMTP response, and test one controlled path before changing mail flow—without disabling TLS, MFA, authentication, or domain protection.
Find out whether the missing result belongs to mail search, a local index, the live directory, an offline address-book snapshot, personal contacts, or recipient suggestions—then correct the smallest proven fault.
Change and hand over
Use this path for tenant moves and staff departures. Both jobs need a defined owner, preserved source, scoped access, acceptance evidence, cleanup, and a handback that actually closes the work.
Back to the decision mapTurn a Microsoft 365 migration into an accountable change: inventory the real workload, prove identity and DNS control, pilot the chosen method, validate user outcomes, and decommission the source only after acceptance.
Recover authorised business data without taking over the person's identity: define purpose, preserve the retention window, grant accountable temporary access, transfer only what is needed, and remove that access when the handback is complete.
Not the right problem?
For Windows, networking, hardware, security, and other technology questions, search the full guide library.
Browse every guide