Skip to content

Commit 475b1bf

Browse files
Update admin-consent-workflow-overview.md
1 parent f5a03cf commit 475b1bf

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/manage-apps/admin-consent-workflow-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ As an admin, the following options exist for you to determine how users consent
3232
- Disable user consent. For example, a high school may want to turn off user consent so that the school IT administration has full control over all the applications that are used in their tenant.
3333
- Allow users to consent to the required permissions. It's NOT recommended to keep user consent open if you have sensitive data in your tenant.
3434
- If you still want to retain admin-only consent for certain permissions but want to assist your end-users in onboarding their application, you can use the admin consent workflow to evaluate and respond to admin consent requests. This way, you can have a queue of all the requests for admin consent for your tenant and can track and respond to them directly through the Microsoft Entra admin center.
35-
To learn how to configure the admin consent workflow, see [configure-admin-consent-workflow.md](configure-admin-consent-workflow.md).
35+
To learn how to configure the admin consent workflow, see [configure the admin consent workflow](configure-admin-consent-workflow.md).
3636

3737
## How the admin consent workflow works
3838

0 commit comments

Comments
 (0)