Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | AADSTS70011: The request is missing a required parameter... | AAD sign-in logs | OAuth2 malformed request |
| Affected OS build | 22621.x (Windows 11 23H2) | winver | All 23H2 builds |
| Registry/OMA-URI | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EntraID\OAuth | Registry Editor | OAuth configuration |
| Service endpoint | https://login.microsoftonline.com | AAD API request | Token issuance endpoint |
| Log line signature | OAuth2ErrorCode=AADSTS70011, Scope=Calendars.Read | Azure AD Sign-In Logs | Missing delegated permission |
Log Files to Check
C:\ProgramData\Microsoft\EntraID\Logs\AADSigninLogs.csvC:\AzureAD\Logs\AuditLogs_20240520.csv
What This Error Actually Means
TheAADSTS70011 error is a specific OAuth2.0 authentication failure raised by the Azure AD (now Entra ID) authentication service. The error string "The request is missing a required parameter" indicates that the client application failed to include a mandatory parameter in its token request, such as scope, client_id, or redirect_uri. This error is typically triggered when an application attempts to access a protected resource (e.g., Microsoft Graph APIs) without being explicitly granted the required permissions. The component responsible for this error is the Microsoft Online Services Sign-In Service, which validates OAuth2.0 requests against the tenant's app registration and consent policies. Specifically, the Calendars.Read scope in the log line points to a missing or unapproved permission for calendar data access.
Affected Versions and Scope
This error occurs on **Windows 11 23H2 (OS build 22621.x)** when applications configured for Entra ID authentication attempt to access APIs requiring unapproved scopes. It is not observed in older OS builds (e.g., 21H2 or earlier) unless the tenant's app registration is misconfigured. The issue is isolated to tenants where the client application lacks delegated or application permissions for the requested scope. It does **not** affect applications using client credentials flow (non-interactive) unless the service principal is missing API permissions. The error is also absent in scenarios where admin consent has been explicitly granted for the required scope.Where To Look First: Logs and Event IDs
Begin by inspecting theC:\ProgramData\Microsoft\EntraID\Logs\AADSigninLogs.csv file for the exact log line:
OAuth2ErrorCode=AADSTS70011, Scope=Calendars.Read.
Cross-reference with the C:\AzureAD\Logs\AuditLogs_20240520.csv file for audit records of failed consent requests. In the Windows Event Viewer, check **Event ID 4625** (failed logon) in the Security log and **Event ID 5145** (OAuth2 request failure) in the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin log. Use PowerShell to extract relevant logs:
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 | Where-Object Message -Match "AADSTS70011".
Root Causes
1. Missing Delegated Permissions in App Registration
The client application's Entra ID app registration lacks theCalendars.Read delegated permission. Verify in the **Entra admin center > Applications > Enterprise Applications > [App Name] > API Permissions**. If the permission is absent, it must be added and admin consent granted.
2. Admin Consent Not Granted
Even if the permission is added, it may remain in a "Pending" state until an admin approves it. Check the **Consent Status** column in the API Permissions blade. Use PowerShell to force consent:Grant-MgApplicationPermission -ApplicationId "APP_ID" -Scope "Calendars.Read".
3. Incorrect Redirect URI
The OAuth2.0 request may specify a redirect URI not configured in the app registration. Validate theRedirectUris property using:
Get-MgApplication -ApplicationId "APP_ID" | Select-Object RedirectUris.
Fix Procedure
- Navigate to the **Entra admin center > Applications > Enterprise Applications** and select the affected app.
- Under **API Permissions**, click
+ Add a permission, selectMicrosoft Graph, and add theCalendars.Readdelegated permission. - Grant admin consent by clicking
Grant admin consentin the API Permissions blade. - If registry modifications are required, update the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EntraID\OAuthkey with the correctClientIdandRedirectUrivalues. - Use PowerShell to verify and update permissions:
Get-MgApplication -ApplicationId "APP_ID" | Add-MgApplicationApiPermission -PermissionScope "Calendars.Read"Update-MgApplication -ApplicationId "APP_ID" -Api $apiPermissionsInvoke-MgGraphRequest -Method PATCH -Uri "https://graph.microsoft.com/v1.0/applications/APP_ID" -Body $apiPermissions - For Intune-managed devices, deploy the fix via an OMA-URI policy:
./Device/Vendor/MSFT/EntraID/OAuth/ClientId./Device/Vendor/MSFT/EntraID/OAuth/RedirectUri
Modifying registry keys under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EntraID may disrupt device enrollment if incorrect values are applied. Always test in a non-production environment first.Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
| AADSTS70011 | Missing required OAuth2 parameter | Log line includes OAuth2ErrorCode=AADSTS70011 and a specific scope |
| AADSTS70001 | Invalid client credentials | Occurs when client_id or client_secret is incorrect |
| AADSTS65001 | Consent required | User or admin consent is pending for the requested scope |
Verification
After applying fixes, monitorAADSigninLogs.csv for successful sign-in events with OAuth2ErrorCode=none. Use PowerShell to confirm permissions are granted:
Get-MgApplication -ApplicationId "APP_ID" | Select-Object Api.
In the Entra admin center, verify the API Permissions blade shows Granted status for Calendars.Read. For device-specific validation, run dsregcmd /status to ensure Entra ID registration is active.
Prevention
Implement a baseline policy in Intune to enforce app permission requirements: - Use the **Intune admin center > Policies > App management policies** to restrict unapproved API scopes. - Schedule PowerShell scripts to audit app registrations:Get-MgApplication | ForEach-Object { Get-MgApplicationApiPermission -ApplicationId $_.Id }.
- Enforce admin consent via the **Entra admin center > External Identities > Consent and permissions > Manage consent requests**.
- Regularly review audit logs in C:\AzureAD\Logs\AuditLogs_*.csv for unauthorized scope requests.
Use
Get-AzGraphAccessToken in PowerShell to quickly test OAuth2 token requests and validate scope approvals without triggering errors.