Turning Unbilled Microsoft 365 Security Work Into a Service Line
- ChannelPro Team
- 434 views
Most MSPs absorb Microsoft 365 security work for free. Here's a five-step way to itemize it, baseline it, and turn QBRs into priced recommendations.

Most MSPs that manage Microsoft 365 are doing more security work than they bill for, and much of it never appears on an invoice. An engineer cleans up a permissions sprawl. Someone pulls a risky forwarding rule. A technician tightens an access policy after a suspicious sign-in. Each task is small. Together they add up to a meaningful share of monthly engineering hours, and because they get folded into a flat fee, nobody on the sales side can talk about them.
Shay Cohen, CEO and co-founder of Optimize365, an M365 security management platform aimed at MSPs, makes the case that this is a pricing problem more than a workload problem. He lays out a five-step path for turning that background labour into a visible, repeatable service line. Cohen's company sells tooling in this space, so read his framing with that in mind. The underlying logic holds up regardless of which tools you use.
The workload is growing, not shrinking
Cohen points to a stream of platform changes over the past year. Microsoft has been rolling enhanced Defender for Office 365 protections into lower-tier E3 plans, adding time-of-click URL scanning to Outlook and Office apps, folding Security Copilot into E5 by default, and expanding Intune's management and privilege controls. Most of these land on tenants automatically.
That's the warning and the opportunity in one. Every new control is another setting your team has to evaluate, configure and explain to a client. If you aren't billing for that evaluation, the unbilled workload keeps expanding with each rollout. Cohen's point is that the work isn't optional for an MSP, since the client assumes someone is watching. So the question becomes whether you get paid for it.
Step one: find out what you're already giving away
Start with the ticket history. Pull recent tickets and projects and sort them by what they touched. How many involved identity, access, permissions, email security, configuration changes, policy updates or remediation? Of those, how many were billed separately, and how many were absorbed into the monthly agreement?
Cohen's experience is that most MSPs find a meaningful chunk of engineering time going to security work that was never itemized. He's blunt about what that means: it isn't generosity, it's a pricing model that hasn't caught up with what you deliver. Platform-originated work deserves its own line. When Microsoft ships a change, someone still has to evaluate and configure it, and that's billable even if no client asked for it.
His suggested exercise is simple. For one month, tag every Microsoft 365 ticket related to identity, access or configuration. At month's end, compare time spent against what was actually billed. The gap is your starting number.
Step two: define "good" before you scale
You can't build a repeatable service on inconsistent tenants. If every client environment is configured differently, every issue becomes a custom investigation, and you have no clean way to explain what a healthy tenant looks like. Cohen argues for a documented security baseline covering areas such as MFA, administrator roles, email security settings, external sharing, mailbox permissions, conditional access and user access controls.
The details will differ by client type, but the principle holds: define a healthy environment first, then monitor against it. Once you have that reference, deviations can be caught automatically rather than discovered during an incident review.
The baseline also needs a review cadence. Microsoft changes default settings and introduces new controls several times a year, so a baseline that sits untouched will quietly go stale while clients assume it's still being enforced. Standardization gives you leverage too. Senior engineers define the baseline once, other technicians apply it consistently, and account managers can explain it in plain terms.
For a practical starting point, Cohen suggests picking your three most common client configurations and writing one baseline that would fit roughly 80% of your book. Refine from there.
Step three: make drift visible to the client
Microsoft 365 tenants never sit still. Users come and go, roles change, sharing settings shift, apps get connected, and policies get edited. Some of that is intentional, some accidental, and some introduces real risk. Configuration drift is where the service opportunity lives.
Some drift doesn't originate with the client at all. When Microsoft enables a new control or changes a default, a tenant's posture can move overnight with no one touching anything. It still has to be caught, explained and accounted for against the baseline.
Clients may not follow the technical details, but they understand that an environment can slowly drift away from a secure state. An MSP that monitors meaningful changes, flags deviations and fixes them before they become incidents builds that value in plain view. The catch is the visibility. Cohen's warning is that if a client can't see the prevented problems, they can't value them, and a competitor with a slicker report can take the account.
Before your next round of reviews, he suggests writing down three things your team fixed or prevented for each client in the last quarter, described in plain language. That list becomes the evidence base for everything else.
Step four: price remediation as a deliverable
Once risk is visible, fixes should stop being favours. A misconfiguration that gets caught and corrected is work, and if your team already estimates effort or complexity, you have the inputs needed to price it.
Cohen recommends a tiered structure. Some items sit inside the retainer, while others are scoped as billable projects. Be upfront about which is which and write down the rules. His observation is that clients rarely object to paying for valuable work once they understand what was done and why it mattered.

Shay Cohen
A practical move is a simple remediation menu covering common tasks such as permission cleanup, licence realignment and policy hardening. Each entry should state the price, what's covered and what isn't. Menus remove the awkward negotiation that happens when a technician has to explain a bill after the fact.
Step five: run the QBR as a sales meeting with a report card
Many MSPs treat the quarterly business review as a status report. Cohen's view is that the better ones treat it as a sales conversation that happens to include a report. If you've completed the first four steps, you already have the material. The frame should be business impact, with questions such as:
- What has changed in the client's environment?
- What risks were identified?
- What did your team fix or prevent?
- What remains unresolved?
- What did Microsoft change on the platform this quarter, and what did we do about it?
Then ask the forward-looking question: what should we tackle next quarter, and why? That follows naturally from a conversation already underway, and the answer can carry recommendations for additional work, higher service tiers or focused remediation projects.
Cohen suggests ending every review with one specific Microsoft 365 security recommendation for the next 90 days, prioritized and priced where appropriate. Cadence matters less than specificity. A quarterly review with concrete, priced recommendations will do more than a monthly check-in that only reports status.
What to do before your next planning cycle
Cohen's bottom line is that Microsoft 365 security is no longer a side task. For many clients it's among the most important areas of operational risk, which gives MSPs a real opening, provided the work is structured so clients understand it and the firm can deliver it profitably.
Before your next planning session, I'd put three questions to the team. How many security hours went unbilled last quarter? Which client tenants still lack a written baseline? And what would your next review look like if every line item had a price? Start with your newest or smallest accounts, where standardizing a clean environment is far easier than retrofitting a legacy one. Build the habit there before taking it to your largest clients.