Windows Enterprise E3 vs E5 comes down to one line on Microsoft’s own licensing page: E5 is everything in E3 plus Microsoft Defender for Endpoint Plan 2. Most comparison pages bury that under a long feature grid, so it looks as if E5 unlocks more of Windows itself. It does not. This post sets out what each subscription actually carries today, which E3 features still need the Enterprise edition on the device, and how to decide whether the E5 step is worth buying for Windows alone.
The choice is one branch of the rules that decide a Microsoft 365 licensing bill, and most organisations meet it inside the Microsoft 365 E3 vs E5 suite decision rather than as a standalone Windows purchase. I have not run either subscription in production; my tenant is a lab with no enrolled devices, so what follows is Microsoft’s documentation, checked on 4 November 2026, plus where I would expect it to bite.
Windows Enterprise E3 vs E5 in one table
The Windows Commercial Licensing overview on Microsoft Learn describes both offers, and its last update is dated 27 May 2026. The rows below come from that page, read on the day of writing. Prices are left out on purpose: they vary by agreement and channel, and a price I cannot check against your quote is a price I will not print.
| Area | Windows 11 Enterprise E3 | Windows 11 Enterprise E5 |
|---|---|---|
| Licensing model | Per user, Commercial Licensing including CSP | Per user, Commercial Licensing including CSP |
| Qualifying operating system | Windows Pro | Windows Pro |
| Enterprise edition OS features | Included | Included |
| Cloud capabilities (Autopatch, Universal Print, subscription activation) | Included | Included |
| Use rights (five Windows instances per user, 36 months support on annual feature releases, virtualisation rights) | Included | Included |
| Microsoft Defender for Endpoint Plan 2 | Not included | Included |
Read down the right-hand column and the only new row is Defender for Endpoint Plan 2. Every Windows feature, every cloud capability and every use right on the page sits in E3. The Learn page describes E5 as being for organisations that want everything in E3 with the addition of Defender for Endpoint Plan 2, a service that helps detect, investigate and respond to advanced attacks on endpoints and networks.
What Windows Enterprise E3 already gives you
E3 is the subscription that turns a Windows Pro device into an Enterprise one, and it carries three kinds of entitlement. The licensing page lists them separately, and the split matters because each kind behaves differently on a device that never left Pro.
Operating system features. Credential Guard, Microsoft Defender Application Guard for Microsoft Edge, Modern BitLocker Management, Personal Data Encryption, DirectAccess, the Always On VPN device tunnel and Windows Experience customization, which covers locked-down desktops and Shell Launcher with Unified Write Filter for kiosks.
Cloud-based capabilities. Windows subscription activation, Windows Autopatch, Universal Print, Microsoft Connected Cache, Endpoint analytics proactive remediation and Organizational messages.
Use rights. Five Windows instances per licensed user, 36 months of support on annual feature releases, access rights for Azure Virtual Desktop, Windows 365 Enterprise and Virtual Desktop Access including FSLogix, Windows release health in the Microsoft 365 admin center, the feature update readiness and compatibility risk reports, Windows LTSC Enterprise and the Microsoft Desktop Optimization Pack.
That is a long list, and all of it is in E3. If a vendor slide shows any of these items under an E5 heading, it is describing a Microsoft 365 suite, not the Windows subscription.
What Windows Enterprise E5 adds: Defender for Endpoint Plan 2
The E5 uplift is a security service, not a Windows feature. The licensing page calls it a post-breach layer of protection: client technology built into Windows plus a cloud service that detects threats which got past other defences, gives you information to investigate the breach across endpoints, and offers response recommendations.
So the honest way to frame Windows Enterprise E3 vs E5 is as a Defender question. If you already license Defender for Endpoint Plan 2 some other way, Windows E5 buys you nothing extra on the Windows side. If you have no endpoint detection and response at all, it may be a sensible route to it for users who only need Windows. The detail of what Defender for Endpoint Plan 2 adds over Plan 1 is where the real decision sits, and it is worth reading before the Windows SKU question.
Which E3 features still need the Enterprise edition on the device
A user licence does not always mean the device runs Enterprise. Microsoft’s licensing page accepts that some devices stay on Pro: machines that were not provisioned properly and never upgraded, devices bought outside IT, vendor laptops added for a project, developers who must test on Pro, and devices certified on Pro only. It says the E3 subscription does not block those scenarios, and that many of its capabilities are not always technically enforced.
The same page then lists which features work on a Pro device covered by the user subscription. These rows are the ones that decide whether the edition change matters:
| Feature | Windows Pro with E3 user licence | Windows Enterprise edition |
|---|---|---|
| Credential Guard | Not available | Available |
| Personal Data Encryption | Not available | Available |
| Windows Experience customization | Not available | Available |
| Organizational messages | Not available | Available |
| 36 months support on annual feature releases | Not available | Available |
| Autopatch, Universal Print, Connected Cache, proactive remediation | Available | Available |
| Modern BitLocker Management, DirectAccess, Always On VPN | Available | Available |
The practical reading: paying for E3 while devices sit on Pro still buys Autopatch, Universal Print and proactive remediation, but it does not buy Credential Guard or the longer servicing window. Those need the edition to actually change on the device.
Subscription activation is how the device becomes Enterprise
The step from Pro to Enterprise is done by Windows subscription activation, not by reimaging. The Deploy Windows Enterprise licenses page on Microsoft Learn sets out the prerequisites:
- The device runs a supported, licensed version of Windows Pro.
- The device is Microsoft Entra joined, or hybrid joined with Microsoft Entra Connect. Customers federated with Microsoft Entra ID are also eligible.
- On-premises Active Directory identities are synchronised to Microsoft Entra ID, so each user has a single identity for on-premises apps and cloud services such as the Windows subscription.
- The licence is assigned per user. The page states plainly that subscription activation does not work with per device licensing.
- The licence reaches the user through group-based licensing where the required Microsoft Entra subscription is available, which the page calls the preferred method, or through the Microsoft 365 admin center, a spreadsheet upload or PowerShell.
Enterprise Agreement customers order a zero-cost SKU per user to provision subscription licences on the tenant. The page lists AAA-51069 for the E3 add-on and AAA-51068 for the E5 add-on, and notes that subscription activation under an EA is not currently available for GCC High or DoD tenants.
The newsletter
Get the next licensing fix like this one by email
Subscribe and get the free 8-page Intune troubleshooting field guide (PDF), then new fixes about twice a month. From a Microsoft MVP.
Where E5 makes sense, and where it does not
Buy Windows Enterprise E5 for a user when all three of these hold: the user needs Windows Enterprise rights, the user is not already covered for Defender for Endpoint Plan 2 by another licence, and your security team will actually work the alerts Plan 2 raises. If the third condition fails, E5 is money spent on a console nobody opens.
Stay on E3 when Defender for Endpoint comes from somewhere else, when your endpoint detection and response tool is not Microsoft’s, or when the users in question are on Microsoft 365 suites that already settle the Windows rights. For smaller organisations under the 300-user cap the comparison usually happens one level up, in Business Premium vs E5 and what the step up buys, rather than at the Windows SKU.
Both subscriptions are per user, so mixing them in one tenant is a licence assignment exercise rather than a technical one. A security team that wants Plan 2 coverage for administrators and high-risk roles first can assign E5 to those users and E3 to everyone else. Check the mixed-licensing terms for Defender with your licensing partner before you rely on that split.
Windows Enterprise E3 vs E5 failure modes
- The licence is assigned and the device stays on Pro. Subscription activation depends on the licensed Microsoft Entra user on an Entra joined or hybrid joined device. A device that is not joined, or used by someone with no licence, is where I would expect the step-up to stall, and Credential Guard never arrives.
- Per device licensing meets subscription activation. The Learn page is explicit that subscription activation requires per user licensing. A per device agreement and a cloud step-up plan do not combine.
- Application Guard is still on the feature list. The licensing page lists Microsoft Defender Application Guard for Microsoft Edge as an Enterprise feature. The Application Guard overview on Microsoft Learn says it is deprecated for Microsoft Edge for Business and is no longer available from Windows 11, version 24H2. Do not justify E3 on it.
- Frontline users expect the full E3 rights. The Windows Enterprise E3 that comes with Microsoft 365 F3 has all the OS features but not the Microsoft Desktop Optimization Pack, Windows LTSC Enterprise or Windows Autopatch. A kiosk design that assumes Autopatch or LTSC needs a different licence.
- E5 is bought and Defender is never onboarded. The licence grants Plan 2; it does not onboard devices. Until onboarding is done, Plan 2 is on the invoice and not on the endpoint.
What I would do differently
I would settle the Defender question before touching the Windows SKU. Count who is already covered for Defender for Endpoint Plan 2, through any bundle, and the Windows E5 list may shrink to almost nothing.
I would audit editions, not just licences. A report of devices still on Pro shows where E3 is being paid for without Credential Guard or the longer servicing window. Fixing the join state and the sign-in is usually cheaper than buying anything new.
I would strike retired features out of the business case. Application Guard is the obvious one today, and the licensing page has not caught up. A feature list is only useful if every line on it still ships.
And I would re-read the Windows Commercial Licensing overview at every renewal. It is the page most comparison grids are copied from, and the version you sign against is the one on your agreement, not the one in this post. If Intune add-ons are on the same order, Intune Plan 1 vs Plan 2 is the other per user question worth settling in the same review.
Last verified: 4 November 2026.



