# Microsoft Entra ID Protection risk events are flowing to the Microsoft Sentinel workspace

Microsoft Entra ID Protection generates risk signals for both user accounts and workload identities (service principals).

Source: https://maester.dev/docs/tests/ZTA.61016

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

## Overview

Microsoft Entra ID Protection generates risk signals for both user accounts and workload identities (service principals). For AI workloads, the workload identity signals are especially important — they detect unusual authentication patterns and suspicious API activity by the service principals that run as AI agents. This check verifies that both user and workload identity risk event categories are enabled on the Entra ID data connector and flowing to the Sentinel workspace.

When Identity Protection risk events are not flowing to Sentinel, the workspace has no risk dimension for the agent service principals that authenticate to AI endpoints. Threat actors who steal or replicate a service principal credential can exploit this gap because their anomalous sign-in and API activity never reaches the SIEM as a risk signal. Without these events, the organization cannot correlate a high-risk service principal identity with the downstream AI workload access that follows it.

## Remediation

- [Connect Microsoft Entra ID Protection to Microsoft Sentinel](https://learn.microsoft.com/azure/sentinel/data-connectors/microsoft-entra-id-protection)
- [Integrate Microsoft Entra logs with Azure Monitor logs](https://learn.microsoft.com/entra/identity/monitoring-health/howto-integrate-activity-logs-with-azure-monitor-logs)
- [Microsoft Entra ID Protection risk policies](https://learn.microsoft.com/entra/id-protection/concept-identity-protection-risks)

## Run it

The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:

```powershell
Install-Module ZeroTrustAssessment -Scope CurrentUser
Connect-Maester
Invoke-Maester -Pack ZTA -SkipBuiltIn
```

Leave out `-SkipBuiltIn` to run Maester's own checks in the same run.

<details>
<summary>About this check</summary>

| | |
| --- | --- |
| Severity | High |
| Effort to fix | Low |
| Impact on users | Low |
| Pillar | AI |
| Category | AI Threat Detection |
| Product | [Azure](/docs/tests/products/azure) |
| Feature | Microsoft Sentinel |
| Area | Logging and detection |
| ATT&CK | [T1078.004](/docs/tests?mitre=T1078.004) Cloud Accounts |
| Licence | AAD_PREMIUM_P2&AGENT_365, AAD_PREMIUM_P2, AGENT_365 |
| Tenant | Workforce |

Product, feature, area and ATT&CK are Maester's: the assessment does not record them, so Maester keeps them in the pack's `taxonomy.json`.

</details>

<p class="mt-ms-note not-content"><svg class="mt-ms-note__logo" viewBox="0 0 21 21" aria-hidden="true"><rect width="10" height="10" fill="#f25022"/><rect x="11" width="10" height="10" fill="#7fba00"/><rect y="11" width="10" height="10" fill="#00a4ef"/><rect x="11" y="11" width="10" height="10" fill="#ffb900"/></svg><span>A Microsoft check, part of the <a href="/docs/tests/packs/zero-trust-assessment">Zero Trust Assessment</a> pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, <a href="/docs/tests/packs/zero-trust-assessment#licence">MIT licence</a>.</span></p>
