Conditional Access grant controls
Observed content change
May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant.
Changed article references · 7 added · 0 removed
- Added link: Require identity verification
#require-identity-verification - Added link: Identity verification licensing
../../fundamentals/licensing#identity-verification - Added link: Configure risk policies
../../id-protection/howto-identity-protection-configure-risk-policies - Added link: identity verification profile
../authentication/concept-authentication-verified-id#create-and-manage-identity-verification-profiles - Added link: Require identity verification for resource access
policy-require-identity-verification#configure-a-resource-access-policy - Added link: Protect onboarding and recovery
policy-require-identity-verification#configure-an-onboarding-and-recovery-policy - Added link: onboarding and recovery control limitations
policy-require-identity-verification#review-control-limitations
[added: Require identity verification]
Before: No saved wording on this side.
After: Require identity verification
[added: The identity verification grant control requires users to verify their identity for protected access. Configure an eligible verification profile and apply the requirement to the supported resource or action scope in your tenant.]
Before: No saved wording on this side.
After: The identity verification grant control requires users to verify their identity for protected access. Configure an eligible verification profile and apply the requirement to the supported resource or action scope in your tenant.
[added: Identity verification and credential provenance are distinct. An identity verification requirement doesn't, by itself, establish the provenance of the specific credential used at sign-in. During preview, credential provenance is recorded only for passkey credentials.]
Before: No saved wording on this side.
After: Identity verification and credential provenance are distinct. An identity verification requirement doesn't, by itself, establish the provenance of the specific credential used at sign-in. During preview, credential provenance is recorded only for passkey credentials.
[added: Check Identity verification licensing for the requirements that apply to your scenario. License requirements for identity verification are separate from the existing generic authentication-strength guidance.]
Before: No saved wording on this side.
After: Check Identity verification licensing for the requirements that apply to your scenario. License requirements for identity verification are separate from the existing generic authentication-strength guidance.
[added: Configure an eligible identity verification profile, then follow the guide for your scenario:]
Before: No saved wording on this side.
After: Configure an eligible identity verification profile, then follow the guide for your scenario:
[added: Require identity verification for resource access for resource policy design, supported issuance testing, and failure handling.]
Before: No saved wording on this side.
After: Require identity verification for resource access for resource policy design, supported issuance testing, and failure handling.
[added: Protect onboarding and recovery for bootstrap policy boundaries.]
Before: No saved wording on this side.
After: Protect onboarding and recovery for bootstrap policy boundaries.
[added: Configure risk policies for the separate risk scenario.]
Before: No saved wording on this side.
After: Configure risk policies for the separate risk scenario.
[added: Use onboarding and recovery user-action targeting to protect bootstrap separately from ordinary resource access. Confirm the target and exclusion options available in your tenant. Preserve emergency access, and keep exclusions scoped and approved rather than removing ordinary resource protection.]
Before: No saved wording on this side.
After: Use onboarding and recovery user-action targeting to protect bootstrap separately from ordinary resource access. Confirm the target and exclusion options available in your tenant. Preserve emergency access, and keep exclusions scoped and approved rather than removing ordinary resource protection.
[added: Note Terms of use and Require authentication strength aren't supported for the onboarding and recovery user action. Most other Microsoft Entra-specific controls also aren't supported for this action. Review the onboarding and recovery control limitations before combining controls. This limitation doesn't apply to ordinary resource-access policies.]
Before: No saved wording on this side.
After: Note Terms of use and Require authentication strength aren't supported for the onboarding and recovery user action. Most other Microsoft Entra-specific controls also aren't supported for this action. Review the onboarding and recovery control limitations before combining controls. This limitation doesn't apply to ordinary resource-access policies.
[added: Require risk remediation remains a distinct control with the behavior described above. The identity verification requirement isn't a rename or an automatic change to that control.]
Before: No saved wording on this side.
After: Require risk remediation remains a distinct control with the behavior described above. The identity verification requirement isn't a rename or an automatic change to that control.
[added: Report-only evaluation isn't enforcement and doesn't prove that verification completed. Report-only guidance excludes user-action policies from evaluation; don't rely on it for onboarding and recovery without confirming support for that action.]
Before: No saved wording on this side.
After: Report-only evaluation isn't enforcement and doesn't prove that verification completed. Report-only guidance excludes user-action policies from evaluation; don't rely on it for onboarding and recovery without confirming support for that action.
Source: Microsoft source · © Microsoft · MIT.
Read the current Microsoft source · Link to this observation · Compare any two versions
Observation details
- Observed by ChangeIntel
- today 11:14 UTC
- Source update metadata
- today 08:34 UTC
- First observed on this installation
- 5 Oct 17:50 UTC
- Last successful check
- today 11:14 UTC
- Next check due
- today 17:14 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.