Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Conditional Access grant controls

This page's changes and edits · All guidance changes

Microsoft's edit ·

Publish Ignite 2026 High Assurance documentation release (#15002)

Microsoft's commit message in MicrosoftDocs/entra-docs · commit d55e854 · +31 −1 lines · also on GitHub

Source wording view
⋯ 1 unchanged line
22 title: How to Configure Grant Controls in Microsoft Entra
33 description: Learn how to configure grant controls in Microsoft Entra Conditional Access policies to secure access to your organization's resources effectively.
44 ms.topic: concept-article
5 −ms.date: 06/02/2026
5 +ms.date: 10/06/2026
6 +author: tilarso
7 +ms.author: tilarso
68 ai-usage: ai-assisted
9 +#customer intent: As an administrator, I want to understand Conditional Access grant controls so that I can choose appropriate requirements for resource access.
710 ms.reviewer: lhuangnorth, jogro
811 ms.custom:
912 - sfi-image-nochange
⋯ 1 unchanged line
1114 - ai-gen-title
1215 - ai-seo-date:08/28/2025
1316 - ai-gen-description
17 + - msecd-doc-authoring-108
1418 ---
1519 # Conditional Access: Grant
1620
⋯ 20 unchanged lines
3741 - [Require approved client app](./policy-all-users-device-compliance.md)
3842 - [Require app protection policy](./policy-all-users-device-compliance.md)
3943 - [Require password change](#require-password-change)
44 +- [Require identity verification](#require-identity-verification)
4045
4146 When admins choose to combine these options, they can use the following methods:
4247
⋯ 187 unchanged lines
230235 ### Terms of use
231236
232237 If your organization created terms of use, other options might be visible under grant controls. These options allow admins to require acknowledgment of terms of use as a condition of accessing the resources that the policy protects. You can find more information about terms of use in [Microsoft Entra terms of use](terms-of-use.md).
238 +
239 +## Require identity verification
240 +
241 +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.
242 +
243 +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.
244 +
245 +
246 +Check [Identity verification licensing](../../fundamentals/licensing.md#identity-verification) for the requirements that apply to your scenario. License requirements for identity verification are separate from the existing generic authentication-strength guidance.
247 +
248 +Configure an eligible [identity verification profile](../authentication/concept-authentication-verified-id.md#create-and-manage-identity-verification-profiles), then follow the guide for your scenario:
249 +
250 +- [Require identity verification for resource access](policy-require-identity-verification.md#configure-a-resource-access-policy) for resource policy design, supported issuance testing, and failure handling.
251 +- [Protect onboarding and recovery](policy-require-identity-verification.md#configure-an-onboarding-and-recovery-policy) for bootstrap policy boundaries.
252 +- [Configure risk policies](../../id-protection/howto-identity-protection-configure-risk-policies.md) for the separate risk scenario.
253 +
254 +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.
255 +
256 +> [!NOTE]
257 +> **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](policy-require-identity-verification.md#review-control-limitations) before combining controls. This limitation doesn't apply to ordinary resource-access policies.
258 +
259 +**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.
260 +
261 +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.
262 +
233263
234264 ## Multiple grant controls
235265
⋯ 19 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy today 18:05 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 17:57 UTC · 272 of 275 readable · 270 fully read · documentation 469/469 current