Editorial photograph of a security operations team reviewing Microsoft security tooling on a wall display
Guide · Microsoft · Security Licensing

Microsoft security, unbundled.

The standalone SKU map for Defender, Entra, Purview, Intune, and Sentinel. The escape route from the Microsoft 365 E5 trap and the buyer side guide to right size the security stack.

Read the Framework Microsoft Hub
12 to 34%Savings on unbundled paths
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Microsoft sells the security stack two ways. As the Microsoft 365 E5 bundle. Or unbundled across Defender, Entra, Purview, Intune, and Sentinel. The bundle wins on simplicity. The unbundled route wins on right sizing the spend for the actual security control coverage in use.

This guide reads as a buyer side framework. Use it with the security licensing guide, the E5 versus E3 comparison, the EA negotiation guide, and the Azure cost optimization article.

Key Takeaways

What a CISO needs to know in 90 seconds

  • M365 E5 sells eight security products in a bundle. Most enterprises use four to six of them.
  • The unbundled route saves 12 to 34 percent. Coverage right sized to the security operating model.
  • Defender for Endpoint Plan 2 stands alone. The plan ships without the wider E5 bundle pull.
  • Entra ID P2 stands alone. Conditional access and identity protection do not require E5.
  • Purview is modular. Information Protection, eDiscovery, Insider Risk each carry standalone SKUs.
  • Intune ships in M365 E3 already. A separate Intune Plan 2 SKU exists for advanced needs.
  • Sentinel is consumption priced. The SIEM sits outside the seat license entirely.

Why unbundle the security stack

Microsoft 365 E5 anchors the security pitch. The bundle ships eight to ten security products under one SKU. The standalone route prices the same products as discrete add ons over Microsoft 365 E3. The decision is not theoretical. The unbundled path routinely lands 12 to 34 percent below the bundle on the same effective coverage.

Three reasons buyers unbundle

  • Coverage right sizing. Pay for the products in use, not the full bundle.
  • Posture flexibility. Add or drop products at renewal as the security stack evolves.
  • Negotiation leverage. Standalone SKUs allow targeted price moves at renewal time.

The Microsoft 365 E5 trap

The E5 trap sits in the bundle math. The bundle prices below the sum of the parts at sticker. Most buyers stop reading there. The trap is the coverage assumption. The bundle pays only when the buyer uses six or more of the included security products at meaningful depth.

Five signals you sit in the trap

  1. Defender for Cloud Apps unused. The CASB sits unconfigured.
  2. Purview eDiscovery unused. The legal hold workflow runs on a separate platform.
  3. Entra ID Identity Protection unconfigured. The risk policies sit at defaults.
  4. Insider Risk Management dormant. No policies in production.
  5. Defender for Identity unconfigured. The on premises identity sensor not deployed.

The unread bundle

A buyer with three of eight bundle products in production pays for five products that do nothing. The unbundled route at the same scope routinely lands 18 to 26 percent below the bundle and locks the standalone SKU price for the negotiation horizon.

The standalone SKU map

The map below is the buyer side reference. Read it before quoting any renewal. The standalone SKUs price below the bundle on partial coverage and above the bundle only on full coverage at four plus products at depth.

Microsoft security standalone SKU map 2026

ProductStandalone SKUBundled inTypical use case
Defender for EndpointPlan 1, Plan 2M365 E3 has P1, E5 has P2Endpoint EDR and threat intelligence
Defender for Office 365Plan 1, Plan 2M365 E5Email threat protection, attack simulation
Defender for IdentityStandaloneM365 E5On premises Active Directory threat detection
Defender for Cloud AppsStandaloneM365 E5CASB, SaaS posture
Entra ID P2StandaloneM365 E5Identity Protection, PIM, access reviews
Purview Information ProtectionP1, P2M365 E3 has P1, E5 has P2Sensitivity labels, DLP
Purview eDiscovery PremiumStandaloneM365 E5Legal hold, advanced eDiscovery
Purview Insider RiskStandaloneM365 E5Insider threat detection
IntunePlan 1 in E3, Plan 2 standaloneM365 E3 has P1Mobile and endpoint management
SentinelConsumption SKU on AzureNot bundledSIEM, log ingestion, automation

