Azure App Registration with Microsoft Credentials in n8n Cloud

[Dorota_Maliszewska]

I’m trying to add Microsoft credentials to n8n. I watched several tutorials where people set it up through Azure — in their interface they have fields to enter Client ID, Client Secret, Tenant ID, etc.

In my case, I don’t see those fields at all. I only see a big “Connect my account” button.

I would prefer to connect it using my own Client ID and Client Secret instead of the automatic account connection.

What should I do to enable this option?

I already tried creating a credential manually with:

• Authentication: Generic Credential Type

• Generic Auth Type: OAuth2 API

• Connection Settings:

  • Grant Type: Client Credentials

  • Access Token URL: https://login.microsoftonline.com/{{ $vars.TenantID }}/oauth2/v2.0/token

  • Client ID: {{ $vars.ClientID}} (my app registration Client ID / App ID)

  • Client Secret: (my app registration secret token)

  • Scope: api://{{ $vars.ClientID}}/.default

  • Authentication: Header

But I don’t know how to actually connect and use this credential in my n8n nodes afterwards.

Does anyone know how to properly set this up?

[Erick_Torres]

In n8n Cloud Microsoft credentials, the UI only displays “Connect my account” (without Client ID/Secret/Tenant). This is intentional: Cloud uses OAuth apps managed by n8n; it doesn’t let you “bring your own app” with that type of credential. For self-hosting, however, the fields do appear, and you follow the classic flow of registering your app in Azure.

You can call Microsoft Graph with “Client Credentials” (app-only) → use “OAuth2 API” + HTTP Request
This works perfectly in Cloud, but it doesn’t “hook” the Microsoft nodes (Excel/Outlook/SharePoint) because they expect the “Microsoft… (Connect my account)” credential.