Skip to content

Commit abf2619

Browse files
WIP
1 parent 989e2ac commit abf2619

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/active-directory/identity-protection/howto-export-risk-data.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: identity-protection
88
ms.topic: how-to
9-
ms.date: 07/30/2021
9+
ms.date: 02/18/2022
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
1313
manager: karenhoran
14-
ms.reviewer: sahandle
14+
ms.reviewer: sahandle, etbasser
1515

1616
ms.collection: M365-identity-device-management
1717
---
@@ -26,7 +26,7 @@ Azure AD stores reports and security signals for a defined period of time. When
2626
| Azure AD MFA usage | 30 days | 30 days | 30 days |
2727
| Risky sign-ins | 7 days | 30 days | 30 days |
2828

29-
Organizations can choose to store data for longer periods by changing diagnostic settings in Azure AD to send **RiskyUsers** and **UserRiskEvents** data to a Log Analytics workspace, archive data to a storage account, stream data to an Event Hub, or send data to a partner solution. Find these options in the **Azure portal** > **Azure Active Directory**, **Diagnostic settings** > **Edit setting**. If you don't have a diagnostic setting, follow the instructions in the article [Create diagnostic settings to send platform logs and metrics to different destinations](../../azure-monitor/essentials/diagnostic-settings.md) to create one.
29+
Organizations can choose to store data for longer periods by changing diagnostic settings in Azure AD to send **RiskyUsers**, **UserRiskEvents**, **RiskyServicePrincipals**, and **ServicePrincipalRiskEvents** data to a Log Analytics workspace, archive data to a storage account, stream data to an Event Hub, or send data to a partner solution. Find these options in the **Azure portal** > **Azure Active Directory**, **Diagnostic settings** > **Edit setting**. If you don't have a diagnostic setting, follow the instructions in the article [Create diagnostic settings to send platform logs and metrics to different destinations](../../azure-monitor/essentials/diagnostic-settings.md) to create one.
3030

3131
[ ![Diagnostic settings screen in Azure AD showing existing configuration](./media/howto-export-risk-data/change-diagnostic-setting-in-portal.png) ](./media/howto-export-risk-data/change-diagnostic-setting-in-portal.png#lightbox)
3232

@@ -38,6 +38,8 @@ Once enabled you will find access to Log Analytics in the **Azure portal** > **A
3838

3939
- AADRiskyUsers - Provides data like the **Risky users** report in Identity Protection.
4040
- AADUserRiskEvents - Provides data like the **Risk detections** report in Identity Protection.
41+
- RiskyServicePrincipals - Provides data like the **Risky workload identities** report in Identity Protection.
42+
- ServicePrincipalRiskEvents - Provides data like the **Workload identity detections** report in Identity Protection.
4143

4244
[ ![Log Analytics view showing a query against the AADUserRiskEvents table showing the top 5 events](./media/howto-export-risk-data/log-analytics-view-query-user-risk-events.png) ](./media/howto-export-risk-data/log-analytics-view-query-user-risk-events.png#lightbox)
4345

0 commit comments

Comments
 (0)