Content reviewed: 12 October 2026
Removing local administrator rights looks simple until finance must update a token driver, a developer needs a signed installer and support has to repair a service. Microsoft Intune Endpoint Privilege Management (EPM) lets a standard user elevate a specific file rather than the whole session. The benefit does not come from merely enabling the agent. It depends on rule quality, the operating model for unknown applications and evidence that an approved executable does not launch unexpected child processes. A weak EPM design simply moves the queue from administrator passwords into a different console.
EPM elevates a process, not the user
When a rule matches, EPM runs the target in an administrative context. Except for Elevate as current user, it uses a virtual account that separates the elevated action from the user profile. The application nevertheless receives full administrative capability on the device. EPM is therefore not safe simply because the employee remains a Standard User. Every allowed EXE, MSI, script and descendant chain is a decision to trust that code with system change.
Four elevation modes serve different risks
| Mode | Good fit | Main risk |
|---|---|---|
| Automatic | Frequent, stable and precisely verified binary | Elevation without a conscious user action |
| User confirmed | Known tool launched from the context menu | Users may confirm by habit |
| Support approved | Unknown or exceptional file requiring review | Queue delay and no native admin alert |
| Elevate as current user | Application dependent on user profile and identity | More exposure of the user profile and token |
Microsoft warns that broad Automatic rules can materially affect security posture. User confirmed can require authentication, business justification or both. Support approved is useful for exceptions: a user submits the file and reason, then an administrator examines its metadata. Elevate as current user should be reserved for software that genuinely depends on the profile and fails under the virtual account; otherwise it gives up part of the isolation EPM is meant to provide.
Licensing and availability in 2026
The 2026 packaging update includes EPM in Microsoft 365 E5; the FAQ applies those E5 packaging changes to E7 too. Microsoft 365 E3 receives a different advanced-feature subset without EPM. For other plans, check the appropriate Intune Suite or EPM add-on and prerequisites. The 1 July pricing date does not prove activation in a particular tenant; verify entitlement and Message Center rollout notices.
Prove device and network readiness before the pilot
EPM supports 64-bit Windows including Arm64, requires Entra joined or hybrid joined devices and enrollment in Intune or Configuration Manager co-management. Windows 365 and single-session AVD are supported. Devices need clear line of sight to required endpoints without SSL inspection; otherwise policy and approval delivery can appear randomly delayed. Assigning an Elevation settings policy installs Microsoft EPM Agent Service under Program Files. Capture agent presence, version, network reachability and policy receipt in readiness evidence.
Separate rules, agent state and permissions
| Symptom | First check |
|---|---|
| Settings policy is Not applicable | Supported Windows version and build, not just 64-bit architecture. |
| Rule assigned, agent inactive | Receipt of an Elevation settings policy enabling EPM. |
| User cannot see approval | Policy delivery, no SSL inspection and the approval deadline. |
| Installer works, next stage fails | Child-process control and the child’s own rule. |
| Administrator cannot see or decide a request | View/Modify rights and RBAC scope. |
The device requirements list Entra joined/hybrid joined, Intune enrollment or co-management and supported builds. Windows 10 appearing in the list does not guarantee functionality after its ordinary support lifecycle ends; the documentation explicitly notes that boundary. Files on network shares are unsupported in rule definitions. Check received policies and effective settings rather than portal targeting alone.
Build rules from the strongest evidence
A hash identifies one exact file but changes with every update. A publisher certificate tolerates new versions while trusting a broader family of code; narrow it with product name, internal name, file description and minimum version where possible. File name or path alone is weak identity. A practical hierarchy uses hashes for stable sensitive tools, tightly constrained publisher rules for managed products and Support approved for everything else.
EPM rules require a file hash for Automatic elevation; this is a requirement, not just a recommendation. User confirmed and Elevate as current user can identify files through a certificate or hash. Updating the file changes its hash, so rule maintenance needs an update process. If argument conditions are configured, test the actual installation and runtime command lines: the same file with disallowed arguments may not elevate.
Child processes change the protection scope
An installer can launch a second MSI, service helper, updater or shell. If only the parent is elevated, the next step may prompt for UAC again. If every descendant is allowed, a trusted bootstrapper may become a launch path for unrelated code. Observe each pilot package as a process tree. Record parent, child, publisher, hash and required context. Extend a rule only to descendants that belong to the verified installation flow, and repeat the measurement after application updates.
Rule conflicts follow a fixed precedence
When matching rules are evaluated, Deny takes precedence. User targeting then outranks device targeting, hashes are the most specific identification, and additional attributes resolve specificity; remaining ties follow User confirmed, Elevate as current user, Support approved and Automatic. The planning guide also documents default enablement when Enable EPM conflicts. This precedence does not protect a child whose evaluation is skipped through inherited elevated parent context.
When a child Deny rule is skipped
| Option | Effect | Check |
|---|---|---|
| Require rule to elevate | The child needs its own matching rule, including Deny evaluation. | Test each subsequent installation stage. |
| Deny all | Children run without elevated context. | This does not automatically prevent them from launching. |
| Allow child processes to run elevated | Children inherit elevation; their rules, including Deny, are skipped. | A separate child Deny rule does not protect against this inheritance. |
The rule creation guide specifies this behaviour. Illustrative test: an allowed installer launches a tool with a Deny rule. The result can differ with the parent’s child-process control. Test the full tree and effective context; two apparently correct assignments alone do not prove blocking.
EPM does not remove local admin membership
The deployment workflow separates auditing, rule design and changes to the local administrators group. Agent installation and rules do not perform that final membership change. EPM also does not interfere with ordinary UAC actions by a local administrator. Keeping membership can leave another elevation route outside EPM. Verify managed and unmanaged elevations alongside effective membership.
Support approval needs an operating process around the portal
Grant View elevation requests for review, plus Modify elevation requests and the correct RBAC scope for approval or denial. Administrators do not automatically see requests outside their scope. Native alerts for new requests are currently absent. Approval initiates device sync and a user notification; support must communicate denials itself. Approval runs for a fixed 24 hours from the decision, without custom duration or early cancellation.
| Field | Why it matters |
|---|---|
| File and hash | Identifies the exact artifact |
| Publisher and signature | Establishes origin and integrity |
| User and device | Provides request and policy context |
| Business justification | Separates need from convenience |
| Process tree | Finds secondary installers and shells |
| Decision and owner | Supports audit and conversion into a managed rule |
The approval workflow applies permission to the requesting user and device. Illustrative timing: approval at 10:00, offline device receives it at 18:00. This does not start a new 24-hour interval; only the remainder from original approval is available. Record decision, delivery and Approval expiration. Requests are not restricted to the device’s primary user.
Network changes have a separate policy
If a worker only needs IPv4, IPv6 or DNS changes, an unrestricted administrative utility is unnecessary. Elevation system settings policy exposes selected changes through Company Portal → Help & support → System settings. Once received, that scenario can work offline; it does not mean new support approvals can be delivered offline. This separate policy type also requires enabled EPM.
Use telemetry to change the ruleset
During the first weeks, measure which files are elevated, where requests fail and approval lead time. A repeated legitimate request is a candidate for a narrow User confirmed rule; a one-off should remain an approval. An unsigned binary is not automatically malicious, but it needs deeper review. Also track the number of devices retaining standing local admin. Success is not more EPM rules; it is fewer permanent privileges without a growth in unresolved incidents.
Pilot real work, not only VIP users
- 01
Inventory elevation demand
Use logs, service-desk data and workshops to learn what truly needs admin
- 02
Remove avoidable demands
Fix packaging, installation or ACLs before creating an EPM rule
- 03
Choose a representative cohort
Include office work, specialists, development and remote devices
- 04
Start with deny and approval
Keep unknown files on support approval; automate only proven repetition
- 05
Test updates and offline states
Exercise new versions, descendants, restart, network loss and rollback
- 06
Remove local admin after evidence
Meet acceptance scenarios first, then monitor support impact
A decision framework for every new request
Ask first whether the application truly needs administrative rights; many internal tools can be corrected with a service, a narrower ACL or Intune packaging. If elevation remains necessary, verify origin, signature, reputation and process tree. Then assess frequency and blast radius. A common, tightly identified file may justify User confirmed; a stable machine operation may rarely justify Automatic; a profile dependency may justify Elevate as current user; uncertainty belongs in Support approved or Deny. Expire decisions regularly. A permanent ownerless rule is simply a new form of local admin.
What EPM does not replace
EPM does not replace patch management, application control, Defender, LAPS or Privileged Identity Management. It does not cover macOS and cannot prevent abuse of a legitimately allowed application when a rule is broad. Combine it with managed software delivery, Windows Defender Application Control or App Control for Business, security monitoring and a LAPS-protected local recovery account. EPM is a precise bridge between a standard user and one administrative task, not a universal privileged access platform.
Frequently asked questions
Is EPM included with Microsoft 365 E3?
Microsoft 365 E3 has a different advanced Intune subset without EPM. EPM is part of the 2026 E5/E7 expansion; for other plans, check add-ons, entitlement and service availability.
Does an administrator receive an email for a request?
Microsoft currently provides no native notification for a new support-approved request. Monitor the queue or build separate alerting.
How long does approval last?
A support approval lasts 24 hours. Its duration cannot currently be customized or revoked early.
Can EPM make the whole user an administrator?
No. It elevates a specific process under a rule, which is why its child processes matter.








