Integrate Azure AD logs with Azure Monitor logs

Follow the steps in this article to integrate Azure Active Directory (Azure AD) logs with Azure Monitor.

Use the integration of Azure AD activity logs in Azure Monitor logs to perform tasks like:

  • Compare your Azure AD sign-in logs against security logs published by Microsoft Defender for Cloud.

  • Troubleshoot performance bottlenecks on your application’s sign-in page by correlating application performance data from Azure Application Insights.

  • Analyze Identity Protection risky users and risk detections logs to detect threats in your environment (public preview)

  • Identify sign-ins from applications that use the Active Directory Authentication Library (ADAL) for authentication. ADAL is nearing end-of-support.

This Microsoft Ignite session video shows the benefits of using Azure Monitor logs for Azure AD logs in practical scenarios:

Supported reports

You can route audit activity logs and sign-in activity logs to Azure Monitor logs for further analysis.

  • Audit logs: The audit logs activity report gives you access to the history of every task that's performed in your tenant.
  • Sign-in logs: With the sign-in activity report, you can determine who performed the tasks that are reported in the audit logs.
  • Provisioning logs: With the provisioning logs, you can monitor which users have been created, updated, and deleted in all your third-party applications.
  • Risky users logs (public preview): With the risky users logs, you can monitor changes in user risk level and remediation activity.
  • Risk detections logs (public preview): With the risk detections logs, you can monitor user's risk detections and analyze trends in risk activity detected in your organization.


To use this feature, you need:

  • An Azure subscription. If you don't have an Azure subscription, you can sign up for a free trial.
  • An Azure AD tenant.
  • A user who's a global administrator or security administrator for the Azure AD tenant.
  • A Log Analytics workspace in your Azure subscription. Learn how to create a Log Analytics workspace.

Licensing requirements

Using this feature requires an Azure AD Premium P1 or P2 tenant. You can find the license type of your tenant on the Overview page in Azure Active Directory.

Tenant information

If you want to know for how long the activity data is stored in a Premium tenant, see: How long does Azure AD store the data?

Send logs to Azure Monitor

  1. Sign in to the Azure portal.

  2. Select Azure Active Directory > Diagnostic settings -> Add diagnostic setting. You can also select Export Settings from the Audit Logs or Sign-ins page to get to the diagnostic settings configuration page.

  3. In the Diagnostic settings menu, select the Send to Log Analytics workspace check box, and then select Configure.

  4. Select the Log Analytics workspace you want to send the logs to, or create a new workspace in the provided dialog box.

  5. Do any or all of the following:

    • To send audit logs to the Log Analytics workspace, select the AuditLogs check box.
    • To send sign-in logs to the Log Analytics workspace, select the SignInLogs check box.
    • To send non-interactive user sign-in logs to the Log Analytics workspace, select the NonInteractiveUserSignInLogs check box.
    • To send service principal sign-in logs to the Log Analytics workspace, select the ServicePrincipalSignInLogs check box.
    • To send managed identity sign-in logs to the Log Analytics workspace, select the ManagedIdentitySignInLogs check box.
    • To send provisioning logs to the Log Analytics workspace, select the ProvisioningLogs check box.
    • To send Active Directory Federation Services (ADFS) sign-in logs to the Log Analytics workspace, select ADFSSignInLogs.
    • To send risky users logs to the Log Analytics workspace, select the RiskyUsers check box. (public preview)
    • To send risk detections logs to the Log Analytics workspace, select the UserRiskEvents check box. (public preview)
  6. Select Save to save the setting.

    Diagnostics settings

  7. After about 15 minutes, verify that events are streamed to your Log Analytics workspace.

Next steps