Skip to main content
  • Home
  • Get Help
  • Troubleshooting
  • Unable to send Outlook message - Failed to create a draft email in Microsoft Outlook Unable to create an email: The mailbox is either inactive, soft-deleted, or is hosted on-premise.
Question

Unable to send Outlook message - Failed to create a draft email in Microsoft Outlook Unable to create an email: The mailbox is either inactive, soft-deleted, or is hosted on-premise.

  • 12 February 2024
  • 7 replies
  • 302 views

I am trying to connect a work email to the Outlook account. The zap works with the laptop Microsoft account which is a gmail account; however, we want the emails to come from the work domain. The email is hosted on Network Solutions and is an active email. We use Microsoft Outlook as our email platform and the email works fine. When I test the connection in Zapier apps it passes. But when I test the zap, it returns the following message: 

Failed to create a draft email in Microsoft Outlook

Unable to create a draft email: The mailbox is either inactive, soft-deleted, or is hosted on-premise.

One article said to create an alias but you cannot use a work email as a gmail alias. 

 

7 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @Wendy222 

Help articles for using Outlook in Zap apps: https://zapier.com/apps/microsoft-outlook/help

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
W

Hello Troy,

Thank you for the response. Unfortunately those articles did not solve the problem. We ended up using gmail instead, which is not ideal. 

SamB
Rank
Userlevel 7
Badge +11

Hi @Wendy222 and @countervail 👋

Were you able to fix the issue by following Ken’s suggestion to ensure the connected mailbox has the correct permissions to grant Zapier the necessary access?

Keen to ensure you’re both all set so please let us know if you’re still in need of any further help at all!

W

Hello @SamB,

No, it did not work and we ended up turning off the zaps. We are using Outlook but not Exchange so that may be the problem. 

Thank you for the follow up. 

Wendy

C
Userlevel 1
Badge

We are getting the same message, our zap has been set up for several years so i think something must have changed at Zapier or Microsoft. Has anyone had any further thoughts on this?

ken.a
Userlevel 7
Badge +6

Hi @countervail,

I did some digging into this, and it seems like the full error of this issue is the MailboxNotEnabledForRESTAPI. Please ensure you have the right mailbox permissions: Microsoft accounts often have very strict permissions, access may need to be granted by an administrator to connect to third parties like Zapier. Submit a request to your Exchange or Global administrator to check on this. For reference: https://docs.microsoft.com/en-us/exchange/troubleshoot/user-and-shared-mailboxes/rest-api-is-not-yet-supported-for-this-mailbox-error#resolution

You should ensure you have all the right permissions with your O365 account. You can share the explicit error code with your Exchange admin to speed this up: MailboxNotEnabledForRESTAPI

Additionally, this is not something that can be changed within Zapier. Other users have posted about this same message on the Microsoft forums: https://learn.microsoft.com/en-us/answers/questions/930733/graph-api-send-mail-error-mailboxnotenabledforrest

Hopefully, this helps!

SamB
Rank
Userlevel 7
Badge +11

Thanks for the update @Wendy222. I’m sorry to hear that adjusting the permissions didn’t work either.

I did some checking and the Microsoft Outlook integration currently only works with Outlook accounts that are directly hosted on Exchange Online (cloud-hosted not self-hosted/on premises). So that could well have been why it was erroring in your case! 

I’d recommend reaching out to our Support team to put in a feature request to have non cloud-hosted accounts supported too. You can do that using the form here: https://zapier.com/app/get-help

In the meantime, do let us know if there’s anything else we can assist with! 🙂

Reply


Terms & Conditions