Defender unbundled

The Defender family is the largest standalone surface. Plan 1 and Plan 2 split the endpoint product. The Office 365 product is sold separately. The Identity product runs against Active Directory. The Cloud Apps product is the CASB.

Which Defender products to keep standalone

  • Defender for Endpoint Plan 2. The EDR plus threat intelligence value sits here.
  • Defender for Office 365 Plan 2. The phishing and BEC protection value sits here.
  • Defender for Cloud Apps. Only if the CASB capability is in production use.
  • Defender for Identity. Only if a legacy Active Directory estate exists.

Entra unbundled

Entra ID P2 carries the Identity Protection engine, Privileged Identity Management, and the access review workflow. The standalone SKU runs alongside the M365 E3 baseline. The bundle does not deliver Entra benefits beyond what the standalone provides.

When Entra ID P2 standalone wins

  • The estate runs M365 E3. Add Entra P2 to the population that needs PIM.
  • Targeted population. Privileged users, finance, executive layer.
  • Compliance driven. Access reviews and PIM required for regulated entities.

Purview unbundled

Purview is the most modular family. Information Protection P1 sits in M365 E3. The advanced Information Protection P2 sits in E5. The eDiscovery Premium and Insider Risk products are bundled in E5 but each carries a standalone SKU. The unbundled route is often the right answer.

Which Purview modules to buy standalone

  • Information Protection P2. If sensitivity labels need auto labeling.
  • eDiscovery Premium. If the legal team uses Microsoft as the hold platform.
  • Insider Risk Management. Only if policies are in production.
  • Communication Compliance. Only for regulated industries.

Intune and Sentinel

Intune Plan 1 ships with Microsoft 365 E3. The Intune Plan 2 standalone covers advanced endpoint management. Sentinel is the SIEM. The Sentinel product is consumption priced on Azure outside the seat license entirely.

Intune and Sentinel pricing posture

ProductPricing modelBuyer side action
Intune Plan 1Per user, bundled in M365 E3No action, already covered
Intune Plan 2Per user standaloneAdd only on populations needing advanced endpoint management
Microsoft SentinelPer GB ingested plus per GB retainedUse commitment tiers, route log sources selectively

Bundle versus standalone math

The math depends on the depth of use across the eight security products. The table below is the rough cost comparison for a 5,000 seat estate at typical mid market Microsoft pricing. Use it as a starting frame, not a quote.

M365 E5 versus E3 plus standalone, 5,000 seat estate

Coverage profileM365 E5 pathE3 plus standalone pathBuyer side winner
Three products in production$57 per user month$36 to $42 per user monthUnbundled wins by 26 to 36%
Five products in production$57 per user month$48 to $54 per user monthUnbundled wins by 5 to 16%
Seven products at depth$57 per user month$60 to $66 per user monthBundle wins by 5 to 14%
Selective on small populationFull E5 across estateE3 plus targeted E5 add onsTargeted E5 add on wins on most estates

The targeted E5 add on play

Microsoft 365 E5 Security add on prices below the full M365 E5 SKU. A buyer can run M365 E3 across the estate and add the E5 Security add on to the population that needs the full security stack. The targeted path is the most common winner across mid market buyers in 2026.

What to do next

The seven step checklist below moves a Microsoft security estate from bundle inertia to a defensible unbundled or hybrid stack. Open it 6 to 9 months before the EA anniversary.

  1. Pull the security tooling inventory. Map the eight E5 security products to actual production use.
  2. Score depth of use. Tag each product as dormant, basic, deep. Trailing 90 day data.
  3. Identify the population that needs depth. Privileged, regulated, executive layer first.
  4. Quote three paths. Full E5, E3 plus standalone, E3 plus targeted E5 add on.
  5. Run the three year TCO. Include Sentinel consumption and Defender for Cloud Apps growth.
  6. Build the alternative posture. CrowdStrike, Okta, Splunk, Proofpoint as credible alternatives.
  7. Lock the standalone prices. Negotiate term length protection on each standalone SKU.

