Low severityauthentication
Power BI Error:
AADSTS900144, Missing required request parameter
What does this error mean?
The OAuth 2.0 token request is missing a required parameter (typically client_id, grant_type, scope, or code).
Common causes
- 1The token request body is missing 'client_id' — common when the app registration's client ID isn't passed in form-encoded body for the /token endpoint
- 2Missing 'grant_type' parameter (e.g. authorization_code, client_credentials, refresh_token) in the POST body
- 3Missing 'scope' or 'resource' parameter when requesting an access token for Power BI / Fabric / Dataverse APIs
- 4Missing 'code' on authorization_code flow, or 'refresh_token' on a refresh flow — often caused by the upstream auth step failing silently
- 5Parameters sent as query string or JSON instead of application/x-www-form-urlencoded body, so Entra ID doesn't see them
How to fix it
- 1Read the exact parameter name in single quotes in the error message — that is literally the field you must add to the request body
- 2Verify the request is POSTed to https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token with Content-Type: application/x-www-form-urlencoded, and that all OAuth parameters are in the body (not the URL)
- 3For Power BI / Fabric service principal flows, ensure client_id, client_secret (or client_assertion), grant_type=client_credentials, and scope=https://analysis.windows.net/powerbi/api/.default are all present
- 4If you're using a Linked Service in Azure Data Factory or a Databricks Power BI connector, re-enter the Application (client) ID and secret — a blank/expired secret often shows up as a missing-parameter error from the SDK layer
- 5Capture the raw HTTP request with Fiddler / a network trace and compare against Microsoft's OAuth 2.0 docs to spot the missing field