When i try to send email through outlook node from n8n getting error likeThe mailbox is either inactive, soft-deleted, or is hosted on-premise.

Question

When i try to send email through outlook node from n8n getting error likeThe mailbox is either inactive, soft-deleted, or is hosted on-premise.

Aravind Babu Paritala 0

{

"errorMessage": "The resource you are requesting could not be found",

"errorDescription": "The mailbox is either inactive, soft-deleted, or is hosted on-premise.",

"errorDetails": {

"rawErrorMessage": [

  "404 - {\"error\":{\"code\":\"MailboxNotEnabledForRESTAPI\",\"message\":\"The mailbox is either inactive, soft-deleted, or is hosted on-premise.\"}}"

],

"httpCode": "404"
```  },

  "n8nDetails": {

```javascript
"nodeName": "Microsoft Outlook",

"nodeType": "n8n-nodes-base.microsoftOutlook",

"nodeVersion": 2,

"resource": "message",

"operation": "send",

"itemIndex": 0,

"time": "11/11/2025, 1:26:13 PM",

"n8nVersion": "1.90.2 (Self Hosted)",

"binaryDataMode": "default",

"stackTrace": [

  "NodeApiError: The resource you are requesting could not be found",

  "    at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:991:19)",

  "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",

  "    at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:1147:20)",

  "    at ExecuteContext.microsoftApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/Outlook/v2/transport/index.js:52:12)",

  "    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/Outlook/v2/actions/message/send.operation.js:271:3)",

  "    at ExecuteContext.router (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/Outlook/v2/actions/router.js:82:26)",

  "    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Microsoft/Outlook/v2/MicrosoftOutlookV2.node.js:38:12)",

  "    at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:681:27)",

  "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:915:51",

  "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1246:20"

]
```  }

}

1 answer

Your answer

Answer 1

Jack-Bu 5,405 Microsoft External Staff Moderator

Hello Aravind Babu Paritala

Thank you for reaching out to Microsoft Q&A regarding the issue with sending emails through the Microsoft Outlook node in your n8n workflow. This error (MailboxNotEnabledForRESTAPI) occurs when the Outlook REST API (via Microsoft Graph) cannot access the mailbox. Common causes include:

The mailbox is hosted on-premise (local Exchange Server) rather than in the cloud.
The account is inactive, soft-deleted, or lacks a valid Microsoft 365 license with Exchange Online.
Licensing or configuration issues in hybrid setups.

Your n8n setup authenticates successfully but fails during email sending, which aligns with mailbox accessibility restrictions. Here something you can do to fix this:

Verify Mailbox Status:
- Sign in to the Microsoft 365 admin center at admin.microsoft.com.
- Navigate to Users > Active users and ensure the account is active. If it's soft-deleted, restore it from Users > Deleted users.
Assign or Confirm License:
- In the admin center, select the user and go to Licenses and apps.
- Assign a Microsoft 365 license that includes Exchange Online (e.g., Business Basic/Standard or Enterprise plans). Save changes and allow time for updates to apply.
Migrate Mailbox if On-Premise:
- If your mailbox is on a local Exchange Server, work with your Exchange admin to migrate it to Microsoft 365. Use the Exchange Admin Center for hybrid setup and migration tools. Refer to Microsoft's official migration guide for detailed instructions: https://docs.microsoft.com/en-us/exchange/mailbox-migration/mailbox-migration.
Check App Permissions:
- In Azure AD, confirm your app registration has Microsoft Graph permissions like Mail.Send and Mail.ReadWrite, with admin consent granted.

After implementing these changes, retest your n8n workflow. Hope this will help you clear things up.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Aravind Babu Paritala 0 Reputation points

2025-11-11T15:57:42.25+00:00

hello @Jack-Bu i have configured above points 1,2,4 properly and regarding point 3 my mail box was there in gcp. Please find the attached screenshots for your reference, but still i am getting same issue
Jack-Bu 5,405 Reputation points Microsoft External Staff Moderator

2025-11-13T15:07:30.25+00:00
Hello Aravind Babu Paritala

Thank you for your update and for providing the screenshots. I appreciate the details about your setup, including that your mailbox was previously in GCP̣ (Google Cloud Platform). It looks like you've recently assigned the Exchange Online (Plan 1) license to the "Agent 9" user. Based on the information, this could stem from a few common scenarios, especially if this is post-migration from Google Workspace to Microsoft 365.

Assigning an Exchange Online license automatically starts mailbox creation, but it can take time to fully provision in the cloud, it may take up to 24 hours. Or even with the license, the mailbox could be in a pending state or not enabled for REST API access if it's a hybrid remnant or has provisioning errors. First, let use PowerShell for a detailed check:

Install the Exchange Online PowerShell module (if not already): Install-Module -Name ExchangeOnlineManagement.

Connect: Connect-ExchangeOnline -UserPrincipalName ******@domain.com.

Run: Get-Mailbox -Identity ******@domain.com | Select Name, RecipientTypeDetails.

If it returns "UserMailbox" under RecipientTypeDetails, it's provisioned in Exchange Online. If there's an error like "mailbox not found," it's not ready.

Next, you can test API Access Directly:

Use Microsoft Graph Explorer: Sign in with the "Agent 9" account, request the Mail.Send permission, and try a simple API call like GET /me/mailFolders. If it fails with the same error, the issue is indeed mailbox-side.

Hope this help.
Aravind Babu Paritala 0 Reputation points

2025-11-14T11:50:25.75+00:00

@Jack-Bu I am able to login through agent9 in outlook web and i was able to send email but from outlook getting same error.
1 day back i have cleared all cache and added few api permissions in azure it was worked after 1 day onwards same issue repeating
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Austin-H 6,990 Reputation points Microsoft External Staff Moderator

2025-12-01T06:19:00.36+00:00

Hello Aravind Babu Paritala
Thank you for your response.
Please check Jack's above answer and try to use a simple API to see if the this is the mailbox issue.
Could you also clarify what steps have you taken specifically when you stated that you cleared all cache? Which permissions did you add that are different from the earlier screenshot?
I am looking forward to your reply.
Aravind Babu Paritala 0 Reputation points

2025-12-01T08:08:07.5366667+00:00

Hello @Austin-H
I have created the api and tested still same issue .
Using Microsoft Graph Explorer i was able to send email with same mail id or account.
Regarding permissions please find the below image and i have highlighted newly added ones with yellow color. And i have removed cache multiple times
Austin-H 6,990 Reputation points Microsoft External Staff Moderator

2025-12-02T05:08:44.3466667+00:00

Hi Aravind Babu Paritala
Thank you for your response.
Upon reviewing your API permission, I do not see any issues in here and you also confirmed that using Graph Explorer you were able to send email with same email id or account. This also means that the license and the mailbox itself is normally working.

I also checked on N8N community and saw your replies there along with another person who also faced the same issue.
Did you check on this thread with N8N Team's answer: https://community.n8n.io/t/microsoft-outlook-client-authentication-failed/228788/10
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link

Are you able to test this using another mailbox-enabled account to see if the issue still persists?

Share via

When i try to send email through outlook node from n8n getting error likeThe mailbox is either inactive, soft-deleted, or is hosted on-premise.

1 answer

Your answer