Using Azure App Registration with Microsoft Credentials in n8n Cloud

Describe the problem/error/question

I’m trying to configure Microsoft Graph API integrations using the client credentials flow via an Azure App Registration** (i.e., using a client_id, client_secret, tenant_id, and .default scope). However, most Microsoft-related credential types in n8n (including **Microsoft OAuth2 API, Microsoft Teams, Outlook, and SharePoint) only expose the delegated login method via the “Connect my account” button.

This makes it difficult to use non-expiring, service-to-service authentication for long-running or automated workflows, where we don’t want to rely on personal logins or user reauthentication.

Is there a way to enable or access the manual configuration option for the Microsoft credential types so we can authenticate via client credentials instead of delegated login?

Ideally, we’d like to use this approach with:

  • Microsoft OAuth2 API
  • Microsoft Teams OAuth2 API
  • Microsoft Outlook OAuth2 API
  • Microsoft SharePoint OAuth2 API

We want to securely access Microsoft Graph across multiple services using our app-registered identity.

We’ve seen examples of manually configured Microsoft OAuth2 credentials in other n8n setups and would like to know if this is currently supported in n8n Cloud (Pro) — and if so, how to enable it.

What is the error message (if any)?

No error per se — the issue is with the credential setup limitation.
Manual client credential fields (like client ID, secret, and tenant) are not exposed in the UI for the affected Microsoft credential types.

Information on your n8n setup

  • n8n version: 1.98.1
  • Running n8n via: n8n cloud (Pro)
1 Like

Any update on this Brad? In a similar situation.

I’m also looking for something like this. I have an idea of what the application permissions would need to be in Graph and I feel like the http node would be the closest to retrieving the data but I’m not 100% sure of the exact config and I might be going completely in the wrong direction :upside_down_face:

Also in a similar boat, using n8n cloud. The automatically generated permissions aren’t suitable for a range of different workflows. Made a similar post about this here: Issue utilising Microsoft node functions with default permissions in n8n cloud

Unfortunately no feedback yet :frowning: