MC1446723 High
Power Platform - New Continuous Access Evaluation (CAE) rollout nearing completion
Summary AI-generated
Final stage rollout of Continuous Access Evaluation (CAE) for Dataverse user sign-ins, requiring updated Entra Conditional Access policies to ensure uninterrupted access.
Suggested actions AI-generated
- Review user-focused CAE Conditional Access policies
- Ensure Dataverse user traffic is permitted by CAE policies
- Avoid overly restrictive location conditions
- Test Dataverse access for users under current policies
- Review policies enforcing location, device, or risk conditions
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1454234 Power Platform – New Continuous Access Evaluation (CAE) announcement
- MC1250351 Power Platform – New Continuous Access Evaluation (CAE) announcement
- MC1326253 Conditional Access policies now apply to Windows Hello for Business and macOS Platform SSO registration
- MC1472591 (Updated) Enhanced security and access controls for Outlook attachments
- MC1403390 Power Platform admin center – Advanced connector policies
- MC1532256 Microsoft Teams: Granular Conditional Access for Teams meetings
Original post from Microsoft
As part of our ongoing security improvements for Power Platform, the Continuous Access Evaluation (CAE) rollout for user sign-in flows in Dataverse is now entering its final stage across public cloud environments. This change affects interactive user access to Dataverse and relies on Microsoft Entra Conditional Access policies for near real-time session evaluation. We expect to complete the rollout by the week of August 10, 2026. Once the rollout is complete, we will follow up with a General Availability (GA) announcement confirming that CAE is fully available across the public cloud.
How does this affect me?
Dataverse user access is transitioning to CAE-enabled authentication, where user sessions are continuously evaluated based on Conditional Access policy signals rather than only during initial sign-in.
As part of this rollout, user sign-in traffic to Dataverse may originate from managed locations that must be permitted and compliant with your organization’s CAE Conditional Access policies. We advise that you review your user-focused CAE policies to ensure continued access to Dataverse.
You will be affected by this change if you have:
Note: This change applies only to interactive user sign-in flows.
What do I need to do to prepare?
Please take the following actions for user access scenarios:Validate interactive user sign-in scenarios:
No action is required if your existing user CAE policies already permit Dataverse access from managed locations.
How does this affect me?
Dataverse user access is transitioning to CAE-enabled authentication, where user sessions are continuously evaluated based on Conditional Access policy signals rather than only during initial sign-in.
As part of this rollout, user sign-in traffic to Dataverse may originate from managed locations that must be permitted and compliant with your organization’s CAE Conditional Access policies. We advise that you review your user-focused CAE policies to ensure continued access to Dataverse.
You will be affected by this change if you have:
- CAE-enabled Conditional Access policies applied to users.
- Location-based conditions in user CAE policies.
- Sign-in frequency, session controls, or risk-based policies for Dataverse users.
Note: This change applies only to interactive user sign-in flows.
What do I need to do to prepare?
Please take the following actions for user access scenarios:
- Review your user-targeted CAE Conditional Access policies.
- Ensure these policies allow Dataverse user traffic from locations that are compliant with your CAE policies.
- Avoid overly restrictive location conditions that could unintentionally block user sessions.
- Test Dataverse access for end users under current CAE policies.
- Review the policies enforcing location, device, or risk conditions.
No action is required if your existing user CAE policies already permit Dataverse access from managed locations.