Treat these as five separate decisions rather than one upgrade. Since mid-2026 Microsoft has been rolling Remote Help, Advanced Analytics and Intune Plan 2 into Microsoft 365 E3, and adding Endpoint Privilege Management, Enterprise Application Management and Cloud PKI to E5, but tenants are provisioned gradually. Before planning anything, open Tenant administration > Intune add-ons in the Intune admin centre and see what your tenant is actually entitled to. Remote Help suits almost any organisation with a help desk. Advanced Analytics pays off only if someone will read it. Endpoint Privilege Management changes how you handle local admin rights, so pilot it in reporting mode first. Cloud PKI matters only if you issue certificates to managed devices. Plan 2 on its own matters mainly for specialist devices.
What your licence actually switches on
Intune licensing has three layers that people routinely blur together. Plan 1 is the base service. Plan 2 is an add-on to Plan 1 for a handful of specialist capabilities. The Intune Suite is a further add-on that includes Plan 2 and bundles the rest. Microsoft Entra ID P1 or P2, which you need for Conditional Access, is licensed separately again.
The bundling changed during 2026. Microsoft's June 2026 service release notes say Microsoft 365 E3 gains Plan 2, Remote Help and Advanced Analytics, and E5 gains everything in E3 plus Endpoint Privilege Management, Enterprise Application Management and Microsoft Cloud PKI. The rollout is gradual and Microsoft says it posts a notice in the Microsoft 365 admin centre 30 days before the change reaches a tenant. So the name on your invoice is a good starting point and a poor final answer.
Here is the entitlement picture as Microsoft currently describes it. Prices are deliberately left out because they vary by region, agreement and VAT treatment.
- Microsoft 365 E3 (commercial): Intune Plan 2 (Tunnel for MAM, specialty device management and Android firmware over-the-air updates), Remote Help and Advanced Analytics.
- Microsoft 365 E5: everything in E3, plus Endpoint Privilege Management, Enterprise Application Management and Microsoft Cloud PKI.
- Microsoft 365 E7: Microsoft's Intune product page says Intune Suite capabilities are included with E5 and E7, and Microsoft's licensing guidance describes E7 as including E5. Confirm on your add-ons page.
- Microsoft 365 Business Premium: Plan 1 and Entra ID P1. It is not named in Microsoft's E3 and E5 announcement, so assume the advanced capabilities are not included unless your add-ons page says otherwise.
- Education and frontline plans: Microsoft says this change does not alter them.
- Standalone Intune, EMS and other licences: Microsoft sells Remote Help, Endpoint Privilege Management, Enterprise Application Management, Advanced Analytics, Plan 2 and Cloud PKI as separate add-ons, with the full Suite available for organisations buying two or more at scale. Plan 1 is the base licence required to add any of them as of 1 July 2026.
- Trials: 90 days, up to 250 users per tenant, one trial per capability per tenant, followed by a 30-day grace period. After that the capability disappears from the admin centre.
Check what your tenant really has
Do this before reading any further plans into the headline licensing. It is read-only and changes nothing.
- Sign in to the Microsoft Intune admin centre as a Global administrator or Billing administrator. Other roles do not see the Your add-ons tab.
- Go to Tenant administration > Intune add-ons. The Capabilities tab shows what your tenant is eligible for. Your add-ons shows what is Active.
- Go to Tenant administration > Tenant status and open the Tenant details tab to see total licensed users and total Intune licences.
- In the Microsoft 365 admin centre, check Message Center for a notice about Intune Suite capabilities. Microsoft says it appears 30 days before the change takes effect in your tenant, so a missing notice can simply mean your tenant has not been reached yet.
- Check who is licensed, not just how many. Remote Help needs a licence for every helper and every sharer, so an E3 or E5 licence on the support team alone is not enough.
Which problem points at which feature
Start from the problem and work towards the feature, not the other way round. A licence you already hold is not a reason to deploy anything.
- Your support team asks users to read out error messages, or shares screens through a general meeting tool: look at Remote Help. Licence gate: E3 or above, or the add-on. Cost of entry is low and it is the easiest of the five to pilot.
- Many users run as local administrators, and you want that to stop without a flood of tickets: look at Endpoint Privilege Management. Licence gate: E5 or the add-on. This is a change to how people work, not just a setting.
- You issue certificates for Wi-Fi, VPN or device identity from an ageing on-premises certification authority: look at Cloud PKI. Licence gate: E5 or the add-on. Skip it if you issue no device certificates.
- You cannot explain why devices are slow, or whether last month's change made things worse: look at Advanced Analytics. Licence gate: E3 or above, or the add-on. It only helps if someone reviews the reports.
- You manage Teams Rooms-style devices, large smart screens or headsets, need Android firmware updates, or need Microsoft Tunnel for unenrolled devices: look at Plan 2.
- None of the above: stay on Plan 1 and spend the time on the basics from earlier in this series.
Plan 2: only if you own the devices it was built for
Microsoft's advanced capabilities page lists the specialist items that sit with Plan 2: over-the-air firmware updates for Android devices, management of AR and VR headsets, large smart-screen devices and conference room meeting devices, and Microsoft Tunnel for devices that are not enrolled in Intune. If you have none of those needs, the Plan 2 part of an E3 upgrade is a footnote.
One wrinkle to be aware of. Microsoft's licensing page describes Plan 2 as including Remote Help and Advanced Analytics, while the E3 release note lists them alongside Plan 2, and each feature's own page says it needs a subscription beyond Plan 1 or Plan 2. The practical answer is the same as before: let the Intune add-ons page in your tenant settle it, not the plan names.
Remote Help: usually the easiest win
Remote Help is a remote support tool built on your own Microsoft Entra accounts. Both the helper and the person being helped sign in with organisational accounts, support rights come from Intune role-based access control, and sessions appear in reports and audit logs. The trade-off is the tight boundary: it cannot cross tenants, so an outsourced help desk working from its own tenant cannot use it unless you issue them devices joined to your tenant or provide access through Windows 365 or Azure Virtual Desktop.
Decide early what level of control each support tier gets. View-only is the least intrusive. Full control and elevation (which lets the helper type credentials into UAC prompts on the user's device) are separate permissions, and Microsoft recommends granting the minimum each role needs. Unattended control is a further step again. On Windows it applies only to physical, corporate-owned, Intune-managed x64 devices that are Entra joined or hybrid joined, needs the Intune Management Extension and Remote Desktop enabled, and the device must be powered on and online. Treat it as a narrowly scoped role for senior staff.
Plan for the network too. Remote Help uses port 443 to Microsoft's Remote Assistance Service, and if your proxy performs SSL inspection the documented Remote Help domains need to be excluded. For helpers, require multifactor authentication through Conditional Access; Microsoft recommends this because helpers hold powerful access, and note that those policies cover Windows and macOS sessions a user accepts, not unattended access.
A first pilot with two machines and one helper account takes little time. Microsoft notes that new or trial licences can take between 30 minutes and 8 hours to become active, so a freshly licensed tenant may report that Remote Help is not enabled when it is. Give it time before troubleshooting.
- In the Intune admin centre, go to Tenant administration > Remote Help and open the Settings tab. Set Enable Remote Help to Enabled. Leave Allow Remote Help to unenrolled devices on its default of disabled unless you have a specific need to support personal devices, because those sessions come with less compliance and audit information. Select Save.
- Create a security group for pilot helpers and another for pilot devices. Then go to Tenant administration > Roles and assign the built-in Help Desk Operator role to the helper group, scoped to the pilot device group or users. A helper needs Remote Tasks - Offer remote assistance, Remote Assistance Connector - Read and at least one Remote Help app permission, and Help Desk Operator covers those. It does not include the Windows unattended control permission, which needs a custom role.
- Assign Remote Help licences to the helper account and the pilot user. Both need one.
- Install the current Remote Help app on the helper's machine and the pilot machine. Microsoft publishes the Windows download at aka.ms/downloadremotehelp.
- Start a session from the helper's Remote Help app, give the code to the pilot user and ask them to accept. Choose View only first, then try Request full control once you are happy the experience is clear to the user.
- Confirm it worked: the helper should see the user's screen, and the session should show up in Remote Help reports in the Intune admin centre and in Tenant administration > Audit Logs. To undo the pilot, set Enable Remote Help back to Disabled and remove the role assignment.
Endpoint Privilege Management: powerful, so start by listening
Endpoint Privilege Management (EPM) lets people run as standard users and still elevate specific tasks, such as installing a known application or running an approved script. Most elevations use a virtual account kept separate from the user's own account, and neither is added to the local Administrators group. It handles .exe, .msi and .ps1 files and is for Windows only.
Whether it suits you depends on how much local admin sprawl you have and whether you will maintain rules. Devices must be Entra joined or Entra hybrid joined, enrolled in Intune or co-managed, and running a 64-bit supported Windows build. Windows 11 24H2 is supported outright; older Windows 11 and Windows 10 builds need specific cumulative updates, and Windows 10 is only an allowed version after its end of support, so behaviour is not guaranteed. The required endpoints must be reachable without SSL inspection.
The risk sits in the rules. An automatic rule elevates without asking, and a rule based on a publisher certificate can allow every app signed by that certificate. Microsoft's guidance is to set the default elevation response to Require support approval or Deny all requests rather than Require user confirmation, because the latter lets any file be elevated. The Elevate as current user type runs under the user's own account and Microsoft says to use it only when virtual-account elevation breaks an application. Also specify a file path on rules where the folder is not writable by standard users.
The sensible first step is an audit-only pilot, which is also Microsoft's recommended first phase. It collects data without removing anyone's admin rights. Moving users from administrator to standard user, and building rules from the reports, are later phases.
The policy installs the EPM client on the device when assigned. Settings in this policy are device-wide even if you assign it to a group of users, so do not use separate settings policies to give different users different defaults. Reporting sends diagnostic and usage data to Microsoft, so check the data collection page before choosing a reporting scope.
- Make sure you have an Intune role that includes Endpoint Privilege Management Policy Authoring, such as the built-in Endpoint Privilege Manager role.
- Go to Endpoint security > Endpoint Privilege Management, open the Policies tab and select Create Policy. Set Platform to Windows and Profile to Windows elevation settings policy, then select Create.
- Name the policy so it is clearly the pilot one. On Configuration settings, leave Endpoint Privilege Management as Enabled and set Default elevation response to Deny all requests (or Require support approval if you want to try the approval flow). Keep Send elevation data for reporting as Yes with the default Reporting scope, which includes all endpoint elevations and is what shows you which files people actually elevate.
- On Assignments, choose your pilot device group only. Select Create. The EPM client is installed on devices at their next policy sync, so allow a little time before checking.
- On the pilot device, open PowerShell and import the EPM tools module that the agent installs. On Windows on Arm64, use Windows PowerShell x64.
Import-Module 'C:\Program Files\Microsoft EPM Agent\EpmTools\EpmCmdlets.dll' - Run Get-ClientSettings to display the effective client settings. You should see the settings from your policy. The Microsoft EPM Agent Service and the folder C:\Program Files\Microsoft EPM Agent should also exist, and right-clicking an executable should offer Run with elevated access.
Get-ClientSettings - To roll back, set Endpoint Privilege Management to Disabled in the policy. The client is deactivated on the next sync and its components are removed after seven days, which gives you time to restore it if this was a mistake.
Cloud PKI: decide on certificates before you click anything
A public key infrastructure (PKI) issues the certificates that devices use for Wi-Fi, VPN, email and device identity. Cloud PKI is Microsoft's hosted certification authority for Intune-managed devices. It replaces the on-premises authority, NDES server and Intune certificate connector that older designs needed, and it supports Windows, macOS, iOS/iPadOS and Android devices that are enrolled in Intune and can use a SCEP certificate profile. It needs a subscription on top of Plan 1 or Plan 2, which E5 now provides.
It suits you if you issue device certificates, want to retire servers you would rather not patch, and can live with its boundaries. You get up to three CAs per tenant, counting cloud root CAs, cloud issuing CAs and bring-your-own-CA issuing CAs. You can build a two-tier hierarchy in the cloud, or anchor an issuing CA to an existing private root such as one on Active Directory Certificate Services. Keys are RSA with sizes of 2048, 3072 or 4096 bits. Microsoft lists no data residency option for it.
The detail most likely to bite is the trial. CAs created during a trial use software-backed keys, and Microsoft says that after you buy a licence the keys stay software-backed and cannot be converted to HSM-backed keys. So a trial CA is for learning how the flow works, not for building the hierarchy you intend to keep.
Revocation also deserves care. Intune hosts the certificate revocation list, valid for seven days and republished every 3.5 days, and it is updated on every revocation. Reports refresh every 24 hours. A custom role can be given permission to revoke issued leaf certificates, so scope that permission tightly and revoke only what you intend to, because anything relying on that certificate will stop authenticating once the revocation is honoured.
If you pilot it, the documented sequence is: create the root and issuing CAs in the Intune admin centre, create and assign trusted certificate profiles for both CAs, then create and assign a SCEP certificate profile for each platform. The device receives the profiles at check-in, generates the key pair locally (the private key never leaves the device), and the SCEP service validates the request before the issuing CA signs it. Use a test device, a single test use of the certificate such as a Wi-Fi network, and confirm the certificate appears in the Cloud PKI reporting dashboard.
Advanced Analytics: useful if somebody reads it
Advanced Analytics extends endpoint analytics, Intune's built-in device experience reporting. It adds a resource performance report (CPU and RAM by device, model and manufacturer), battery health, anomaly detection that flags regressions after configuration changes, an enhanced device timeline, device query for near real-time device state, device query across multiple devices and device scopes that filter reports by scope tag. It supports Windows devices that are Intune-managed, co-managed, Entra joined or Entra hybrid joined.
Prerequisites matter more than the licence here. Devices must be enrolled and onboarded to endpoint analytics, and endpoint analytics must be configured in your tenant. Multi-device query also needs a properties catalog policy deployed. Once licensed, the features switch on automatically, but Microsoft says it can take up to 48 hours to appear after you buy licences or start a trial.
Be honest about whether you will use it. The anomalies report earns its keep when someone checks it after Windows updates or app deployments. Device query is data about people's machines, so decide who may use it, and read Microsoft's description of the data it captures before enabling it widely.
To check whether it has switched on, open the Intune admin centre and go to Reports > Endpoint analytics. With the feature active you should see the added reports, such as Resource performance, Battery health and Anomalies. If they are missing after 48 hours, recheck that the right users or devices are licensed and that devices are onboarded to endpoint analytics.
Technical terms explained
- Conditional Access
- A Microsoft Entra feature that applies access rules at sign-in, for example requiring multifactor authentication or a compliant device before allowing access to an app.
- endpoint analytics
- The Intune reporting area that scores device startup performance, app reliability and sign-in experience. Advanced Analytics adds extra reports and tools on top of it.
- HSM
- Hardware security module. A tamper-resistant system for generating and storing cryptographic keys. HSM-backed CA keys are harder to extract than software-backed ones.
- Intune Management Extension
- A Microsoft agent installed on Intune-managed Windows devices that handles tasks such as running scripts and installing Win32 apps. Remote Help uses it to deliver remote launch and unattended session requests.
- PKI
- Public key infrastructure: the certification authorities, policies and software used to issue, renew and revoke digital certificates that prove the identity of devices and users.
- SCEP
- Simple Certificate Enrollment Protocol. A method by which a device requests a certificate from a certification authority, with Intune supplying the profile and a one-time challenge that proves the device is managed.
- UAC
- User Account Control, the Windows prompt that asks for administrator approval or credentials before a task that changes the system.
Sources and further reading
- Microsoft Intune licensing plans and options - Microsoft Learn
- Microsoft Intune advanced capabilities - Microsoft Learn
- What's new in Microsoft Intune - Microsoft Learn
- Microsoft Intune product and licensing FAQ - Microsoft Security
- Use Remote Help to assist users authenticated by your organisation - Microsoft Learn
- Plan for Remote Help with Microsoft Intune - Microsoft Learn
- Deploy Remote Help with Microsoft Intune - Microsoft Learn
- Endpoint Privilege Management overview - Microsoft Learn
- Plan and prepare for Endpoint Privilege Management deployment - Microsoft Learn
- Deploy Endpoint Privilege Management with Microsoft Intune - Microsoft Learn
- Managing elevation settings for Endpoint Privilege Management - Microsoft Learn
- Microsoft Cloud PKI for Microsoft Intune - Microsoft Learn
- Microsoft Intune Advanced Analytics overview - Microsoft Learn
- Intune Remote Help: the deep dive now that it's included in your E5 - MSEndpointMgr
- Intune Suite now included in Microsoft 365 E3 and E5 - Admin365.Blog