Skip to content

Commit 29693aa

Browse files
authored
Merge pull request #210959 from MarkusVi/mon110
mon110
2 parents 4ec825c + 900f8f6 commit 29693aa

File tree

2 files changed

+154
-5
lines changed

2 files changed

+154
-5
lines changed
Lines changed: 145 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,145 @@
1+
---
2+
3+
title: How to view applied conditional access policies in the Azure AD sign-in logs | Microsoft Docs
4+
description: Learn how to view applied conditional access policies in the Azure AD sign-in logs
5+
services: active-directory
6+
documentationcenter: ''
7+
author: MarkusVi
8+
manager: amycolannino
9+
editor: ''
10+
11+
ms.service: active-directory
12+
ms.topic: how-to
13+
ms.workload: identity
14+
ms.subservice: report-monitor
15+
ms.date: 09/14/2022
16+
ms.author: markvi
17+
ms.reviewer: besiler
18+
19+
ms.collection: M365-identity-device-management
20+
---
21+
22+
# How to: View applied conditional access policies in the Azure AD sign-in logs
23+
24+
With conditional access policies, you can control, how your users get access to the resources of your Azure tenant. As a tenant admin, you need to be able to determine what impact your conditional access policies have on sign-ins to your tenant, so that you can take action if necessary. The sign-in logs in Azure AD provide you with the information you need to assess the impact of your policies.
25+
26+
27+
This article explains how you can get access to the information about applied conditional access policies.
28+
29+
30+
## What you should know
31+
32+
As an Azure AD administrator, you can use the sign-in logs to:
33+
34+
- Troubleshoot sign in problems
35+
- Check on feature performance
36+
- Evaluate security of a tenant
37+
38+
Some scenarios require you to get an understanding for how your conditional access policies were applied to a sign-in event. Common examples include:
39+
40+
- **Helpdesk administrators** who need to look at applied conditional access policies to understand if a policy is the root cause of a ticket opened by a user.
41+
42+
- **Tenant administrators** who need to verify that conditional access policies have the intended impact on the users of a tenant.
43+
44+
45+
You can access the sign-in logs using the Azure portal, MS Graph, and PowerShell.
46+
47+
48+
49+
## Required administrator roles
50+
51+
52+
To see applied conditional access policies in the sign-in logs, administrators must have permissions to:
53+
54+
- View sign-in logs
55+
- View conditional access policies
56+
57+
The least privileged built-in role that grants both permissions is the **Security Reader**. As a best practice, your global administrator should add the **Security Reader** role to the related administrator accounts.
58+
59+
60+
The following built in roles grant permissions to read conditional access policies:
61+
62+
- Global Administrator
63+
64+
- Global Reader
65+
66+
- Security Administrator
67+
68+
- Security Reader
69+
70+
- Conditional Access Administrator
71+
72+
73+
The following built in roles grant permission to view sign-in logs:
74+
75+
- Global Administrator
76+
77+
- Security Administrator
78+
79+
- Security Reader
80+
81+
- Global Reader
82+
83+
- Reports Reader
84+
85+
86+
## Permissions for client apps
87+
88+
If you use a client app to pull sign-in logs from Graph, your app needs permissions to receive the **appliedConditionalAccessPolicy** resource from Graph. As a best practice, assign **Policy.Read.ConditionalAccess** because it's the least privileged permission. Any of the following permissions is sufficient for a client app to access applied CA policies in sign-in logs through Graph:
89+
90+
- Policy.Read.ConditionalAccess
91+
92+
- Policy.ReadWrite.ConditionalAccess
93+
94+
- Policy.Read.All
95+
96+
97+
98+
## Permissions for PowerShell
99+
100+
Like any other client app, the Microsoft Graph PowerShell module needs client permissions to access applied conditional access policies in the sign-in logs. To successfully pull applied conditional access in the sign-in logs, you must consent to the necessary permissions with your administrator account for MS Graph PowerShell. As a best practice, consent to:
101+
102+
- Policy.Read.ConditionalAccess
103+
- AuditLog.Read.All
104+
- Directory.Read.All
105+
106+
These permissions are the least privileged permissions with the necessary access.
107+
108+
To consent to the necessary permissions, use:
109+
110+
` Connect-MgGraph -Scopes Policy.Read.ConditionalAccess, AuditLog.Read.All, Directory.Read.All `
111+
112+
To view the sign-in logs, use:
113+
114+
`Get-MgAuditLogSignIn `
115+
116+
The output of this cmdlet contains a **AppliedConditionalAccessPolicies** property that shows all the conditional access policies applied to the sign-in.
117+
118+
For more information about this cmdlet, see [Get-MgAuditLogSignIn](https://docs.microsoft.com/powershell/module/microsoft.graph.reports/get-mgauditlogsignin?view=graph-powershell-1.0).
119+
120+
The AzureAD Graph PowerShell module doesn't support viewing applied conditional access policies; only the Microsoft Graph PowerShell module returns applied conditional access policies.
121+
122+
## Confirming access
123+
124+
In the **Conditional Access** tab, you see a list of conditional access policies applied to that sign-in event.
125+
126+
127+
To confirm that you have admin access to view applied conditional access policies in the sign-ins logs, do:
128+
129+
1. Navigate to the Azure portal.
130+
131+
2. In the top-right corner, select your directory, and then select **Azure Active Directory** in the left navigation pane.
132+
133+
3. In the **Monitoring** section, select **Sign-in logs**.
134+
135+
4. Click an item in the sign-in row table to bring up the Activity Details: Sign-ins context pane.
136+
137+
5. Click on the Conditional Access tab in the context pane. If your screen is small, you may need to click the ellipsis [] to see all context pane tabs.
138+
139+
140+
141+
142+
## Next steps
143+
144+
* [Sign-ins error codes reference](./concept-sign-ins.md)
145+
* [Sign-ins report overview](concept-sign-ins.md)

articles/active-directory/reports-monitoring/toc.yml

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -63,18 +63,20 @@
6363
items:
6464
- name: Access activity logs
6565
href: howto-access-activity-logs.md
66+
- name: Configure prerequisites for Reporting API
67+
href: howto-configure-prerequisites-for-reporting-api.md
6668
- name: Download logs
6769
href: howto-download-logs.md
68-
- name: Manage inactive user accounts in Azure AD
69-
href: howto-manage-inactive-user-accounts.md
7070
- name: Find activity reports
7171
href: howto-find-activity-reports.md
72+
- name: Manage inactive user accounts in Azure AD
73+
href: howto-manage-inactive-user-accounts.md
7274
- name: Troubleshoot sign-in errors for a user
7375
href: howto-troubleshoot-sign-in-errors.md
74-
- name: Configure prerequisites for Reporting API
75-
href: howto-configure-prerequisites-for-reporting-api.md
76-
- name: How to use Azure AD workbooks
76+
- name: Use Azure AD workbooks
7777
href: howto-use-azure-monitor-workbooks.md
78+
- name: View applied conditional access policies
79+
href: how-to-view-applied-conditional-access-policies.md
7880

7981
- name: Monitoring
8082
items:
@@ -125,6 +127,7 @@
125127
href: reports-faq.yml
126128
- name: Sign-in log schema
127129
href: reference-azure-monitor-sign-ins-log-schema.md
130+
128131
- name: Workbooks
129132
items:
130133
- name: Authentication prompts analysis
@@ -139,6 +142,7 @@
139142
href: workbook-risk-analysis.md
140143
- name: Sensitive Operations Report
141144
href: workbook-sensitive-operations-report.md
145+
142146
- name: Recommendations
143147
items:
144148
- name: Convert to conditional access MFA

0 commit comments

Comments
 (0)