---
title: Azure AD
description: ''
slug: /help/docs/integrations/automation-integrations/azure-ad/
canonical: https://www.sumologic.com/help/docs/integrations/automation-integrations/azure-ad/
---
import useBaseUrl from '@docusaurus/useBaseUrl';
***Version: 1.17
Updated: Sep 3, 2026***
[Microsoft Entra ID](https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-id), formerly known as Azure Active Directory (Azure AD), is an identity and access management solution from Microsoft that helps organizations secure and manage identities in cloud and on-premises environments.
## Authentication modes
The integration supports two authentication types, configured via the **Authentication Type** field in the integration resource:
| Mode | When to use |
|:------|:----------|
| **Application (Client Credentials)** | Uses `client_id` + `client_secret`. Works for all standard actions except **Reset User Password With Writeback**. |
| **Delegated (Device Code Flow)** | Actions that require a signed-in user's context, such as **Reset User Password With Writeback**, which requires the Privileged Auth Admin role. Tokens are scoped to the user who completes the browser sign-in. |
Use **Application** for most automation. Use **Delegated** only when Microsoft requires user context for the target operation.
## Actions
* **Add Member To Group** *(Enrichment)* - Add a user to a specific group.
* **Confirm User Compromised** *(Containment)* - Confirm a user as compromised in Azure AD Identity Protection.
* **Create Group** *(Enrichment)* - Create a group.
* **Create User** *(Enrichment)* - Create a new user.
* **Delete Group** *(Containment)* - Delete a specific group.
* **Delete User** *(Containment)* - Delete a specific user.
* **Disable User** *(Containment)* - Block user account.
* **Dismiss Risky User** *(Containment)* - Dismiss the risk for a specific risky user.
* **Enable User** *(Containment)* - Enable a specific user account.
* **Exchange Device Code** *(Custom)* - Polls Microsoft until the user completes browser sign-in and returns tokens. (Delegated auth only.)
* **Get Manager** *(Enrichment)* - Get user manager.
* **Get Member Groups** *(Enrichment)* - Retrieve group memberships for the user.
* **Get Risky User** *(Enrichment)* - Retrieve risk details for a specific user.
* **Get User** *(Enrichment)* - Get details for a specific user.
* **Initiate Delegated Auth** *(Enrichment)* - Starts the Device Code Flow by calling Microsoft's `/oauth2/v2.0/devicecode` endpoint. Returns `user_code`, `verification_uri`, `device_code`, `interval`, `expires_in`, and `message`. (Delegated auth only.)
* **List Devices** *(Enrichment)* - Retrieve a list of device objects registered in the organization.
* **List Groups** *(Enrichment)* - List all the groups available in an organization.
* **List Of Group Members** *(Enrichment)* - Retrieve a list of members in a specific group.
* **List Risky Users** *(Enrichment)* - Retrieve a list of risky users detected by Azure AD Identity Protection.
* **List Users** *(Enrichment)* - List all users.
* **Remove Member From Group** *(Containment)* - Remove a user from a specific group.
* **Reset User MFA** *(Containment)* - Reset the MFA authentication methods for a user, with an option to require re-enrollment at next sign-in.
* **Reset User Password** *(Containment)* - Reset user password.
* **Reset User Password With Writeback** *(Containment)* - Resets a user's password with writeback to on-premises AD. (Delegated auth only) — Microsoft does not support application permissions for this endpoint.
* **Revoke Sign In Sessions** *(Containment)* - Invalidates all the refresh tokens issued to applications for a user (as well as session cookies in a user's browser).
## Azure Active Directory configuration
The following steps show how to create an Azure AD Application in order to work with Sumo Logic automation.
1. Log in to the Azure portal with the user who has administrator privileges.
1. Navigate to **Azure Active Directory** > **App registrations** > **New registration**.
1. In the registration form, choose a name for your application and then click **Register**.
1. Write down the Application ID and Directory ID. You will need them later for the integration configuration.
1. To configure Azure AD Application permissions, on the left, choose **API permissions**.
1. Click the **Add a permission** button.
1. Select your application in App registrations in the Azure portal. Application permissions are for service or daemon-type applications that need to access the API as themselves, without user interaction for sign-in or consent.
1. Select the following **Application** permissions to add: `Device.ReadWrite.All`, `Directory.Read.All`, `Directory.ReadWrite.All`, `Group.ReadWrite.All`, `GroupMember.ReadWrite.All`, `IdentityRiskyUser.ReadWrite.All`, `User-PasswordProfile.ReadWrite.All`, `User.EnableDisableAccount.All`, `User.Read.All`, `User.ReadWrite.All`, `User.RevokeSessions.All`, `UserAuthenticationMethod.ReadWrite.All`.
1. Once API permissions are added, then Admin must consent to grant these permissions ([Learn more about permissions and consent](https://docs.microsoft.com/azure/active-directory/develop/v2-permissions-and-consent?WT.mc_id=Portal-Microsoft_AAD_RegisteredApps).)
1. Once Admin Consent is granted, API permissions configuration has been completed. Then we have to add a Client secret for authentication, along with the Client ID and Directory ID. To add a client secret, go to Certificates and secrets, and click **New client secret**.
1. Select the description and expiry period for the created secret and create it.
1. Once it's created, make sure you save its value, since it's only displayed once.
1. Once you do these steps, you will need to find the Tenant ID in order to use it on your resources file.
1. Once the Azure AD application is configured, you will need the application's Client ID, secret, and Tenant ID.
1. Assign the app the role of User Administrator. This is required to perform the **Reset User Password** action.
* **Azure Active Directory** > **Roles and administrators** > **User Administrator** > **Add assignments** > **Your app** > **Add**.
## Delegated auth setup (one-time)
Complete this setup once to enable delegated actions such as **Reset User Password With Writeback**. After setup, playbooks run automatically using the stored refresh token — no repeat browser sign-in needed.
**Prerequisite**: The signed-in user must hold the **Privileged Auth Admin** role in Azure AD.
1. In the integration resource, set **Authentication Type** to **Delegated**.
1. Run **Initiate Delegated Auth**. Note the `user_code` and `verification_uri` from the output.
1. Open the `verification_uri` in a browser, enter the `user_code`, and complete sign-in as the privileged user.
1. Run **Exchange Device Code** with `device_code` mapped from step 2. The action polls until sign-in completes (default timeout: 90s).
1. Copy the `refresh_token` from the **Exchange Device Code** output.
1. Paste the `refresh_token` into the **Delegated Refresh Token** field in the integration resource and save.
The integration is now ready for automated use. Re-authentication is only needed if the token is unused for 90 days or an admin explicitly revokes it.
**Token reference:**
| Token | Lifetime | Notes |
|-------|----------|-------|
| `access_token` | 60–90 minutes | Short-lived; obtained during the Exchange Device Code step |
| `refresh_token` | 90-day sliding window | Resets on each use; survives multiple access token exchanges |
## Configure Azure AD in Automation Service and Cloud SOAR
import IntegrationsAuth from '../../reuse/integrations-authentication.md';
import IntegrationCertificate from '../../reuse/automation-service/integration-certificate.md';
import IntegrationEngine from '../../reuse/automation-service/integration-engine.md';
import IntegrationLabel from '../../reuse/automation-service/integration-label.md';
import IntegrationProxy from '../../reuse/automation-service/integration-proxy.md';
import IntegrationTimeout from '../../reuse/automation-service/integration-timeout.md';
*
* **API URL**. Enter the Azure AD API URL, for example, `https://graph.microsoft.com`
* **Directory (Tenant) ID**. Enter the [tenant ID](https://learn.microsoft.com/en-us/entra/fundamentals/how-to-find-tenant) located when you configured Azure AD [above](#azure-active-directory-configuration).
* **Application (Client) ID**. Enter the client ID from your Azure Application.
* **Application (Client) Secret**. Enter your client secret.
* **Authentication Type**. Select `Application` (default) for client credential auth, or `Delegated` to enable Device Code Flow actions.
* **Delegated Refresh Token**. Paste the refresh token obtained during the [delegated auth setup](#delegated-auth-setup-one-time).
*
*
*
*
For information about Microsoft Entra ID (formerly Azure AD), see [Entra ID documentation](https://learn.microsoft.com/en-us/entra/identity/).
## Change Log
| Version | Date | Description |
|:--|:--|:--|
| v1.17 | September 3, 2026 | - Added Delegated (Device Code Flow) authentication support alongside existing Application (Client Credentials) auth.
- Added new actions (Delegated auth only): **Initiate Delegated Auth**, **Exchange Device Code**, and **Reset User Password With Writeback**.
- Added new integration resource fields: Authentication Type, Delegated Refresh Token.
|
| v1.15 | July 31, 2026 | - Added new actions: **Confirm User Compromised**, **Dismiss Risky User**, **Enable User**, **Get Risky User**, and **List Risky Users**.
- Improved integration reliability, enhanced error handling, better edge case support, and more user-friendly error messages.
|
| v1.14 | May 7, 2026 | Fixed an issue in the Reset User Password and Remove Member From Group actions that caused errors when processing the response. |
| v1.12 | May 7, 2026 | Added a new action: **Reset User MFA**. |
| v1.11 | April 27, 2026 | Upgraded the `python3_generic` Docker image (Python 3.8) to `python3_12_generic` (Python 3.12) to address Python 3.8 end-of-life and improve security and performance. |
| v1.10 | January 3, 2025 | Added new actions: **List Of Group Members** and **Remove Member From Group**. |
| v1.9 | November 12, 2024 | Added a new action: **Reset User Password**. |
| v1.8 | January 16, 2024 | Added a new action: **Get Member Groups**. |
| v1.7 | September 19, 2023 | Versioning. |
| v1.6 | August 31, 2023 | Added new actions: **List Devices** and **Disable User**. |
| v1.5 | August 25, 2023 | Added a new action: **Revoke Sign In Sessions**. |
| v1.4 | June 26, 2023 | Changed multiline hints to single line. |
| v1.3 | April 28, 2023 | - Updated integration (updated the integration fields with environmental variables and improved error handling).
- Removed action **Filter Users** as we already have a similar **List Users** action.
- Changed a few action types from Containment to Enrichment.
- Added a new action: **List Groups**.
|
| v1.2 | November 10, 2022 | Added a new action: **Get Manager**. |
| v1.1 | March 11, 2022 | Updated the logo in Azure AD integration. |
| v1.0 | October 7, 2021 | Initial release of the Azure AD integration. |
## Additional resources
For Azure AD, Sumo Logic provides the following sources for collecting data and corresponding apps for visualizing it:
- Use the [Microsoft Azure AD Inventory source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/microsoft-azure-ad-inventory-source/) to collect Azure AD Inventory data and the [Microsoft Azure AD Inventory app](/docs/integrations/saas-cloud/microsoft-azure-ad-inventory/) to visualize it.
- Use the [Microsoft Graph Azure AD Reporting source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/microsoft-graph-azure-ad-reporting-source/) to collect Azure AD reporting data and the [Microsoft Graph Azure AD Reporting app](/docs/integrations/saas-cloud/microsoft-graph-azure-ad-reporting/) to visualize it.