Skip to content

Commit 8d1c972

Browse files
WIP
1 parent eeabcc1 commit 8d1c972

File tree

1 file changed

+32
-30
lines changed

1 file changed

+32
-30
lines changed
Lines changed: 32 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Continuous access evaluation in Azure AD
3-
description: Responding to changes in user state faster with continuous access evaluation in Azure AD
2+
title: Continuous access evaluation for workload identities in Azure AD
3+
description: Respond to changes to applications with continuous access evaluation for workload identities in Azure AD
44

55
services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: conceptual
9-
ms.date: 07/18/2022
9+
ms.date: 07/22/2022
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -15,47 +15,49 @@ ms.reviewer: vmahtani
1515

1616
ms.collection: M365-identity-device-management
1717
---
18-
# Continuous access evaluation for service principals (preview)
18+
# Continuous access evaluation for workload identities (preview)
1919

20-
Continuous Access Evaluation (CAE) for service principals allows [What are workload identities?](../develop/workload-identities-overview.md) service accounts to gain significant security benefits by providing real-time enforcement of Conditional Access location and risk policies along with instant enforcement of token revocation events.
20+
Continuous access evaluation (CAE) for [workload identities](../develop/workload-identities-overview.md) provides security benefits to your organization. It enabled real-time enforcement of Conditional Access location and risk policies along with instant enforcement of token revocation events for workload identities.
2121

22-
## Scenarios
22+
Continuous access evaluation doesn't currently support managed identities.
2323

24-
CAE for Service Principals public preview scope includes the following:
24+
## Scope of preview
2525

26-
- Instant enforcement of key revocation events – service principal disable, service principal delete and High service principal risk detected by Azure AD Identity Protection
27-
- Enforcement of location based Conditional Access policies
26+
The continuous access evaluation for workload identities public preview scope includes support for Microsoft Graph as a resource provider.
2827

29-
The only resource provider enabled as part of this preview is Microsoft Graph only for third party (3P) clients
28+
The preview can target service principals for line of business (LOB) applications.
3029

31-
Opt-in for CAE+SP
30+
We support the following revocation events:
3231

33-
[Claims challenges, claims requests, and client capabilities](../develop/claims-challenge.md)
34-
The opt-in for CAE+SP is when API implementer requests xms_cc as an optional claim. The xms_cc claim with a value of "cp1" in the access token is the authoritative way to identify a client application is capable of handling a claims challenge. Your Microsoft-sourced authentication SDK may include this opt-in parameter. (for example, Azure SDK)
32+
- Service principal disable
33+
- Service principal delete
34+
- High service principal risk as detected by Azure AD Identity Protection
3535

36-
Opt-out for CAE+SP
36+
Continuous access evaluation for workload identities supports [Conditional Access policies that target location and risk](workload-identity.md#implementation).
3737

38-
In order to opt out, don't send xms_cc claim with a value of "cp1"; if you're a premium tenant, you could also create Conditional Access policy to disable CAE for SP as an immediate stop-gap measure
39-
Register an application with Azure AD, create a service principal and create a Conditional Access policy
40-
Refer this link to register an application with Azure AD and create a service principal.
41-
Refer this link to create a Conditional Access policy.
42-
To create a policy that corresponds to service principals, under Assignments select Workload Identities. Configure the remainder of the policy controls per your organizational requirements. Location ranges can be configured within the Conditions tab. Select Create once configured to create your Conditional Access policy.
43-
a. CAE is enabled in Conditional Access policies by default.
44-
b. If you want to disable CAE, navigate to your policy and disable CAE as found in the Session tab.
38+
## Enable your application
4539

46-
Sign In Logs Verification
40+
Developers can opt in to Continuous access evaluation for workload identities when their API requests `xms_cc` as an optional claim. The `xms_cc` claim with a value of `cp1` in the access token is the authoritative way to identify a client application is capable of handling a claims challenge. For more information about how to make this work in your application, see the article, [Claims challenges, claims requests, and client capabilities](../develop/claims-challenge.md).
4741

48-
When a client’s access to a resource is blocked due to CAE being triggered, the client’s session will be revoked and the client will need to reauthenticate. This behavior can be verified in the sign-in logs.
42+
### Disable
43+
44+
In order to opt out, don't send the `xms_cc` claim with a value of `cp1`.
45+
46+
Organizations who have Azure AD Premium can create a [Conditional Access policy to disable continuous access evaluation](concept-conditional-access-session.md#customize-continuous-access-evaluation) applied to specific workload identities as an immediate stop-gap measure.
47+
48+
## Troubleshooting
49+
50+
When a client’s access to a resource is blocked due to CAE being triggered, the client’s session will be revoked, and the client will need to reauthenticate. This behavior can be verified in the sign-in logs.
4951

5052
The following steps detail how an admin can verify sign in activity in the sign-in logs:
5153

5254
1. Sign into the Azure portal as a Conditional Access Administrator, Security Administrator, or Global Administrator.
53-
1. Browse to Azure Active Directory > Sign in logs > Service Principal Sign-ins Admins can use filters to ease the debugging process.
54-
1. Double select on an entry to see activity details. The field Continuous access evaluation will indicate whether a CAE token was issued in a particular sign-in attempt.
55+
1. Browse to **Azure Active Directory** > **Sign-in logs** > **Service Principal Sign-ins**. You can use filters to ease the debugging process.
56+
1. Select an entry to see activity details. The **Continuous access evaluation** field indicates whether a CAE token was issued in a particular sign-in attempt.
5557

56-
Related Links
58+
## Next steps
5759

58-
Developers Guide for CAE for Service Principals
59-
CAE documentation
60-
Service Principal Portal Operational Guide
61-
[How to use Continuous Access Evaluation enabled APIs in your applications](../develop/app-resilience-continuous-access-evaluation.md)
60+
- [Register an application with Azure AD and create a service principal](../develop/howto-create-service-principal-portal.md#register-an-application-with-azure-ad-and-create-a-service-principal)
61+
- [How to use Continuous Access Evaluation enabled APIs in your applications](../develop/app-resilience-continuous-access-evaluation.md)
62+
- [Sample application using continuous access evaluation](https://github.com/Azure-Samples/ms-identity-dotnetcore-daemon-graph-cae)
63+
- [What is continuous access evaluation?](../conditional-access/concept-continuous-access-evaluation.md)

0 commit comments

Comments
 (0)