N8n Cloud (Pro) – Microsoft Teams OAuth fails: AADSTS7000222 expired client secret for app aad843ca-42a7-4219-a3f9-91bcf621d795

Questions
1

Hi n8n team,
We’re on n8n Cloud (Pro). Our Microsoft Teams integration stopped working.
When we try to reconnect the Microsoft Teams credential (“Connect my account”), OAuth fails with:
error: invalid_client
AADSTS7000222: The provided client secret keys for app ‘aad843ca-42a7-4219-a3f9-91bcf621d795’ are expired.
Timestamp: 2026-01-14 08:06:29Z
Trace ID: 9c9e8a04-d496-4406-996d-cd2ce2b72d00
Correlation ID: 0e88da54-bf23-4ac3-93d4-d2b48dbb8eee
Because we are using n8n Cloud, we only have “Connect my account” and cannot change Client ID/Secret on our side.
Can you please rotate/renew the client secret for the n8n Cloud Microsoft OAuth app (aad843ca-…)?
n8n setup:

instance information

Debug info

core

  • n8nVersion: 1.123.6
  • platform: docker (cloud)
  • nodeJsVersion: 22.21.0
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 50
  • license: enterprise (sandbox)
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/142.0.0.0 safari/537.36
  • isTouchDevice: false
    Generated at: 2026-01-14T11:36:36.815Z

Thanks,
Yadhav

1 Like
3

so this is actually on n8n’s side - that app ID (aad843ca-…) is n8n Cloud’s shared OAuth app for Microsoft Teams, and if the client secret expired they need to rotate it.

you cant fix this yourself since youre using the managed cloud credential. best bet is to ping @[n8n team members] directly here or open a support ticket through your cloud dashboard - they should be able to renew the secret pretty quickly.

in the meantime if you need it working asap, you could create your own Azure app registration and use the “OAuth2 API” credential type with your own client ID/secret, but that’s more setup.

4

so this is an n8n cloud infrastructure issue - that client secret is managed by n8n’s backend team, not something you can fix on your end. you need to reach out to n8n support directly since this requires them to rotate the expired secret for their Microsoft Teams OAuth app.

quickest way is through the support widget in your n8n cloud dashboard (bottom right corner usually) or email [email protected] with that trace ID. include the error details you posted here - they should be able to rotate it pretty fast since it’s affecting cloud users.