Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | AADSTS70011: The provided value for the input parameter 'scope' is not valid. | Entra ID sign-in logs | -> ErrorDetail |
| Affected build range | Microsoft 365 builds | Product documentation | |
| Registry key involved | | | |
| Relevant service/endpoint URL | https://login.microsoftonline.com/<tenantId>/oauth2/v2.0/token | Entra ID documentation | -> Token endpoint |
| Log line signature | ErrorDetail: AADSTS70011 | Sign-in logs | |
Log Files to Check
C:\ProgramData\Microsoft\IdentityManager\Logs\idaudit.loghttps://portal.microsoftonline.com/<tenant>/reports/sa/signinEvents
What This Error Actually Means
AADSTS70011 is an error code raised by Microsoft Entra ID during OAuth 2.0 or OpenID Connect (OIDC) authentication flows when the scope parameter provided in the request does not match any registered API permissions for the application. The component that raises this error is the token endpoint of Entra ID, which validates the requested scopes against the app registration's manifest and API permission settings before issuing an access token.
The exact error string seen in sign-in logs will be "AADSTS70011: The provided value for the input parameter 'scope' is not valid." This indicates that there's a mismatch between what your application is requesting and what it has been configured to use within Entra ID. Common scenarios include typos, deprecated API endpoints being used, or incorrect scope strings due to mixing v1.0 and v2.0 endpoint formats.
Affected Versions and Scope
This error affects Microsoft 365 builds where OAuth 2.0 and OIDC authentication flows are utilized for accessing Entra ID resources. It is particularly relevant in environments that rely heavily on API permissions to control access to various services within the Microsoft Graph or other Azure AD-managed APIs.
The affected build range includes all current Microsoft 365 versions, as this error pertains to a fundamental aspect of OAuth and OIDC authentication rather than being tied to specific software releases. However, it does not affect legacy systems that do not use these modern authentication protocols for accessing Entra ID resources.
Where To Look First: Logs and Event IDs
To diagnose AADSTS70011 errors, you should first check the sign-in logs available in the Microsoft 365 admin center. Navigate to
https://portal.microsoftonline.com//reports/sa/signinEvents and filter for events that include "AADSTS70011" in their ErrorDetail field.
Additionally, you can inspect local log files on affected devices by checking the file located at
C:\ProgramData\Microsoft\IdentityManager\Logs\idaudit.log. Look for entries containing "AADSTS70011". This will provide context around when and how often this error occurs within your environment.
Event IDs related to OAuth authentication failures can also be useful. Specifically, Event ID 3402 in the
Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin log may indicate issues with token requests that lead to AADSTS70011 errors.
Root Causes
Typos or Malformed Scope Strings
One common cause is a typo in the scope string used by your application. For example, using
'https://graph.windows.net/.default' instead of the correct Microsoft Graph v2 format
'https://graph.microsoft.com/.default'. This can easily be caught by reviewing the exact log line from Entra ID sign-in logs.
Mismatched API Permissions
Another frequent issue is when an application attempts to use a scope that has not been granted permissions in its app registration within Entra ID. For instance, if your app requests
'User.Read' but this permission hasn't been added under the "API permissions" section of the app's configuration.
Deprecated API Endpoints
If an application is using a scope that targets a deprecated or retired API endpoint, it will also result in AADSTS70011. This often happens when older applications are not updated to use newer APIs as they become available.
Fix Procedure
- Navigate to the Microsoft Entra admin center and go to Identity > Applications > App registrations > select your application.
- In the API permissions section, verify that all necessary scopes are listed under Configured permissions. If any are missing, add them by clicking "Add a permission" and selecting from the available options for Microsoft Graph or other APIs.
- Use PowerShell to inspect the app's manifest for registered scopes: Run
(Get-MgApplication -ApplicationId ).RequiredResourceAccess.
- If you're using MSAL (Microsoft Authentication Library) in your application, ensure that the scope array is correctly configured. For example, use
scopes = ['https://graph.microsoft.com/.default'] for v2 endpoint compatibility.
- To prevent multi-resource scope request issues, configure each resource's scopes separately per token request if necessary.
Be cautious when making changes to API permissions as this can affect existing tokens and potentially break enrolled devices that rely on these permissions.
Error Code Variants
| Error Code | Description |
| AADSTS70011 | Invalid scope parameter in OAuth request |
| AADSTS50126 | Invalid client secret provided for the application |
| AADSTS70008 | The grant type is not supported by this service |
Verification
After applying fixes, you should verify that AADSTS70011 errors no longer appear in the sign-in logs. Additionally, check if your application can now successfully authenticate and receive tokens with the intended scopes.
You can also use PowerShell to confirm that the required API permissions have been correctly added to the app registration:
(Get-MgApplication -ApplicationId ).RequiredResourceAccess
Prevention
To prevent recurrence of AADSTS70011 errors, ensure that all applications are regularly reviewed and updated for compatibility with current API endpoints. Implement a policy to require developers to validate scope strings against the Entra ID documentation before deploying new authentication flows.
Additionally, consider implementing automated checks in your CI/CD pipeline to catch malformed or unsupported scope requests early in development cycles.