Why Most MSPs Skip Purview
Ask an MSP how they protect sensitive data and you’ll usually hear about a third-party DLP tool, an email security gateway, or a backup product with “compliance” in the name. What you’ll rarely hear is Microsoft Purview, even though most of their clients are already paying for some version of it.
For defense contractors handling CUI, that gap matters. Purview is the native control plane for labeling, encrypting, and tracking sensitive data across Microsoft 365. It maps directly to a large chunk of NIST 800-171 and CMMC Level 2. And it only works properly when it’s configured in the client’s own tenant, against the client’s own licenses.
This post covers why most MSPs don’t deploy it, what the licensing actually looks like, and how nuvioIT approaches it.
Why MSPs avoid Purview
It’s complicated. Sensitivity labels, label policies, auto-labeling, DLP rules, retention, insider risk, audit. Every piece has its own settings, its own licensing gate, and its own way to break Outlook if you get it wrong. There is no “turn on Purview” button.
It’s per-tenant by design. Unlike a SIEM, you can’t run Purview from an MSP-owned platform and point it at clients. Labels and policies live in the client tenant, tied to the client’s licenses. There’s no multi-tenant shortcut. Every deployment is a real deployment.
Third-party tools are easier to sell. A single DLP or email security product that the MSP already resells, manages from one console, and marks up is a simpler business than configuring Purview correctly fifty times.
Licensing is confusing. Purview features are scattered across E3, E5, add-on SKUs, and pay-as-you-go meters. Many MSPs don’t know which features a client’s license actually unlocks, so they avoid the whole thing rather than guess.
Mistakes are visible. Deploy Purview badly and users can’t open attachments, external partners get locked out of documents, or mail gets blocked. That’s a support ticket avalanche. A lot of MSPs decide the risk isn’t worth the reward.
What that costs the client
You’re paying for controls you’re not using. If you hold Microsoft 365 E5 or G5, you already own sensitivity labels, DLP, retention, insider risk, and advanced audit. Layering a third-party tool on top means paying twice for overlapping capability.
Third-party tools move your data out of your boundary. Most MSP-managed DLP and email security products inspect content in the vendor’s cloud. For a CUI environment, that’s another external system in your assessment scope, and usually one that isn’t FedRAMP High or ITAR-eligible.
Your CUI isn’t labeled. CMMC expects you to identify CUI, mark it, control access to it, and encrypt it in transit and at rest. Sensitivity labels do all four inside Microsoft 365. Without them, you’re documenting manual processes an assessor has to take on faith.
The configuration isn’t yours. When an MSP manages data protection through their own platform, the policies, rules, and audit trail live with them. Switch providers and the protection goes with them.
How Microsoft Purview licensing actually works
This is where most of the confusion lives, so here’s the practical breakdown.
Microsoft 365 Business Premium. The small business suite, capped at 300 seats in both Commercial and GCC High. On its own it includes manual sensitivity labels, basic DLP, standard retention, and standard audit, roughly the same Purview footprint as E3. Until recently it was Commercial only. Business Premium is now available in GCC High, and as of February 2026 it can be extended with two add-ons: Microsoft Defender for Business for the security side, and a Microsoft Purview add-on that unlocks the advanced compliance features (auto-labeling, Endpoint DLP, extended audit retention, Insider Risk) without moving to G5. For a defense contractor under 300 users, this is now the cheapest legitimate path to a CMMC-ready Purview deployment in a CUI enclave, and it’s the first thing we look at for a new small DIB client.
One caution: the commercial E5 Compliance add-on is not licensed for Business Premium. The admin center will let you assign it, but that isn’t a supported combination. In GCC High, the Purview add-on built for Business Premium is the right SKU.
Microsoft 365 E3 / G3. Gets you the basics: manual sensitivity labels, basic DLP for Exchange, SharePoint, OneDrive and Teams, standard retention policies, and standard audit. For many commercial clients, this is enough to get labeling and simple DLP in place.
Microsoft 365 E5 / G5. Unlocks the controls CMMC clients actually need: auto-labeling based on content, Endpoint DLP, advanced retention and records management, Insider Risk Management, Communication Compliance, Audit (Premium) with longer retention, and eDiscovery (Premium). This is the tier where Purview becomes a real compliance engine instead of a checkbox.
E5 Compliance / E5 Information Protection & Governance add-ons. For clients on E3 who don’t want the full E5 jump. The E5 Compliance add-on gets you most of the Purview E5 feature set at a fraction of the cost of full E5. This is often the right answer for a small DIB contractor.
Pay-as-you-go features. Some newer Purview capabilities, like certain data governance and AI-related protections, bill through an Azure subscription by usage rather than through a per-user license. Clients need an Azure subscription linked to Purview to use them.
GCC High. Same tiers, government SKUs. Business Premium with its Defender and Purview add-ons, G3 and G5, plus the enterprise compliance add-ons. Feature parity generally trails commercial by a few months, and some capabilities arrive later or not at all. We track this and design baselines around what’s actually available in GCC High today, not what the commercial roadmap promises.
The key point: the license has to be assigned to the user in the client’s tenant. There is no way for an MSP to license Purview on the client’s behalf from a separate environment. This is why the per-tenant model isn’t a choice for Purview. It’s the only model that works.
How nuvioIT does it
We deploy Purview directly in the client’s tenant, on the client’s licenses, and we’ve built the tooling to do it consistently.
Two baselines, not one. We maintain separate Purview baselines for GCC High and Commercial. The GCC High baseline is built for a CUI enclave: labels that mark and encrypt CUI, DLP rules that stop it leaving the boundary, retention aligned to DFARS, audit configured for assessment evidence. The Commercial baseline is built to keep CUI out: spillage detection and controls that catch CUI that shows up where it shouldn’t and route it back to the enclave.
Deployed from code, into your tenant. Our Purview toolkit is a set of PowerShell deployment scripts we pull down per client. It deploys the baseline, validates that the configuration matches what it should be, and flags drift when someone changes a setting later. Nothing runs from a nuvioIT-owned platform. The scripts execute against your tenant and the configuration lives there.
SSP evidence comes out of the deployment. The same toolkit exports the evidence your System Security Plan needs: which labels exist, what they enforce, which DLP policies are active, what retention is configured. When your C3PAO asks how you meet a control, we hand them the output from your own tenant.
Sentinel integration is part of the baseline. Purview alerts, label changes, and DLP events forward into your Sentinel workspace, which also lives in your tenant. Data protection and detection stay inside one boundary you own.
We license to fit, not to upsell. We map the controls you need to the cheapest license path that delivers them. For a small DIB contractor in GCC High that’s usually Business Premium plus the Purview add-on. For mid-sized shops it’s G3 plus a compliance add-on. Full G5 makes sense for larger environments or when you want everything in one SKU. We’ll tell you which and why.
What you actually get
- Sensitivity labels that identify and encrypt CUI in your tenant
- DLP that blocks CUI from leaving your boundary, with alerts in your Sentinel
- Retention and audit configured for CMMC evidence
- A documented, repeatable baseline that we can re-validate anytime
- SSP evidence generated from your own configuration
- Everything in your tenant, on your licenses, under your ownership
Fire us tomorrow and every label, policy, and audit record stays exactly where it is.
Questions to ask your current MSP
- Which Purview features does my current license include, and are we using them?
- Where does my DLP or data protection tool inspect my content? Whose cloud?
- Are my CUI documents labeled and encrypted today?
- Can you show me the Purview policies in my tenant, right now?
- If I leave, what data protection stays with me?
The bottom line
Most MSPs skip Purview because it’s hard to deploy well and easy to replace with something they can sell from one console. That leaves clients paying for controls they don’t use and pushing sensitive data through third parties they can’t scope.
nuvioIT builds Purview inside your tenant, on the licenses you already own, with a baseline designed for how CUI actually moves in a defense contractor’s environment. We manage it. You keep it.
If you want a look at what your current license already unlocks, reach out.
