EPM automation with Adaptive Cards transforms how IT teams handle elevation requests in Microsoft Intune. By combining Azure Logic Apps with Teams Adaptive Cards, you can automate the entire Endpoint Privilege Management (EPM) approval workflow, allowing approvers to act on requests without leaving Microsoft Teams. This EPM automation solution eliminates the need to constantly monitor the Intune portal.

What Is Endpoint Privilege Management?

Endpoint Privilege Management (EPM) is a feature in the Microsoft Intune Suite that allows organizations to manage and control local administrator rights on Windows devices — without granting permanent admin access. It enables rule-based and Just-In-Time (JIT) elevation, ensuring users can perform privileged tasks only when necessary, and only under defined conditions.

Rules-Based Elevation: Three Options

EPM supports three types of elevation rules:

1. Automatic Elevation — The application is elevated silently without user interaction, based on predefined rules.
2. User-Confirmed Elevation — The user is prompted to confirm the elevation request, typically with a business justification and/or Windows authentication.
3. Support-Approved Elevation — The user submits a request that must be approved by IT or support staff before elevation is granted. This is the model we focus on in this post, as it allows integration with Microsoft Teams for real-time approvals.

Just-In-Time Elevation with Support Approval

Support-approved elevation is ideal for organizations that want to maintain strict control over admin rights while still enabling flexibility for end users. When a user requests elevation, the request is logged and routed for approval. By integrating this process with Microsoft Teams using Azure Logic Apps, IT teams can receive instant notifications and respond quickly — without switching tools or missing critical requests.

Currently, when approved, these requests remain valid for 24 hours.

Benefits of Using EPM

Implementing Endpoint Privilege Management offers several key advantages:

• User Empowerment: Allows users to perform necessary tasks without waiting for manual intervention — when policies allow it.
• Improved Security: Reduces the attack surface by eliminating standing admin rights.
• Operational Efficiency: Automates elevation workflows and reduces helpdesk overhead.
• Compliance and Auditing: Provides detailed logs of elevation activity for auditing and compliance reporting.

The Challenge with Manual EPM Approvals

When EPM is configured in Microsoft Intune, end users can request elevation to run applications requiring administrator privileges. However, the traditional approval workflow requires IT administrators to:

1. Navigate to the Intune portal
2. Find the pending elevation request
3. Review the request details
4. Approve or deny the request

This process, while secure, creates friction, especially when approvers are busy with other tasks or aren’t actively monitoring the Intune console.

The result?

Delayed approvals and frustrated users waiting for elevated access.

Configuring EPM in Microsoft Intune

Before setting up the automation, you need an EPM elevation rules policy. In this example we enable the “Mark 8 Project Team” to request elevation for Wireshark. I am assuming here that EPM was already enabled in your tenant.

Start in Microsoft Intune and navigate to the Endpoint security blade. Under Endpoint Privilege Management go to Policies and create a new Elevation rules policy.

After going through the basics, fill in the detailed information about the application you are adding to the rule. This information can be collected using the EpmTools.dll.

Using this tool you can even extract publisher certificates from the file. These can be added to the reusable library.

Finally, fill in all the necessary details about the file.

Verify the configuration from a demo device. From the end-user perspective the Run with elevated access option should be visible, and the elevation request dialog should open.

For the Intune administrator, the request should appear in the Elevation requests tab almost immediately.

Verifying the Graph API Data

Before building the Logic App, confirm that elevation requests are visible through the Microsoft Graph API. Open the Graph Explorer and query deviceManagement/elevationRequests.

Make sure you are using the beta version of the API and that the DeviceManagementConfiguration.Read.All permission has been granted. Otherwise, the query returns a permission error.

How EPM Automation with Adaptive Cards Works

Our EPM automation solution bridges Microsoft Intune and Microsoft Teams by creating an automated workflow that:

• Polls for pending requests every 5 minutes using Microsoft Graph API
• Posts Adaptive Cards to a designated Teams channel with all request details
• Enables one-click approval or denial directly from Teams
• Updates the Adaptive Card to show the final decision and who made it

Architecture for EPM Automation

1. Logic App (Recurrence Trigger - every 5 minutes)
        │
        ├──> GET Microsoft Graph API
        │    /deviceManagement/elevationRequests
        │
        ├──> Filter requests with status = "pending"
        │
        ├──> For each pending request:
        │    └──> Post Adaptive Card to Teams channel
        │         ├──> Approve button
        │         └──> Deny button
        │
        └──> When button clicked:
             └──> POST approval/denial via Graph API
             └──> Update Adaptive Card with decision

Key Components of the EPM Automation Solution

