MC1250351 High
Power Platform – New Continuous Access Evaluation (CAE) announcement
Summary AI-generated
Dataverse user sign-ins are moving to CAE-enabled authentication for real-time session evaluation; review CAE Conditional Access policies before rollout completes by September 2026.
Suggested actions AI-generated
- Review user-focused CAE Conditional Access policies
- Ensure location conditions do not block Dataverse access
- Test Dataverse sign-in under CAE policies
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
- MC1446723 Power Platform - New Continuous Access Evaluation (CAE) rollout nearing completion
- MC1446227 Power Platform - Manage agent security with enhanced admin controls
- 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
- MC1411574 (Updated) Microsoft Entra: System-preferred authentication now applies to first-factor authentication
Original post from Microsoft
We are announcing our CAE rollout for user sign-in flows to Dataverse as part of ongoing security improvements for Power Platform. This change affects interactive user access to Dataverse and relies on Microsoft Entra Conditional Access (CAE) policies for near real-time session evaluation. This feature is being gradually rolled out across Dataverse environments, which is anticipated to be complete by September 2026.
Users are advised to review their user-focused CAE Conditional Access policies to ensure continued access to Dataverse.
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 at the 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.
Note: This change applies only to interactive user sign-in flows.
Who is Impacted?
Customers with:
Customers should take the following actions for user access scenarios:
Users are advised to review their user-focused CAE Conditional Access policies to ensure continued access to Dataverse.
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 at the 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.
Note: This change applies only to interactive user sign-in flows.
Who is Impacted?
Customers with:
- 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.
Customers should take the following actions for user access scenarios:
- Review user-targeted CAE Conditional Access policies
- Ensure policies allow Dataverse user traffic from locations which are compliant as per your CAE policies.
- Avoid overly restrictive location conditions that could unintentionally block user sessions.
- Validate interactive user sign-in scenarios
- Test Dataverse access for end users under current CAE policies.
- Review the policies enforcing location, device, or risk conditions.