Microsoft Teams & OneDrive Node - Unable to connect Account (Enterprise Tenant)

Describe the problem/error/question

I have configured all the required permissions in Microsoft Entra as specified in the n8n credentials for the Microsoft Teams Trigger node:


Despite this, I am unable to connect the account.

I’m running n8n locally via npm. The application is registered in MS. For comparison, other nodes like SharePoint work without issues. In general the application and the technical user works IMHO.

Additionally, it appears that the permission Subscription.ReadWrite.All does not exist in Microsoft Graph. This is confirmed in the official Microsoft documentation: Microsoft Graph permissions reference.

Find output after trying to connect “Connect my account” below.

Besides the Teams Credentials I’m also struggling with the same issue in the “Microsoft Drive account” credentials. Which permissions must be enabled in Entra ID? I can’t find any hint or documentation from n8n side.

Looking forward to get some input how to connect the MS nodes in n8n in enterprise context.

What is the error message (if any)?

Please share your workflow

Credentials Only, no workflow yet developed

Share the output returned by the last node

Information on your n8n setup

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

Based on the recent issues reported with Microsoft Teams and OneDrive nodes, it looks like you’re encountering a known problem. The permission `Subscription.ReadWrite.All` that n8n documentation mentions doesn’t actually exist in Microsoft Graph - this appears to be a documentation error that’s affecting multiple users.

For a workaround, try these steps:

• Skip the `Subscription.ReadWrite.All` permission since it doesn’t exist

• Ensure you have admin consent for all the other permissions (`ChannelMessage.Read.All`, `Chat.Read.All`, `Team.ReadBasic.All`)

• Check if your Azure app registration is set to “Accounts in any organizational directory” rather than single tenant

• Try re-creating your credentials in n8n after confirming the permissions are properly consented

You can track this issue on [GitHub](Intermittent Unable to sign without access token Error When Listing Items via OneDrive Node (No download files and no authenticator) · Issue #12694 · n8n-io/n8n · GitHub) where similar authentication problems with Microsoft nodes are being reported. The n8n team appears to be aware of these Microsoft integration issues in recent versions.