In the following, you’ll learn how to ingest sign-in logs from your Microsoft Entra ID instance into Grail and monitor them on the Dynatrace platform.
There are two ways to enable Entra ID sign-in logs forwarding to Dynatrace:
See below for details.
Microsoft Entra ID continuously exports sign-in logs to Azure Event Hubs.
An Azure Function app pre-processes the logs and sends them to Dynatrace, taking advantage of the OpenPipeline dedicated log ingest endpoint.
The fetched data is mapped to the Dynatrace Semantic Dictionary.
Data is stored in Grail in a unified format, in a default bucket called default_logs
. For details, see Built-in Grail buckets.
Enable Entra ID sign-in logs forwarding to Dynatrace via either of the two options:
To set up Microsoft Entra ID sign-in log monitoring, follow the steps below.
In Dynatrace, go to Settings > Process and contextualize > OpenPipeline and select Logs.
Go to Pipelines and select Pipeline.
Under Processing, select Processor > Technology bundle > Azure Entra ID Audit Logs.
Select Choose.
Enter a name for your Azure pipeline and select Save.
Under Dynamic routing, select Dynamic route.
Enter the following matching condition:
matchesValue(cloud.provider, "azure") ANDmatchesPhrase(content, "\"SignInLogs\"")
Select the newly created pipeline, enter a name for the Dynamic route, and select Add.
Verify the configuration by running the following query in Notebooks:
fetch logs| filter cloud.provide == "azure"AND isNotNull(audit.action)AND isNotNull(authentication.is_multifactor)
Download our sample dashboard from GitHub.
Open Dashboards, select Upload, then select the downloaded file.
With the ingested data, you can leverage Dynatrace platform to monitor your Microsoft Entra ID sign-in activity and access to business-critical organization applications, spotting anomalies and staying ahead of potential threats. For details, see Monitor suspicious sign-in activity with Dynatrace.