Comparison guide

Magrathean vs MSP for M365 security

Compare project-based Microsoft 365 security cleanup with a traditional managed service provider contract.

The right choice depends on who will own the control after the first fix. Use this page to separate specialist remediation, general support, assessment readiness and ongoing operations before you buy the wrong shape of help.

Buying signal

Decide by ownership after the fix.

If the problem is a security control gap, the useful output is a decision trail: what is weak, what should change first, who owns it and what evidence proves the change happened. If the problem is day-to-day capacity, the useful output is usually a support model and recurring service level.

Use the rows below to check whether the work needs focused Microsoft 365 security depth, assessment readiness, routine user support or a long-running operational supplier. Mixing those jobs is how scope becomes expensive and unclear.

Decision point

Magrathean

Typical MSP

Scope

Focused review, remediation and handover for Microsoft 365, Entra ID, Intune, Defender and CE Plus readiness.

Broad ongoing support, user tickets, device support, supplier management and recurring operations.

Buying model

Defined project around a specific control problem.

Retainer or per-user managed service contract.

Best fit

You need risky controls fixed, reviewed or prepared for audit.

You need ongoing helpdesk and day-to-day IT operations.

Handover

Outputs are designed for internal IT or an existing MSP to keep running.

Operational knowledge often stays inside the MSP delivery model.

Questions before choosing

Is the urgent problem security posture or everyday ticket volume?
Who will own Conditional Access, Defender, Intune and evidence after the work finishes?
Do you need a fixed remediation backlog or a recurring operations contract?

Handover to expect

Project work should leave a risk register, approved changes and runbook. MSP work should leave a support model, escalation route and recurring service rhythm.

A common example is a company with an MSP already answering user tickets but no one owning Conditional Access exceptions or Defender alerts. That company does not need a second helpdesk first; it needs the risky control set reviewed and handed back with evidence, owners and recurring checks.

What a clear decision should produce

By the end of the comparison, you should know whether Magrathean or Typical MSPfits the current problem, who will own the work after purchase, what evidence should be produced, and which work should be left out of scope. That prevents a security project from turning into general support, and prevents support work from being judged as specialist remediation.

Choose Magrathean when

You already have internal IT or an MSP but need specialist Microsoft 365 security depth.
You want a control-by-control plan with handover, not another support queue.
You need Cyber Essentials Plus readiness or tenant cleanup before a deadline.

Choose Typical MSP when

You need first-line helpdesk coverage.
You need hardware, printer, telecoms or office support.
You want one supplier to run ongoing IT operations.

Book review See proof