Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.3.1. Endpoint Privilege Management

💡 First Principle: Most users need admin rights for a handful of specific tasks, not for everything, so giving them local admin to install one driver is like handing over the master key to fix one lock. Endpoint Privilege Management (EPM) keeps everyone a standard user and elevates individual files that you've approved — which means the real design question is how precisely you identify a file, and what happens when no rule matches.

EPM is Windows-only: devices must be Entra joined or hybrid joined, enrolled in Intune or co-managed, and running a supported 64-bit Windows release (Windows 365 and single-session Azure Virtual Desktop included). It elevates .exe, .msi and .ps1 files, but not files on network shares. You manage it at Endpoint security > Endpoint Privilege Management.

How elevation works without admin rights. For most elevation types, EPM runs the file under a virtual account isolated from the user's own account; neither account is added to the local Administrators group. Users get a right-click option, Run with elevated access. The EPM client installs automatically when a device receives an elevation settings policy that enables EPM, and is removed seven days after EPM is disabled.

Three policy types:
  • Elevation settings policy turns EPM on, sets reporting, and sets the default elevation response. It's device-scoped even when assigned to a user group, so give per-user differences through rules instead.
  • Elevation rules policy identifies specific files and how each elevates, with up to 100 rules per policy. No rule works unless the device also has a settings policy that enables EPM.
  • Elevation system settings policy, still rolling out, lets standard users change IPv4, IPv6 and DNS settings.

Elevation types for a rule:

  • Automatic — elevates silently at every launch. Use sparingly, for trusted business-critical files. Automatic rules require a file hash and don't support wildcards.
  • User confirmed — the default for new rules. The user confirms a prompt, optionally with a business justification, Windows authentication or both.
  • Elevate as current user — runs under the user's own account rather than the virtual account, preserving profile paths and environment variables, and always requires Windows authentication. It has a broader attack surface, so use it only when virtual-account elevation breaks an app.
  • Support approved — the user submits a request and an admin approves it in the admin center.
  • Deny — blocks the file from running elevated.

Identifying files. A rule needs a file name and can add a path, a signing certificate, a hash, a minimum version and other attributes. File hash rules are the strongest EPM can create. A certificate rule lets any file signed by that certificate elevate, so pair it with other attributes (a standard user can rename files) and always set a file path standard users can't modify. Child process behavior defaults to Require rule to elevate; Allow all child processes to run elevated skips rule evaluation for children, including deny rules.

When rules conflict, EPM applies this order:

  1. A Deny rule always wins.
  2. Rules assigned to a user beat rules assigned to a device.
  3. A rule with a hash is the most specific.
  4. Otherwise, the rule with the most defined attributes wins.
  5. If still tied: User confirmed, then Elevate as current user, then Support approved, then Automatic.
  6. No matching rule and the user chose Run with elevated access: the default elevation response applies.

The default elevation response options are Deny all requests, Require support approval and Require user confirmation; Not Configured behaves as Deny. Microsoft recommends Deny or Require support approval, because Require user confirmation effectively lets every file elevate.

Support approvals. Requests appear on the Elevation requests tab, and Intune doesn't notify admins about them, so someone has to check. An approval lets that user run the file elevated for 24 hours, with no custom duration and no early cancel. A denial sends nothing to the user.

Reporting and roles. Report data is processed every 24 hours and kept for 30 days. Viewing EPM reports now requires the Endpoint Privilege Management Policy Authoring > View Reports permission; Device configurations > Read is no longer enough, and admins without it get an HTTP 403. Built-in roles are Endpoint Privilege Manager (full rights) and Endpoint Privilege Reader. Once users can elevate what they need, remove their admin rights with an account protection policy that manages local group membership.

⚠️ Exam Trap: Because the end result — an app running with admin rights — looks like local admin access, people assume EPM makes users local administrators. It doesn't. Users stay standard users; EPM elevates only the files an elevation rule matches (by hash or certificate, with automatic, user-confirmed or support-approved elevation), and anything else falls to the default elevation response.

Reflection Question: A device has a user-assigned rule that elevates a tool automatically by hash, and a device-assigned Deny rule for the same file. What happens when the user launches it, and how would your answer change if the device rule were User confirmed instead?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned