大网数据广告活动
域与目录服务

Error AADSTS650056 - Misconfigured application

· 52CE 我爱测

Provides solutions for the AADSTS650056 misconfiguration error.

Summary

This article provides troubleshooting steps and solutions for the "AADSTS650056: Misconfigured application" error.

Symptoms

When you try to sign in to a web application that uses Microsoft Entra ID, you receive the following error message:

AADSTS650056: Misconfigured application. This could be due to one of the following: The client has not listed any permissions for 'AAD Graph' in the requested permissions in the client’s application registration. Or, The admin has not consented in the tenant. Or, Check the application identifier in the request to ensure it matches the configured client application identifier. Please contact your admin to fix the configuration or consent on behalf of the tenant.

Cause

This error typically occurs for one of the following reasons:

  • The Issuer that's provided in the SAMLRequest is not valid.
  • The application doesn't have the required permissions to call Microsoft Graph APIs.
  • The admin hasn't consented to the permissions for the application on behalf of the tenant.

Solution 1: The Issuer provided in the SAMLRequest is not valid (for SAML Authentication flows)

In the following SAML request example, the Issuer value must match the Identifier (Entity ID) that's configured in the enterprise application. This value is also known as the Identifier URI or App ID URI. For example, a SAML request might resemble the following request:

<samlp:AuthnRequest xmlns="urn:oasis:names:tc:SAML:2.0:metadata" ID="id6c1c178c166d486687be4aaf5e482730" Version="2.0" IssueInstant="2013-03-18T03:28:54.1839884Z" xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"> <Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion">https://www.contoso.com</Issuer> </samlp:AuthnRequest> 

In this example, the Identifier URI is https://www.contoso.com.

To fix a mismatch, do one of the following actions:

  • Update the Identifier in the enterprise application so that it matches the Issuer in the SAML request.
  • Update the SaaS application configuration on the vendor side so that it passes the correct Issuer.

Solution 2: Verify application permissions and consent

If your organization owns the application, follow these steps:

  1. Sign in to the Azure portal, go to the App registrations screen, select your app registration, and then select API permissions.

  2. Make sure that the application has at least the User.Read delegated permission from Microsoft Graph.

  3. Check the Status field to determine whether the permissions are consented to. For example:

    • If the permission isn't consented to, the value appears as Pending or blank.
    • If the permission is successfully consented to, the value appears as "Granted for [Tenant Name]."

    Example of a consented permission:

    :::image type="content" source="./media/error-code-AADSTS650056-misconfigured-app/graph-api-permissions.png" alt-text="Screenshot of adding Graph API permissions." :::

If your organization isn't the application owner, follow these steps:

  1. Sign in to the application by using a Global Administrator account. You should see a consent screen that prompts you to grant permissions. Make sure that you select the Consent on behalf of your organization option before you proceed.

    Example of the consent screen:

    :::image type="content" source="./media/error-code-AADSTS650056-misconfigured-app/consent-permissions.png" alt-text="Screenshot of consent screen" :::

  2. If you don't see the consent screen, delete the application from the Enterprise applications section in Microsoft Entra ID, and then try again to sign in.

If the error persists, go to the next solution.

Solution 3: Manually build the consent URL

If the application is designed to access a specific resource, you might not be able to use the Consent button in the Azure portal. Instead, you might have to manually generate a consent URL, and then open the URL to grant permissions to the application.

For the authorization V1 endpoint

The consent URL resembles the following text:

https://login.microsoftonline.com/{Tenant-Id}/oauth2/authorize?response\_type=code
&client\_id={App-Id}
&resource={App-Uri-Id}
&scope=openid
&prompt=consent

For example:

https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/authorize
?response\_type=code
&client\_id=00001111-aaaa-2222-bbbb-3333cccc4444
&resource=https://vault.azure.net/
&scope=openid
&prompt=consent

For the authorization V2 endpoint

The consent URL resembles the following text:

https://login.microsoftonline.com/{Tenant-Id}/oauth2/v2.0/authorize
?response_type=code
&client_id={App-Id}
&scope=openid+{App-Uri-Id}/{Scope-Name}
&prompt=consent

For example:

https://login.microsoftonline.com/contoso.onmicrosoft.com/oauth2/v2.0/authorize
?response_type=code
&client_id=00001111-aaaa-2222-bbbb-3333cccc4444
&scope=openid+https://vault.azure.net/user_impersonation
&prompt=consent
  • If the application accesses itself as the resource, {App-Id} and {App-Uri-Id} are the same.
  • You can get the {App-Id} and {App-Uri-Id} values from the application owner.
  • {Tenant-Id} corresponds to your tenant identifier. This value can be either your domain or your directory ID.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 05/19/2025
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。