- Print
- DarkLight
Azure AD is an identity and access management solution from Microsoft that helps organizations secure and manage identities for hybrid and multicloud environments.
Integration Method: API
Tables: Authentication
Event Types: input, api_input_signin, input_managed_identity, input_adfs, input_signin, input_unauth, input_service_principle_log
Setup and Configure
Log on to Azure with a user account that has the Global Administrator role.
Navigate to Microsoft Entra ID > App registrations > New registration. The “Register an application” page window appears.
Enter the application's registration information:
In the ‘Name’ section, enter a meaningful application name that will be displayed to users.
For ‘Supported account types’, click the Accounts in any organizational directory option.
Set the ‘Redirect URI’ to http://localhost.
Click on Register to create the application.
On the app “Overview” page, copy the ‘Application (client) ID’ and ‘Directory (tenant) ID’ for later use.
Add Endpoint Access
Once the application is created, appropriate permissions should be provided to get data. The appropriate permissions to the application are needed to configure these endpoints. The following section details how to configure and add permissions to the sign-in endpoint.
Endpoint needed for Azure AD Sign-in
Add Permissions
To add permissions for the endpoint outlined above, from the Azure Active Directory portal:
Select the application whose logs are to be accessed (generally, the application registered earlier on this page).
Click API Permissions, and then click Add a Permission. The “Request API permissions” window appears.
Click on Microsoft Graph.
Click on Application Permissions.
The following permissions need to be granted for the endpoint to function properly:
Endpoints
Permission
Directory.Read.All
In the ‘Select permissions’ search bar, enter the permissions shown above, and check the box to include it. If you run into any problems, check out Microsoft's official documents.
Click the Add permissions button after selecting all required permissions.
On the “API permissions” page, click Grant Admin Consent for <tenant>.
Click the Yes button on the consent confirmation. The required permissions are now added for the endpoints.
In the end, you must have the following permissions set for Microsoft Graph.
Create the Client ID and Client Secret
The final step in configuring the Graph API is creating a Client ID and Client Secret. To create these items, from the Azure Portal:
Select the application created above.
Click Certificates & secrets, and then Client Secrets.
Click New client secret. The “Add a client secret” window appears.
Enter a ‘Description’ for this client secret.
Select the desired expiry period from the ‘Expires’ drop-list.
Click Add.
Copy the ‘Value’ field, which will be used to initialize the beat.