Control 2.3: Conditional Access Policies for Copilot Workloads — Portal Walkthrough
Step-by-step portal configuration for implementing Conditional Access policies that govern access to Microsoft 365 Copilot.
Prerequisites
- Entra ID Conditional Access Administrator or Security Administrator role
- Microsoft Entra ID P1 or P2 license
- Device compliance policies configured in Microsoft Intune
- Named locations defined for corporate network ranges
- Action required: If your organization uses "All resources" CA policies with exclusions, audit and remediate for the June 15, 2026 baseline-scopes enforcement rollout (see Step 2)
Steps
Step 1: Discover the Enterprise Copilot Platform App ID in Your Tenant
Portal: Microsoft Entra Admin Center Path: Microsoft Entra admin center > Entra ID > Enterprise applications
Before creating or modifying any Copilot CA policy, confirm the tenant's Enterprise Copilot Platform service principal and Application ID. Microsoft Learn lists Enterprise Copilot Platform as part of the Office 365 Conditional Access app suite, but it directs administrators to look up Application IDs in their own tenant rather than using a published static GUID.
- Set Application type to Microsoft Applications.
- Add the Application ID column.
- Search for Enterprise Copilot Platform and record the display name, Application ID, and App owner organization ID.
- Search existing policies for references to the tenant-discovered Copilot app. Use the CA optimization agent to identify policies that may need updating. A misconfigured app ID causes the policy to miss Copilot traffic entirely.
Step 2: Audit for June 2026 Baseline-Scopes CA Enforcement Change
Portal: Microsoft Entra Admin Center Path: Microsoft Entra admin center > Protection > Conditional Access > Optimization
Beginning June 15, 2026, Entra ID is progressively rolling out enforcement of Conditional Access for baseline scopes (OIDC scopes such as openid/profile and baseline directory scopes such as User.Read, People.Read) even for resources excluded in "All resources" policies. This closes a bypass path that previously allowed access requesting only those baseline scopes without full enforcement. The rollout reaches tenants progressively over several weeks; you can enable enforcement early or opt out per-policy via the Baseline scopes settings.
- Open the Conditional Access optimization agent
- Review all policies scoped to "All resources" that include resource exclusions
- Identify any policy that excludes the tenant-discovered Enterprise Copilot Platform application
- Deploy remediated policies in report-only mode to assess user impact
- Enable enforcement early in a test tenant, or verify the tenant's rollout status via the Baseline scopes settings, before the rollout completes
Step 3: Create Conditional Access Policy for Copilot
Portal: Microsoft Entra Admin Center Path: Microsoft Entra admin center > Protection > Conditional Access > New policy
Create a dedicated Conditional Access policy targeting Copilot workloads: - Name: "FSI Copilot Access — Compliant Device Required" - Users: Include Copilot deployment groups; exclude emergency access accounts - Target resources: Enterprise Copilot Platform, using the Application ID discovered in your tenant - Conditions: All client apps, any platform - Grant: Require device compliance AND require MFA
Step 4: Configure Device Compliance Requirements
Portal: Microsoft Entra Admin Center Path: Microsoft Entra admin center > Protection > Conditional Access > [Policy] > Grant controls
Set grant controls requiring managed, compliant devices for Copilot access: - Require device to be marked as compliant (Intune managed) - Require multi-factor authentication - Require both controls (AND operator, not OR)
This helps prevent Copilot access from unmanaged personal devices in FSI environments.
Step 5: Define Location-Based Conditions
Portal: Microsoft Entra Admin Center Path: Microsoft Entra admin center > Protection > Conditional Access > Named locations
Configure named locations for location-aware Copilot access: - Define corporate office IP ranges as trusted locations - Define VPN exit points as trusted locations - Optionally block Copilot access from non-trusted locations for highly regulated roles
Step 6: Configure Session Controls
Portal: Microsoft Entra Admin Center Path: Microsoft Entra admin center > Protection > Conditional Access > [Policy] > Session controls
Add session controls for additional security: - Sign-in frequency: Require re-authentication every 8 hours for Copilot sessions (4 hours for Regulated) - Persistent browser session: Disable for non-compliant devices - App-enforced restrictions: Enable for SharePoint integration - Conditional Access App Control: Route through Defender for Cloud Apps if configured
Step 7: Enable Adaptive Protection Integration
Portal: Microsoft Purview > Insider Risk Management > Adaptive Protection Path: Microsoft Purview > Insider Risk Management > Adaptive Protection settings
Configure IRM Adaptive Protection to feed real-time risk signals into Conditional Access: 1. Enable Adaptive Protection in IRM settings 2. Configure risk level thresholds (Recommended: High risk triggers CA block; Regulated: Medium risk triggers CA block) 3. Return to Entra ID Conditional Access and create a policy that responds to IRM risk levels: - Condition: Insider risk — tied to IRM Adaptive Protection signal - Grant: Block access (Regulated) or require re-authentication (Recommended) 4. When a user's IRM risk level is elevated, the CA policy automatically restricts their next Copilot authentication without requiring manual intervention
Step 8: Test Policy in Report-Only Mode
Portal: Microsoft Entra Admin Center Path: Microsoft Entra admin center > Protection > Conditional Access > [Policy] > Enable policy > Report-only
Deploy the policy in report-only mode to evaluate impact before enforcement: - Monitor the Conditional Access insights workbook for policy matches - Review sign-in logs for users who would be blocked or challenged - Verify no legitimate users are unexpectedly impacted - After 1-2 weeks of clean results, switch to enforcement mode
FSI Recommendations
| Tier | Recommendation |
|---|---|
| Baseline | Require MFA for all Copilot access; compliant device required; audit CA policies for Copilot exclusions for the June 2026 baseline-scopes rollout; enable Adaptive Protection in audit mode |
| Recommended | Location-based restrictions; session controls with 8-hour re-auth; remove Copilot-specific exclusions from "All resources" policies and test in report-only ahead of the June 2026 rollout; enable Adaptive Protection dynamic blocking for high-risk users |
| Regulated | Compliant device AND MFA AND trusted location required; session controls with 4-hour re-auth and app-enforced restrictions; Defender for Cloud Apps integration; CA policy remediation completed and enforcement enabled ahead of the June 2026 rollout; Adaptive Protection dynamic blocking at medium-risk threshold |
Next Steps
- Proceed to PowerShell Setup for Conditional Access automation
- See Verification & Testing to validate access controls
- Review Control 2.9 for Defender for Cloud Apps session controls
- Review Control 2.10 for IRM Adaptive Protection configuration
- Back to Control 2.3