Describe the problem/question:
I’m using n8n Cloud and trying to connect a Customer Service mailbox via the Microsoft OAuth2 API (Outlook integration).
When I go through the OAuth flow, I log in with the service mailbox account (for example support@…).
However, when I’m asked to grant admin consent, I must sign in with my admin account.
Once I approve with the admin account, the connection in n8n ends up being tied to the admin user instead of the service mailbox.
So even though I authenticate using the service mailbox address, n8n links the admin user as the connected identity.
My question:
Why does this happen, and how can I correctly connect the service mailbox (or shared mailbox) so the integration runs under that identity, not the admin one?
What I’ve already tried:
- Logging in with the service mailbox and granting admin consent when prompted → admin user gets linked.
- Giving admin consent in advance in the Azure Enterprise App → same result after OAuth flow.
- Explicitly setting the shared mailbox address in the node/credential → still the admin identity is used.
Expected behavior:
The credential should connect and operate under the service/shared mailbox account (e.g., support@…) rather than the admin account.
Information on your n8n setup:
- n8n version: Latest n8n Cloud version
- Running n8n via: n8n Cloud
- Credential type: Microsoft OAuth2 API