Content reviewed: 12 October 2026
Since July 2026, Microsoft 365 E3 also includes Intune Plan 2, Remote Help and Advanced Analytics. Microsoft 365 E5 and E7 add Endpoint Privilege Management, Cloud PKI and Enterprise Application Management. The Microsoft planning guide confirms this distribution. At renewal, however, knowing that the company owns E3 or E5 is insufficient. You need to identify the users with the qualifying suite, who will receive each capability and whether an existing add-on still covers a gap.
Which capabilities E3 and E5 cover
| Qualifying suite | Included capabilities | What this does not imply |
|---|---|---|
| Microsoft 365 E3 | Intune Plan 2, Remote Help, Advanced Analytics | E3 does not automatically add EPM, Cloud PKI or EAM |
| Microsoft 365 E5 / E7 | E3 capabilities plus EPM, Cloud PKI and Enterprise Application Management | One entitled user does not license the whole organisation |
| Other plan | Check the exact SKU; separate add-ons may be needed | The E3/E5 change does not itself extend Business Premium or EMS |
Do not confuse Microsoft 365 E3 with Office 365 E3. Standalone Intune Plan 1 is likewise not evidence of entitlement to every advanced capability. Check the specific terms for education, government and other specialised offers. The Intune licensing documentation distinguishes the base service, additional plans and user or device requirements.
Check entitlement, configuration and operation separately
A licence determines who may use a capability. Configuration determines who receives a policy and which permissions they hold. An operational test proves that the scenario works. A green portal status or visible menu replaces none of these checks. In a mixed E3/E5 environment, EPM can be available in the tenant while some users lack the required entitlement.
Keep a simple record for each capability: user or device, licence source, assigned service plans, policy target group, owner and verification date. Include shared computers and role changes. Dynamic groups can automate assignment, but their rules and processing delays belong in the test plan.
Remote Help: check both sides of support
Remote Help requires entitlement for both the helper and the user receiving support. Unlicensed administrator access to Intune is not permission to use remote support. The Remote Help plan also requires participants in the same tenant and appropriate RBAC permissions for the helper. An outsourced service desk therefore needs a separate review of identities, devices and its supported operating model.
Before replacing an existing tool, test representative platforms, access controls, session auditability and the modes you actually need. Attended support, unattended access and support for unenrolled devices have different prerequisites. A Remote Help entitlement alone does not establish that every mode fits your operation.
EPM: a device group is not a licence register
EPM allows users to work without permanent local-administrator rights while elevating approved tasks. Microsoft describes policies targeted at user or device groups. A technically valid policy assignment still needs an entitled population. Test secondary users of shared laptops and employees moving from E5 to E3.
The pilot should cover an approved installation, a denied task and an application with child processes. Record the purpose, owner and change process for each rule. This operational work remains necessary even when the capability no longer requires a separate purchase.
Check overlaps before renewal
| Situation | What to verify | Decision evidence |
|---|---|---|
| E3 with standalone Remote Help | Entitlement for helpers and sharers; required platforms | Covered-user list and successful pilot |
| E5 with standalone EPM or Cloud PKI | Who uses the add-on and has included entitlement | User, capability and renewal-date matrix |
| Business Premium with a small specialist group | Targeted add-on cost and scope versus changing the suite | Same population and contract period in both options |
| E3, E5, F3 and contractors | Exceptions, shared devices and entitlement source | Capability-level records rather than total licence count |
In a hypothetical company with 80 E3 users and 20 E5 users, you cannot treat EPM as included for all 100 people. First identify who uses it and their entitlement. Similarly, Remote Help licences for ten support staff do not by themselves cover every recipient of support. The budget model starts with benefiting people rather than purchased bundle totals.
A practical decision process
- 01
Export the current position
Record exact SKUs, assigned users, active service plans, standalone add-ons, trials and renewal dates
- 02
Build a capability matrix
Compare actual use with current entitlement; distinguish licence purchase from policy assignment
- 03
Run a representative pilot
Test a regular user, helper, shared device and an E5-to-E3 change
- 04
Plan the contract change
Cancel add-ons only after coverage and the contractual window are verified; update the service catalogue and support documentation
If an expected capability is missing, inspect the actual licence, assignment and service plans, policy targeting, supported platform and permissions. Use those findings when investigating tenant availability or contacting Microsoft support. The advanced capabilities overview helps identify the service involved; an old price list or menu screenshot does not prove coverage.
Frequently asked questions
Does Microsoft 365 E3 include the full Intune Suite scope?
E3 includes the selected capabilities listed here. In the current distribution, EPM, Cloud PKI and Enterprise Application Management belong to E5/E7 rather than E3 alone.
Does Office 365 E3 receive the same capabilities?
The E3 name does not establish this. Check the exact product and SKU; this guide concerns Microsoft 365 E3 and E5.
Can we cancel standalone add-ons immediately?
Only after checking all benefiting users, provisioning the included capabilities and confirming contract terms. The add-on may still cover another group.
Is a Remote Help licence for the helper sufficient?
No. The recipient also needs entitlement, and identity, device and RBAC requirements must be satisfied.
Was Business Premium automatically extended?
The July extension of these enterprise suites does not itself establish the same extension for Business Premium. Review its own scope and any required add-ons.