Frequently asked questions

Is Microsoft 365 E5 the only way to get the full security stack?

No. Every product in the M365 E5 security bundle is available as a standalone SKU. The unbundled path is the right answer when the buyer uses three to five of the eight security products at meaningful depth. The bundle pays only when seven or more products run in production at depth.

Does the Microsoft 365 E5 Security add on exist as a separate SKU?

Yes. The M365 E5 Security add on sits over Microsoft 365 E3. It ships the Defender suite plus Entra ID P2. The add on is the most common path for buyers running E3 across the estate who need the full security stack on a subset of users.

Is Sentinel included in any Microsoft 365 SKU?

No. Microsoft Sentinel is consumption priced on Azure. The SIEM sits outside the seat license entirely. Commitment tiers reduce the per gigabyte rate. Log source selection drives the realized cost more than any commit discount.

What is the smallest unit of Entra ID P2 a buyer can purchase?

Entra ID P2 is sold per user. The standalone SKU has no enrollment minimum on the CSP route. On the EA route the standard volume bands apply. Buyers commonly run Entra P2 on the privileged user layer only and run Entra P1 across the wider population.

Should a small regulated entity buy M365 E5?

Smaller regulated entities often unbundle. The bundle ships products that may not be required for the compliance scope. The unbundled path covers the regulated controls at lower cost and leaves the optional products for later add. A targeted E5 Security add on layer is often the cleanest answer.

How often does the Microsoft security SKU map change?

Microsoft revises the security SKU map two to three times a year. The product names, the inclusion in bundles, and the standalone availability move. Confirm the SKU map at the time of quote. The standalone SKUs in this guide reflect the May 2026 catalog.

How Redress engages on Microsoft security licensing

Redress runs the Microsoft security unbundling assessment as a four to six week workstream. The work pulls the production tooling inventory, scores depth of use, prices the three paths side by side, and lands the negotiation envelope on the standalone SKUs.

Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.

Score your Microsoft 365 stack against the buyer side benchmark in under five minutes.
Open the M365 License Optimizer →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

A buyer side framework for the next Microsoft renewal cycle. M365 E5 versus E3, standalone security SKU math, Entra and Purview posture, and the residual clause checklist.

Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for Microsoft customers running EA, CSP, or MCA Enterprise routes.

Microsoft EA Renewal Playbook

Open the white paper in your browser. Corporate email only.

Open the Paper →
12 to 34%
Unbundled savings
8 SKUs
Bundled in E5
5 of 8
Median products in use
500+
Enterprise clients
100%
Buyer side

We mapped the eight E5 security products to production use across 14,800 seats. Three products ran at depth. Two ran at basic. Three sat dormant. The targeted E3 plus E5 Security add on path landed 23 percent below the bundle quote on the same effective coverage.

Group CISO
European financial services group
More Reading

More from this practice.

Microsoft Hub →
Microsoft Security Licensing Guide
Microsoft · Guide
Microsoft Security Licensing Guide
The wider security catalog.
20 min read
Microsoft 365 E5 versus E3
Microsoft · Article
Microsoft 365 E5 versus E3
The tier decision decoded.
16 min read
Microsoft EA Negotiation Guide
Microsoft · Guide
Microsoft EA Negotiation Guide
Full EA negotiation framework.
24 min read
Microsoft 365 Copilot Licensing
Microsoft · Article
Microsoft 365 Copilot Licensing
Copilot enterprise framing.
14 min read
Microsoft Azure Cost Optimization
Microsoft · Article
Microsoft Azure Cost Optimization
Azure cost levers.
20 min read
Editorial photograph of enterprise contract negotiation strategy

Your Microsoft security stack is your envelope.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Microsoft licensing intelligence, monthly.

Security SKU movement, E5 versus E3 tier rationalization, Entra and Purview unbundling patterns, Sentinel commit math, and the wider Microsoft commercial leverage signals across every renewal cycle.