Microsoft outlook node unable to connect . error - 404 - The resource you are requesting could not be found

Help me Build my Workflow
,
1

Hello all. I’m building a workflow that starts with a connection to a client’s outlook email. The client is using https://outlook.office.com/.
I’m using n8n cloud.
In order to connect, I fist created a ‘Microsoft Outlook OAuth2 API’ credential (with the help of information provided in an earlier post). In summary, the admin connected to my local machine and logged in with an admin-email to provide n8n access.
But on trying to GET messages using the ‘Microsoft Outlook node’, I get this error response -

404 - The resource you are requesting could not be found.
The mailbox is either inactive, soft-deleted, or is hosted on-premise.

I have access to the email account and I have verified that it is active. And I’m able to send and receive emails from this account.
Any ideas on how to get to the root-cause of this issue ?
I’m trying to find ways to determine if the problem is on the n8n-side or some missing permissions on the microsoft admin side.
I’m working with the IT admin of the client and I’m not quite sure what I should be asking them to check find the problem.

Any ideas on trouble-shooting this would be helpful. TIA.

2

You authenticated with the admin’s email, not the actual mailbox user. If the admin logged in during the OAuth flow, the credential is now tied to the admin’s identity, not the client’s mailbox. I think you might need the OAuth to created by the exact mailbox user.

3

@davidh - thanks for the pointer. But is there a way to ascertain that that is indeed the case ? Like a place where I can find the ‘id’ that will determine the actual identity of the entity on behalf whom the request is being made ?

4

create a webhook node and a http node

  • using the HTTP node to call the webhook using the credentials you created.
  • examine the call in the webhook node, and check the token in the Authorization Header.
1 Like
5

Thank you @Tim_Yeung . That helped to view the Auth header and I was able to decode the JWT token to view details.
And @davidh - you were right that the credentials that were used were that of the admin’s and not the client’s mailbox.
So, I guess my next step would be to able to find a way to login with the exact mailbox user (which previously I wasn’t able to do as as I was hitting the ‘Need Admin Approval’ error message.]