Microsoft Outlook OAuth fails with AADSTS900144: missing 'scope' parameter

Questions
,
1

Hi,
I’m using n8n Cloud v2.30.8.
When creating a new Microsoft Outlook credential using Managed OAuth2 (recommended), clicking “Connect” redirects to Microsoft but immediately returns:
AADSTS900144: The request body must contain the following parameter: ‘scope’.
This happens:

  • In a brand new workflow
  • With a brand new Microsoft credential
  • Using Microsoft Outlook nodes (Create Draft / Get Many Messages)
    Gmail OAuth works correctly in the same n8n Cloud instance.
    Could you please advise whether this is a known issue or if there is a workaround?
    Thanks.

Describe the problem/error/question

What is the error message (if any)? AADSTS900144: missing ‘scope’ parameter

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hi @JonnyPix Welcome!
On “Managed OAuth2 (recommended)” n8n builds the Microsoft sign-in request and sets the scopes for you, so AADSTS900144 means the managed Microsoft flow is sending Microsoft an authorize request with no scope. You can’t change scopes in managed mode, and Gmail working confirms it’s specific to the managed Microsoft app, not your instance.

Workaround you can use now: skip the managed option and set up a standard Microsoft Outlook OAuth2 API credential with your own Azure app. Register an app at portal.azure.com, copy the OAuth Redirect URL shown in the n8n credential panel and add it in Azure under Redirect URIs as a Web URI, then paste the Client ID and Client Secret into n8n and click Connect. This flow sends the scopes itself and gets past the error.

The managed flow can only be fixed on n8n’s side, so report it so they can patch the managed Microsoft app: help@n8n.io

3

Thanks for letting us know about this, We have created IAM-1052 as the internal dev ticket to look into it.