BadRequest

Microsoft Graph rejected the request

Answer: The request shape, property value, query option, or operation is invalid for the target endpoint.

Resolution playbook

Fix it, then prove it

Use the error record as the starting point; use tenant evidence to confirm the actual cause.

A generic HTTP 400 is only the envelope; the Graph error body contains the useful cause.
The token is missing, expired, for the wrong audience, or contains the wrong delegated/application permission type.
Consent, Microsoft Entra role, licensing, resource ownership, or endpoint-specific authorization is still insufficient.

Read the inner error message and target property.
Validate the body against the endpoint's current request schema.
Reduce the request to a minimal call, then add query options or properties back deliberately.

Acquire a new access token after permissions or consent change.
Confirm delegated permissions appear in scp or application permissions appear in roles, and that aud targets Microsoft Graph.
Repeat the exact HTTP method and endpoint and confirm the response no longer returns the same request ID/status.

The failure persists after the documented prerequisites and a new authentication/session attempt.
Multiple users, apps, devices, or networks show the same error, suggesting tenant policy or service scope.
You can provide the exact UTC time, tenant, application/resource, correlation or request ID, and sanitized logs.

Inspect the active Graph PowerShell context

Get-MgContext | Select-Object ClientId,TenantId,Account,AuthType,Scopes

Read-only. Confirms tenant, auth type, and delegated scopes. For app-only tokens, also inspect the token roles claim.

A generic HTTP 400 is only the envelope; the Graph error body contains the useful cause.