Skip to content

Commit 53fad4b

Browse files
Merge pull request #87054 from MicrosoftGuyJFlo/CAConceptual
[Azure AD] Conditional Access - Conceptual
2 parents c4e322c + 433e25c commit 53fad4b

File tree

5 files changed

+135
-2
lines changed

5 files changed

+135
-2
lines changed

articles/active-directory/conditional-access/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,10 @@
1919
- name: Concepts
2020
expanded: false
2121
items:
22-
- name: Adopting Conditional Access
23-
href: howto-conditional-access-adoption-kit.md
2422
- name: Common Conditional Access policies
2523
href: concept-conditional-access-policy-common.md
24+
- name: Conditional Access policy components
25+
href: concept-conditional-access-policies.md
2626
- name: Conditions
2727
href: conditions.md
2828
- name: Location conditions
Lines changed: 131 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,131 @@
1+
---
2+
title: Building a Conditional Access policy - Azure Active Directory
3+
description: What are all of the options available to build a Conditional Access policy and what do they mean?
4+
5+
services: active-directory
6+
ms.service: active-directory
7+
ms.subservice: conditional-access
8+
ms.topic: conceptual
9+
ms.date: 09/17/2019
10+
11+
ms.author: joflore
12+
author: MicrosoftGuyJFlo
13+
manager: daveba
14+
ms.reviewer: calebb
15+
16+
ms.collection: M365-identity-device-management
17+
---
18+
# Building a Conditional Access policy
19+
20+
As explained in the article [What is Conditional Access](overview.md), a Conditional Access policy is an if-then statement, of **Assignments** and **Access controls**. A Conditional Access policy brings signals together, to make decisions, and enforce organizational policies.
21+
22+
How does an organization create these policies? What is required?
23+
24+
![Conditional Access (Signals + Decisions + Enforcement = Policies)](./media/concept-conditional-access-policies/conditional-access-signal-decision-enforcement.png)
25+
26+
## Assignments
27+
28+
The assignments portion controls the who, what, and where of the Conditional Access policy.
29+
30+
### Users and groups
31+
32+
Users and groups assign who the policy will include or exclude. This assignment can include all users, specific groups of users, directory roles, or external guest users.
33+
34+
### Cloud apps or actions
35+
36+
Cloud apps or actions can include or exclude cloud applications or user actions that will be subject to the policy.
37+
38+
### Conditions
39+
40+
A policy can contain multiple conditions.
41+
42+
#### Sign-in risk
43+
44+
For organizations with [Azure AD Identity Protection](../identity-protection/overview.md), the risk detections generated there can influence your Conditional Access policies.
45+
46+
#### Device platforms
47+
48+
Organizations with multiple device operating system platforms may wish to enforce specific policies on different platforms.
49+
50+
The information used to calculate the device platform comes from unverified sources such as user agent strings that can be changed.
51+
52+
#### Locations
53+
54+
Location data is provided by IP geolocation data. Administrators can choose to define locations and choose to mark some as trusted like those for their organization's network locations.
55+
56+
#### Client apps
57+
58+
By default Conditional Access policies apply to browser apps, mobile apps, and desktop clients that support modern authentication.
59+
60+
This assignment condition allows Conditional Access policies to target specific client applications not using modern authentication. These applications include Exchange ActiveSync clients, older Office applications that do not use modern authentication, and mail protocols like IMAP, MAPI, POP, and SMTP.
61+
62+
#### Device state
63+
64+
This control is used to exclude devices that are hybrid Azure AD joined, or marked a compliant in Intune. This exclusion can be done to block unmanaged devices.
65+
66+
## Access controls
67+
68+
The access controls portion of the Conditional Access policy controls how a policy is enforced.
69+
70+
### Grant
71+
72+
#### Block access
73+
74+
Block access does just that, it will block access under the specified assignments. The block control is powerful and should be wielded with the appropriate knowledge.
75+
76+
#### Grant access
77+
78+
The grant control can trigger enforcement of one or more controls.
79+
80+
- Require multi-factor authentication (Azure Multi-Factor Authentication)
81+
- Require device to be marked as compliant (Intune)
82+
- Require Hybrid Azure AD joined device
83+
- Require approved client app
84+
- Require app protection policy
85+
86+
Administrators can choose to require one of the previous controls or all selected controls using the following options. The default for multiple controls is to require all.
87+
88+
- Require all the selected controls (control and control)
89+
- Require one of the selected controls (control or control)
90+
91+
### Session
92+
93+
Session controls can limit the experience
94+
95+
- Use app enforced restrictions
96+
- Currently works with Exchange Online and SharePoint Online only.
97+
- Passes device information to allow control of experience granting full or limited access.
98+
- Use Conditional Access App Control
99+
- Uses signals from Microsoft Cloud App Security to do things like:
100+
- Block download, cut, copy, and print of sensitive documents.
101+
- Monitor risky session behavior.
102+
- Require labeling of sensitive files.
103+
- Sign-in frequency
104+
- Ability to change the default sign in frequency for modern authentication.
105+
- Persistent browser session
106+
- Allows users to remain signed in after closing and reopening their browser window.
107+
108+
## Simple policies
109+
110+
A Conditional Access policy must contain at minimum the following to be enforced:
111+
112+
- **Name** of the policy.
113+
- **Assignments**
114+
- **Users and/or groups** to apply the policy to.
115+
- **Cloud apps or actions** to apply the policy to.
116+
- **Access controls**
117+
- **Grant** or **Block** controls
118+
119+
![Blank Conditional Access policy](./media/concept-conditional-access-policies/conditional-access-blank-policy.png)
120+
121+
## Next steps
122+
123+
[Simulate sign in behavior using the Conditional Access What If tool](troubleshoot-conditional-access-what-if.md)
124+
125+
[Common Conditional Access policies](concept-conditional-access-policy-common.md)
126+
127+
[Planning a cloud-based Azure Multi-Factor Authentication deployment](../authentication/howto-mfa-getstarted.md)
128+
129+
[Managing device compliance with Intune](https://docs.microsoft.com/intune/device-compliance-get-started)
130+
131+
[Microsoft Cloud App Security and Conditional Access](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)
Loading
Loading

articles/active-directory/conditional-access/overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,8 @@ Customers with [Microsoft 365 Business licenses](https://docs.microsoft.com/offi
8686

8787
## Next steps
8888

89+
[Building a Conditional Access policy piece by piece](concept-conditional-access-policies.md)
90+
8991
To learn how to implement Conditional Access in your environment, see [Plan your Conditional Access deployment in Azure Active Directory](plan-conditional-access.md).
9092

9193
[Learn about Identity Protection](../identity-protection/overview-v2.md)

0 commit comments

Comments
 (0)