Conditional Access target resources
Observed content change
May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices.
Changed article references · 5 added · 0 removed
- Added link: create an eligible identity verification profile
../authentication/concept-authentication-verified-id#create-and-manage-identity-verification-profiles - Added link: Require identity verification with Conditional Access
policy-require-identity-verification#configure-an-onboarding-and-recovery-policy - Added link: Enable the global onboarding and recovery exclusion
policy-require-identity-verification#enable-the-global-onboarding-and-recovery-exclusion-preview - Added link: enable the global onboarding and recovery exclusion
policy-require-identity-verification#enable-the-global-onboarding-and-recovery-exclusion-preview - Added link: control limitations
policy-require-identity-verification#review-control-limitations
[added: Policies targeting All resources also apply to onboarding and account recovery events unless you enable the global user-action exclusion. These policies can require credentials or other controls that users can't satisfy before they establish or restore their authentication methods.]
Before: No saved wording on this side.
After: Policies targeting All resources also apply to onboarding and account recovery events unless you enable the global user-action exclusion. These policies can require credentials or other controls that users can't satisfy before they establish or restore their authentication methods.
[added: Under Entra ID > Conditional Access > Settings (Preview), Global exclusions exposes the Account onboarding and recovery (Preview) setting. When enabled, it excludes the Account onboarding and recovery user action from policies targeting All resources. Policies that directly target the user action still apply.]
Before: No saved wording on this side.
After: Under Entra ID > Conditional Access > Settings (Preview), Global exclusions exposes the Account onboarding and recovery (Preview) setting. When enabled, it excludes the Account onboarding and recovery user action from policies targeting All resources. Policies that directly target the user action still apply.
[added: This is a global user-action exclusion, not a resource exclusion configured in an individual policy. It doesn't exclude users from ordinary application access policies. Review the tenant-wide impact and protect the bootstrap journey with a policy targeting the user action. For steps and validation guidance, see Enable the global onboarding and recovery exclusion.]
Before: No saved wording on this side.
After: This is a global user-action exclusion, not a resource exclusion configured in an individual policy. It doesn't exclude users from ordinary application access policies. Review the tenant-wide impact and protect the bootstrap journey with a policy targeting the user action. For steps and validation guidance, see Enable the global onboarding and recovery exclusion.
User actions are tasks that a user performs. Conditional Access supports[removed: two][added: the following] user actions:
Before: User actions are tasks that a user performs. Conditional Access supports two user actions:
After: User actions are tasks that a user performs. Conditional Access supports the following user actions:
[added: Use Account onboarding and recovery to apply Conditional Access to onboarding and recovery, separately from ordinary resource access. Before configuring an identity verification requirement, create an eligible identity verification profile. Follow Require identity verification with Conditional Access to configure and test the policy.]
Before: No saved wording on this side.
After: Use Account onboarding and recovery to apply Conditional Access to onboarding and recovery, separately from ordinary resource access. Before configuring an identity verification requirement, create an eligible identity verification profile. Follow Require identity verification with Conditional Access to configure and test the policy.
[added: Creating a user-action policy doesn't automatically exclude the journey from All resources policies. To remove that overlap while retaining policies targeting the user action, enable the global onboarding and recovery exclusion.]
Before: No saved wording on this side.
After: Creating a user-action policy doesn't automatically exclude the journey from All resources policies. To remove that overlap while retaining policies targeting the user action, enable the global onboarding and recovery exclusion.
[added: Note Terms of use, Require authentication strength, and most other Microsoft Entra-specific controls aren't supported for this action. These limitations don't apply to ordinary resource-access policies. Review the control limitations before rollout. Don't use report-only results as proof that an onboarding or recovery policy is evaluated or enforced. Risk-based Conditional Access policies currently don't apply to onboarding actions.]
Before: No saved wording on this side.
After: Note Terms of use, Require authentication strength, and most other Microsoft Entra-specific controls aren't supported for this action. These limitations don't apply to ordinary resource-access policies. Review the control limitations before rollout. Don't use report-only results as proof that an onboarding or recovery policy is evaluated or enforced. Risk-based Conditional Access policies currently don't apply to onboarding actions.
Source: Microsoft source · © Microsoft · MIT.
Read the current Microsoft source · Link to this observation · Compare any two versions
Observation details
- Observed by ChangeIntel
- today 05:01 UTC
- Source update metadata
- 17 Nov 08:34 UTC
- Microsoft's latest commit in that period
- Publish Ignite 2026 High Assurance documentation release (#15002) · committed 17 Nov 00:04 UTC · View diff
- First observed on this installation
- 5 Oct 23:18 UTC
- Last successful check
- today 05:01 UTC
- Next check due
- 19 Nov 05:01 UTC
Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.