You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/entra/entra-id/app-integration/troubleshoot-consent-issues.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Troubleshooting consent issues in Microsoft Entra ID
3
3
description: Helps you troubleshoot and resolve consent issues in Microsoft Entra ID.
4
-
ms.date: 01/06/2025
4
+
ms.date: 01/1/2025
5
5
ms.reviewer: willfid, v-weizhu
6
6
ms.service: entra-id
7
7
ms.custom: sap:App registrations
@@ -28,8 +28,8 @@ When an application tries to sign-in or get an access token for a resource which
28
28
There are many reasons why you might receive a message indicating that admin approval or admin consent is required. Consider the following high-level scenarios:
29
29
30
30
- The `User.Read` permission is missing.
31
-
- User consent is disabled.
32
-
- User assignment required is enabled.
31
+
- User consent is disabled on the tenant level.
32
+
- User assignment required is enabled for the application.
33
33
- A service principal doesn't exist in the tenant for the client app.
34
34
- A service principal doesn't exist in the tenant for the resource.
35
35
- A consent URL that specifies `prompt=admin_consent` or `prompt=consent` is requested.
0 commit comments