Augmentt surveyed 193 MSP professionals about how they manage Microsoft 365 across their clients. The results were blunt: 77% aren’t fully confident every client tenant meets their own security baseline, 58% still set up new tenants by hand or with custom scripts, and only 17% describe their M365 work as mostly proactive.
We asked three MSP leaders to react: John Hansman, CEO of truit; Avion Bryant, CTO of Stronghold Data; and Rory Dakin, Owner of ComputersDOTCalm. Between them they cover a two-person shop, a three-person shop and a platform MSP with more than 200 tenants. Here’s what they told us.
Here’s the full conversation:
Manual onboarding is where the gaps start
58% of MSPs set a new tenant’s security baseline manually or with scripts. Only 38% push it automatically from a platform.
John wasn’t entirely surprised. Before automating, his team had to “muscle our way through onboarding,” and he still meets prospects who have a couple of tools in place and no layered approach.
Avion explained why it matters as you grow. Offboarding is a common example: a tech disables the license but leaves the user active, along with guest accounts, app registrations and other access attached to it.
“When you’re doing a lot of things, manual tasks, what happens is you open up security gaps.” -Avion Bryant, CTO at Stronghold Data
Most M365 work is still reactive
Only 17% of MSPs say their M365 work is mostly proactive, and 63% had a Microsoft change create unplanned work or break something in a client environment in the past year.
Rory’s advice for staying ahead: don’t overcommit, and understand, trust and stick to the tools you use. A small team can’t keep up with Microsoft by hand. His team used to rely on scripts and manual inputs, and as they grew, that became very hard to keep track of, even with good documentation.
Baseline confidence comes down to discipline
Is 100% confidence in every tenant’s baseline possible? Avion thinks so, but says it takes discipline, not just tooling. Complacency, staff turnover and pressure from clients are what erode it.
John compared it to backup checks: you verify the baseline the same way you verify backups ran. Rory added that standardizing licensing matters as much as standardizing tools. A mix of Basic, Standard, Premium and Copilot licenses across clients makes a consistent security posture very hard to define.
That lines up with the survey: 52% of MSPs named consistency and standardization as their top priority, above margin, scale or upsell.
“Standardization gives you efficiency, efficiency gives you profitability.” – Rory Dakin, Owner at ComputersDOTCalm
💡 Related content: “Compliance as a Growth Engine” Watch the webinar replay →
Liability: contracts, reports and insurance
An attendee asked how a smaller MSP manages liability. John’s first answer was simple: have really good contracts, because too many MSPs still work on a handshake. He also says to make sure clients understand you are not their cyber insurer. They need their own policy.
Avion added transparency. Send regular reports on the client’s Microsoft environment, and if a client refuses something like conditional access, document it and put it in your managed service agreement. Rory suggested using cyber insurance requirements as a model for defining your own responsibilities.
When clients push back on security
Another attendee asked whether they require clients to adopt their security standards. All three said yes.
“For one, I don’t want to be in the news. Two, I don’t want you in the news.” -Avion Bryant, CTO at Stronghold Data
When a new baseline comes out, Avion calls the client and raises it. If they won’t agree, it’s an exit conversation. John moved his business to three plans, each starting with cybersecurity, and lost one client in the switch. Rory simply implements improvements, because clients trust his team to do the right thing. Avion’s one caveat: regulated clients, such as banks or those under CMMC, need a formal process for any new tool.
Three ways to report security work
Only 42% of MSPs prove their security work with automated reporting. The three guests showed three different approaches:
- Rory lets clients choose monthly, quarterly, annual or no reports, and keeps everything in a portal they can access.
- John skips emailed reports and meets every client quarterly, bringing the reports to the meeting.
- Avion sends monthly reports to regulated clients who face audits and exams, and uses reporting with everyone else to show his team’s work and shape strategy with leadership.
Copilot readiness starts with governance
40% of MSPs said AI and Copilot are their top client request, but only 10% say more than three-quarters of their client tenants are ready for it.
John’s view is that employees are already using AI, so governance comes first: find out what’s being used, then standardize on one tool. Rory pairs Copilot with Purview and gives curious clients an isolated sandbox to experiment in. Avion recommends a top-down rollout, starting with the owner, so the data Copilot can reach becomes a conversation before it becomes a problem.
A note from us
This part is our point, not our guests’. The report shows that most MSPs know what their baseline should be. The hard part is applying it the same way across every tenant and proving it stays applied. That’s what Augmentt is built for: deploying baselines across client tenants from one place, alerting when something drifts, and reporting on it in a way clients understand.
Read the full M365 MSP Reality Report to see all the findings.
FAQs
- How do most MSPs set up security for a new Microsoft 365 tenant? In Augmentt’s survey of 193 MSPs, 58% set a new tenant’s security baseline manually or with custom scripts. Only 38% push it automatically from a platform.
- Why is manual offboarding a security risk? A tech may disable a license but leave the user active, along with guest accounts, app registrations and other access. Repeatable, automated offboarding closes those gaps.
- How should a small MSP manage liability? Use strong written contracts, define your responsibilities clearly, document any security measures a client refuses, and make sure clients carry their own cyber insurance.
- Should MSPs require clients to follow their security standards? All three MSP leaders on the panel do. They raise standards when threats change and treat a client’s refusal as grounds for an exit conversation, with extra process for regulated clients.
- How can MSPs prepare client tenants for Copilot? Start with governance: find out which AI tools are already in use, standardize on one, protect data with tools like Purview, and roll out from the top down so data access is reviewed first.