Azure Logic App for EPM Automation

The Logic App serves as the orchestration engine for EPM automation. Using a recurrence trigger, it periodically queries the Microsoft Graph API for pending EPM elevation requests and processes each one by posting an interactive Adaptive Card to Teams.

Adaptive Cards for Approval Actions

The Adaptive Cards display comprehensive request information:

• Requester – Who’s requesting elevation
• Device Name – Which device the request originates from
• Application – The executable requesting elevation
• File Path – Where the application is located
• Publisher – The application’s publisher
• Justification – Why the user needs elevation

The card includes two action buttons: Approve (green) and Deny (red). Once clicked, the Adaptive Card updates to reflect the decision.

Managed Identity for Secure EPM Automation

Security is paramount. Instead of storing credentials or secrets, the EPM automation solution uses an Azure Managed Identity to authenticate to Microsoft Graph API. This eliminates secret management overhead and follows security best practices.

Microsoft Graph API Integration

The solution leverages the Graph API beta endpoint for EPM operations:

• GET /deviceManagement/elevationRequests – Retrieve pending requests
• POST /deviceManagement/elevationRequests/{id}/approve – Approve a request
• POST /deviceManagement/elevationRequests/{id}/deny – Deny a request

Infrastructure as Code with Bicep

The entire EPM automation solution is defined using Azure Bicep, making it reproducible and version-controllable. Here’s a simplified look at the main resources:

// Managed Identity for secure Graph API access
resource managedIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {
  name: '${logicAppName}-identity'
  location: location
  tags: tags
}

// Teams API Connection
resource teamsConnection 'Microsoft.Web/connections@2016-06-01' = {
  name: 'teams-connection'
  location: location
  properties: {
    displayName: 'Teams Connection for EPM Approval'
    api: {
      id: subscriptionResourceId('Microsoft.Web/locations/managedApis', location, 'teams')
    }
  }
}

// Logic App with workflow definition
resource logicApp 'Microsoft.Logic/workflows@2019-05-01' = {
  name: logicAppName
  location: location
  identity: {
    type: 'UserAssigned'
    userAssignedIdentities: {
      '${managedIdentity.id}': {}
    }
  }
  properties: {
    definition: loadJsonContent('workflow.json').definition
    // ... parameters
  }
}

Deploying Your EPM Automation with Adaptive Cards

A PowerShell deployment script automates the entire setup process:

# Deploy with default settings
.\deploy.ps1

# Or customize the deployment
.\deploy.ps1 -ResourceGroupName "rg-epm-approval" -Location "westeurope"

# Preview changes first
.\deploy.ps1 -WhatIf

The script handles:

• Prerequisites validation (Azure CLI, Bicep, login status)
• Resource group creation
• Bicep template deployment
• Graph API permission assignment via Microsoft Graph PowerShell
• Teams connection authorization prompt

Required Graph API Permissions

The Managed Identity needs the following application permissions:

Cost of EPM Automation

One of the best aspects of this EPM automation solution is its cost-effectiveness:

Total: ~$2-6/month depending on the number of requests processed.

Security Best Practices

The EPM automation solution follows security best practices:

• No secrets stored – Managed Identity handles authentication
• Least privilege – Only required Graph permissions are assigned
• Audit trail – All decisions are logged in both Intune and Logic App run history
• Secure outputs – Sensitive data is protected in Logic App runs

Extending the EPM Automation Solution

The modular design allows for easy extensions:

• Email notifications – Add email alerts for high-priority requests
• ServiceNow integration – Create tickets for tracking purposes
• Conditional logic – Auto-approve requests from specific applications
• Escalation workflows – Escalate unanswered requests after a timeout

Conclusion

EPM automation with Adaptive Cards transforms the approval experience from a portal-centric task into a seamless Teams-based workflow. Approvers can now handle elevation requests without context-switching, leading to faster response times and improved user satisfaction.

The solution is cost-effective (under $10/month), secure (no secrets, managed identity), and easy to deploy (Infrastructure as Code with automated deployment scripts).

Ready to implement EPM automation with Adaptive Cards in your environment? Check out the full source code and detailed deployment instructions on GitHub!

Sources

• Endpoint Privilege Management overview | Microsoft Learn
• Azure Logic Apps documentation | Microsoft Learn
• Adaptive Cards documentation | Microsoft Learn
• Microsoft Teams Connectors | Microsoft Learn
• Microsoft Graph API | Microsoft Learn
• Azure Managed Identities | Microsoft Learn
• Azure Bicep documentation | Microsoft Learn

The post EPM Approval Workflow: Adaptive Cards and Logic Apps appeared first on Jens Du Four.