A buyer side guide to Intune Plan 1 versus Plan 2 in 2026. What each plan covers, how the Intune Suite fits, and how to license the advanced tier only where it is needed.
Intune Plan 1 is the core endpoint management already inside Microsoft 365 E3 and E5, while Plan 2 is a per user add on for advanced features, so the buyer side job is to license Plan 2 only for the users who truly need it.
This guide is for IT and procurement leaders sizing Intune in 2026. Read it with the Microsoft security licensing guide and the Microsoft Practice page so the device strategy and the commercial design stay aligned.
Plan 1 is the baseline. Plan 2 adds a defined set of advanced capabilities on top, so the split is about features rather than core management.
Plan 1 covers the everyday work of endpoint management. It enrolls devices, pushes policy, and protects company data across Windows, macOS, iOS, and Android.
Plan 2 layers advanced features on the base. It is an add on, so you always pay it on top of a plan that already includes Plan 1.
The Suite is the broadest package. It bundles Plan 2 with the other advanced add ons into a single per user subscription priced above Plan 2 on its own.
Intune licensing paths compared
| Path | Best fit | Watch out for |
|---|---|---|
| Plan 1 only | Standard device management | Already in E3 and E5 |
| Plan 1 plus Plan 2 | Some users need Tunnel or PKI | License only those users |
| Intune Suite | Broad advanced feature need | Pay for features you skip |
Plan 2 and the Suite stack on a base plan, never replace it. The user must already hold Plan 1 through E3, E5, or a standalone plan before the add on applies. Microsoft documents the Intune add on structure that governs this.
Cost control is about scope, not the list price. The base is usually already paid through M365, so the spend you control is the add on layer.
Map each advanced feature to the users who actually need it. Microsoft Tunnel suits a mobile field workforce, while a desk based estate may need none of the Plan 2 features at all.
Plan 1 is the core Intune endpoint management included in Microsoft 365 E3 and E5. Plan 2 is an add on that layers advanced features on top, including Microsoft Tunnel for mobile, Cloud PKI, and advanced endpoint analytics. Plan 2 only matters once you need those specific capabilities.
Yes. Intune Plan 1 is included in Microsoft 365 E3, E5, and the standalone Enterprise Mobility plans. Most organizations already own Plan 1 through their existing M365 licensing and do not need to buy it separately.
The Intune Suite bundles Plan 2 with the advanced add ons such as Remote Help, Endpoint Privilege Management, and advanced analytics into one per user subscription. It is the broadest package and is priced above Plan 2 alone.
Only if you need a feature it adds, such as Microsoft Tunnel, Cloud PKI, or advanced endpoint analytics. A standard estate that manages Windows and mobile devices is usually well served by Plan 1 inside E3 or E5.
Plan 2 is licensed per user as an add on to a base that already includes Plan 1. You cannot buy Plan 2 in isolation, so the math is always the base plan plus the Plan 2 increment per user who needs it.
License Plan 2 or the Intune Suite only for the users who need the advanced features, not the whole estate. Confirm Plan 1 is already covered by E3 or E5 before buying anything, and map each advanced feature to a real requirement.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The common error is buying Plan 2 for the whole base when only a slice needs Tunnel or Cloud PKI. The advanced features are paid for far more widely than used.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Microsoft 365 and endpoint licensing, Intune tiers, EA renewals, and the buyer side moves we are running in client engagements.