Skip to content

Commit 458e9e6

Browse files
authored
Merge pull request #242191 from MicrosoftGuyJFlo/ConditionalAccessOverview0623
[Azure AD] Conditional Access - Overview update
2 parents 06f2f26 + f7a8695 commit 458e9e6

File tree

3 files changed

+34
-16
lines changed

3 files changed

+34
-16
lines changed
Loading
338 KB
Loading

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

Lines changed: 34 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -6,25 +6,27 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: overview
9-
ms.date: 02/13/2023
9+
ms.date: 06/20/2023
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
1313
manager: amycolannino
14-
ms.reviewer: calebb
14+
ms.reviewer: kvenkit
1515

1616
ms.collection: M365-identity-device-management
1717
ms.custom: zt-include
1818
---
1919
# What is Conditional Access?
2020

21-
The modern security perimeter now extends beyond an organization's network to include user and device identity. Organizations can use identity-driven signals as part of their access control decisions.
21+
Microsoft is providing Conditional Access templates to organizations in report-only mode starting in January of 2023. We may add more policies as new threats emerge.
22+
23+
The modern security perimeter extends beyond an organization's network perimeter to include user and device identity. Organizations now use identity-driven signals as part of their access control decisions.
2224

2325
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4MwZs]
2426
25-
Conditional Access brings signals together, to make decisions, and enforce organizational policies. Azure AD Conditional Access is at the heart of the new identity-driven control plane.
27+
Azure AD Conditional Access brings signals together, to make decisions, and enforce organizational policies. Conditional Access is Microsoft's [Zero Trust policy engine](/security/zero-trust/deploy/identity) taking signals from various sources into account when enforcing policy decisions.
2628

27-
![Conceptual Conditional signal plus decision to get enforcement](./media/overview/conditional-access-signal-decision-enforcement.png)
29+
:::image type="content" source="media/overview/conditional-access-signal-decision-enforcement.png" alt-text="Diagram showing concept of Conditional Access signals plus decision to enforce organizational policy.":::
2830

2931
Conditional Access policies at their simplest are if-then statements, if a user wants to access a resource, then they must complete an action. Example: A payroll manager wants to access the payroll application and is required to do multifactor authentication to access it.
3032

@@ -35,14 +37,16 @@ Administrators are faced with two primary goals:
3537

3638
Use Conditional Access policies to apply the right access controls when needed to keep your organization secure.
3739

38-
![Conceptual Conditional Access process flow](./media/overview/conditional-access-overview-how-it-works.png)
39-
4040
> [!IMPORTANT]
4141
> Conditional Access policies are enforced after first-factor authentication is completed. Conditional Access isn't intended to be an organization's first line of defense for scenarios like denial-of-service (DoS) attacks, but it can use signals from these events to determine access.
4242
4343
## Common signals
4444

45-
Common signals that Conditional Access can take in to account when making a policy decision include the following signals:
45+
Conditional Access takes signals from various sources into account when making access decisions.
46+
47+
:::image type="content" source="media/overview/conditional-access-central-policy-engine-zero-trust.png" alt-text="Diagram showing Conditional Access as the Zero Trust policy engine aggregating signals from various sources.":::
48+
49+
These signals include:
4650

4751
- User or group membership
4852
- Policies can be targeted to specific users and groups giving administrators fine-grained control over access.
@@ -55,21 +59,24 @@ Common signals that Conditional Access can take in to account when making a poli
5559
- Application
5660
- Users attempting to access specific applications can trigger different Conditional Access policies.
5761
- Real-time and calculated risk detection
58-
- Signals integration with [Azure AD Identity Protection](../identity-protection/overview-identity-protection.md) allows Conditional Access policies to identify risky sign-in behavior. Policies can then force users to change their password, do multifactor authentication to reduce their risk level, or block access until an administrator takes manual action.
62+
- Signals integration with [Azure AD Identity Protection](../identity-protection/overview-identity-protection.md) allows Conditional Access policies to identify and remediate risky users and sign-in behavior.
5963
- [Microsoft Defender for Cloud Apps](/defender-cloud-apps/what-is-defender-for-cloud-apps)
60-
- Enables user application access and sessions to be monitored and controlled in real time, increasing visibility and control over access to and activities done within your cloud environment.
64+
- Enables user application access and sessions to be monitored and controlled in real time. This integration increases visibility and control over access to and activities done within your cloud environment.
6165

6266
## Common decisions
6367

6468
- Block access
6569
- Most restrictive decision
6670
- Grant access
67-
- Least restrictive decision, can still require one or more of the following options:
71+
- Less restrictive decision, can require one or more of the following options:
6872
- Require multifactor authentication
73+
- Require authentication strength
6974
- Require device to be marked as compliant
7075
- Require Hybrid Azure AD joined device
7176
- Require approved client app
72-
- Require app protection policy (preview)
77+
- Require app protection policy
78+
- Require password change
79+
- Require terms of use
7380

7481
## Commonly applied policies
7582

@@ -83,6 +90,20 @@ Many organizations have [common access concerns that Conditional Access policies
8390
- Blocking risky sign-in behaviors
8491
- Requiring organization-managed devices for specific applications
8592

93+
Administrators can create policies from scratch or start from a template policy in the portal or using the Microsoft Graph API.
94+
95+
## Administrator experience
96+
97+
Administrators with the [Conditional Access Administrator](../roles/permissions-reference.md#conditional-access-administrator) role can manage policies in Azure AD.
98+
99+
Conditional Access is found in the Azure portal under **Azure Active Directory** > **Security** > **Conditional Access**.
100+
101+
:::image type="content" source="media/overview/conditional-access-overview.png" alt-text="Screenshot of the Conditional Access overview page in the Azure portal." lightbox="media/overview/conditional-access-overview.png":::
102+
103+
- The **Overview** page provides a summary of policy state, users, devices, and applications as well as general and security alerts with suggestions.
104+
- The **Coverage** page provides a synopsis of applications with and without Conditional Access policy coverage over the last seven days.
105+
- The **Monitoring** page allows administrators to see a graph of sign-ins that can be filtered to see potential gaps in policy coverage.
106+
86107
## License requirements
87108

88109
[!INCLUDE [Active Directory P1 license](../../../includes/active-directory-p1-license.md)]
@@ -93,7 +114,7 @@ Risk-based policies require access to [Identity Protection](../identity-protecti
93114

94115
Other products and features that may interact with Conditional Access policies require appropriate licensing for those products and features.
95116

96-
When licenses required for Conditional Access expire, policies aren't automatically disabled or deleted so customers can migrate away from Conditional Access policies without a sudden change in their security posture. Remaining policies can be viewed and deleted, but no longer updated.
117+
When licenses required for Conditional Access expire, policies aren't automatically disabled or deleted. This grants customers the ability to migrate away from Conditional Access policies without a sudden change in their security posture. Remaining policies can be viewed and deleted, but no longer updated.
97118

98119
[Security defaults](../fundamentals/concept-fundamentals-security-defaults.md) help protect against identity-related attacks and are available for all customers.
99120

@@ -103,6 +124,3 @@ When licenses required for Conditional Access expire, policies aren't automatica
103124

104125
- [Building a Conditional Access policy piece by piece](concept-conditional-access-policies.md)
105126
- [Plan your Conditional Access deployment](plan-conditional-access.md)
106-
- [Learn about Identity Protection](../identity-protection/overview-identity-protection.md)
107-
- [Learn about Microsoft Defender for Cloud Apps](/cloud-app-security/what-is-cloud-app-security)
108-
- [Learn about Microsoft Intune](/intune/index)

0 commit comments

Comments
 (0)