How to Send Emails from Shopify Flow Using Microsoft 365 or Outlook.com
Shopify Flow can’t send a custom email on its own. MailAction adds a Send transactional email action to Flow and sends each message through an email provider you connect. Microsoft is one of them. It works with a Microsoft 365 (formerly Office 365) mailbox on your own domain and with a personal Outlook.com or Hotmail account.
There are two ways to connect. For most stores, signing in with Microsoft is the quickest, and it works even when SMTP is turned off for your mailbox. SMTP is there for the cases sign-in doesn’t cover.
What You'll Need
- A Shopify store on a plan that includes Shopify Flow
- MailAction installed on your store
- A Microsoft 365 mailbox with an Exchange Online license, or a personal Outlook.com or Hotmail account
Option 1
Sign In with Your Microsoft Account
You sign in to Microsoft, and MailAction gets permission to send email from that account. It can only send. It can’t read, change or delete anything in your mailbox. You can remove its access at any time: at myapps.microsoft.com for a work account, or at account.live.com/consent/Manage for a personal one.
Emails go out from the address you sign in with, and they show the name on that Microsoft account. Replies go to the reply-to address in MailAction’s sender details, or to the account’s address if you didn’t set one. If you need a different From address, use option 2 instead.
This option doesn’t use SMTP, so it works when Microsoft has turned SMTP off for your mailbox. That’s the setting behind the “5.7.139 Authentication unsuccessful” error.
Step 1Pick the Account You'll Send From
Sign in with the account whose address customers should see. On Microsoft 365, a dedicated mailbox like [email protected] keeps automated mail out of someone’s personal inbox. For a small store, a personal Outlook.com address is fine.
A Microsoft 365 account needs an Exchange Online license. Without one, there’s no mailbox to send from. In the Microsoft 365 admin center, under Users → Active users, a licensed user has a Mail tab.
Step 2Check the Name on the Account
MailAction can’t set the sender name for this option, so emails use the name on the Microsoft account. Your store name is usually the right choice.
- Personal account: sign in at account.microsoft.com, open Your info, and edit your name
- Microsoft 365: an admin changes the user’s display name in the Microsoft 365 admin center under Users → Active users
Step 3Open the Connect Dialog in MailAction
Step 4Sign In with Microsoft
Click Connect Microsoft account. A Microsoft window opens. Pick the account, check what MailAction asks for, and click Accept.
The window closes and MailAction shows the account as connected. The first provider you connect becomes your Primary, and all email goes through it.
Common Issues When Signing In
Microsoft says you need admin approval, or “Your organization needs an admin to approve MailAction”
- Some organizations only let admins approve apps. Ask your Microsoft 365 admin to approve MailAction
- If your organization uses admin consent requests, your admin finds yours in the Microsoft Entra admin center under Enterprise apps → Admin consent requests. Once they approve it, click Connect Microsoft account again
“MailAction needs permission to send email”
- The Microsoft screen asked for permissions and they weren’t accepted. Click Connect Microsoft account again and accept them
The Microsoft window didn’t open, or nothing happens after signing in
- Your browser may have blocked the pop-up. Allow pop-ups for admin.shopify.com, or use the Open Microsoft sign-in link MailAction shows while it waits
- Keep the MailAction tab open until the Microsoft window closes. MailAction checks for the result in the background
Emails fail with “MailboxNotEnabledForRESTAPI”
- The account you signed in with has no mailbox MailAction can send from. For Microsoft 365, ask your admin to check that the user has an Exchange Online license. Then send a test email again
Emails fail with “Microsoft access was revoked or has expired”
- Microsoft stopped accepting MailAction’s access. This happens when the password changes, when someone removes MailAction from the account’s apps, or when an admin changes sign-in rules. Open the provider in MailAction and click Reconnect Microsoft account
Emails fail with “ErrorMessageSubmissionBlocked”
- Microsoft has blocked the account from sending, often after a lot of email went out in a short time
- For a personal account, sign in at outlook.com to see the notice and unblock it
- For Microsoft 365, ask your admin to unblock the account in the Microsoft Defender portal under Restricted entities
Option 2
Connect Microsoft 365 over SMTP
MailAction’s Custom SMTP option connects to Microsoft 365 with a host, port, username and password. It takes more setup than signing in, but you can send from a shared mailbox or another address your account is allowed to send as. This option is for Microsoft 365 only. For a personal Outlook.com account, use option 1.
Microsoft 365 turns SMTP off for most mailboxes, so most of the work happens on the Microsoft side.
Microsoft is also phasing out sign-in with a username and password over SMTP, which this option relies on. It’s scheduled to be off by default for existing tenants from the end of December 2026 (an admin can still turn it back on), and off from the start for tenants created after that. If that happens to you, switch to option 1.
What you'll need
- A Microsoft 365 mailbox with an Exchange Online license
- Microsoft 365 admin access, or an admin who can change a few settings for you, since SMTP is off by default
Step 1Turn On SMTP for the Mailbox
Microsoft 365 calls SMTP sending Authenticated SMTP and turns it off for most mailboxes. Turn it on for the mailbox you’ll send from.
In the Microsoft 365 admin center, go to Users → Active users, select the mailbox, open the Mail tab, and click Manage email apps. Check Authenticated SMTP and save. (Admins who prefer PowerShell can run Set-CASMailbox -Identity [email protected] -SmtpClientAuthenticationDisabled $false instead.)
Two settings for the whole organization can still block SMTP after that:
- Security defaults. When security defaults are on, SMTP sign-in with a password is blocked for everyone, whatever the mailbox setting says. An admin has to turn them off, or exclude the sending account with a Conditional Access policy.
- The organization-wide SMTP setting. An admin can check it with
Get-TransportConfig | Format-List SmtpClientAuthenticationDisabled. If it saysTrue, SMTP is off for everyone and the mailbox checkbox won’t help until it’s changed.
Step 2Choose the Password
Which password you use depends on whether the mailbox has multifactor authentication (MFA).
No MFA: use the mailbox’s normal password.
MFA on: the normal password won’t work, because SMTP can’t answer an MFA prompt. Use an app password instead. Sign in as that user at mysignins.microsoft.com/security-info, choose Add method → App password, name it something like “MailAction”, and copy it. Microsoft shows it only once.
Some organizations that require MFA through Conditional Access don’t offer app passwords at all. If that’s yours, use option 1 instead.
Step 3Find Your Microsoft 365 SMTP Settings
The settings are the same for every Microsoft 365 organization:
- Host:
smtp.office365.com - Port:
587 - Username: the mailbox’s full email address
- Password: the mailbox password, or the app password from the previous step
Use port 587. Microsoft 365 doesn’t accept port 465 at this host, and port 25 is blocked for this kind of sending.
Step 4Connect Microsoft 365 in MailAction
In MailAction, open Settings, click Add provider, and choose Custom SMTP. Enter host smtp.office365.com, port 587, the full mailbox address as the username, and the password or app password.
Microsoft 365 sends as the mailbox you sign in with. To use a different name or address, turn on Override sender and fill them in. Microsoft 365 rejects a From address the mailbox isn’t allowed to send as (see the common issues below).
Click Connect. MailAction tests the connection before saving, so a wrong password or SMTP still being off shows up right away. The first provider you connect becomes your Primary.
Common Issues When Connecting over SMTP
“535 5.7.139 Authentication unsuccessful”
- Check that Authenticated SMTP is on for the mailbox under Users → Active users → Mail → Manage email apps. It’s off for most mailboxes, and it’s the most common cause
- If the mailbox has MFA, use an app password instead of the normal password
- Check whether security defaults are on. They block SMTP for everyone and override the mailbox setting
- If you can’t turn SMTP on, use option 1. It doesn’t need SMTP
“535 5.7.3 Authentication unsuccessful” right after turning SMTP on
- The change can take up to an hour to apply. Wait, then click Connect again
- If it still fails, check security defaults and the password, or use option 1
“550 5.7.30 Basic authentication is not supported for Client Submission”
- Your organization no longer accepts SMTP sign-in with a password. Switch to option 1
“5.7.60 Client does not have permissions to send as this sender”
- Microsoft 365 only lets a mailbox send as itself unless it has permission for another address. Check the From address in MailAction’s sender details and in Override sender. It has to match the mailbox exactly
- To send as another address, such as a shared
support@mailbox, an admin gives this mailbox Send As permission for it in the Exchange admin center
“Connection timed out”
- Check that the host is exactly
smtp.office365.comand the port is587. Port465won’t work at this host
After You Connect Microsoft
Step 1Send a Test Email
Step 2Add the Action to a Flow Workflow
Open Shopify Flow, create a workflow and pick a trigger, such as Order created. Add the Send transactional email action. It shows up in the action list once MailAction is installed.
Fill in the recipient (it can come from the trigger, like the customer’s email), a subject line and the HTML body. There’s also an optional preview text field for the snippet inboxes show. You can use Liquid in the body to pull in order details, customer names and other workflow data.
Save the workflow and turn it on. Then place a test order and check MailAction’s sent emails log to confirm it went out.
Common Issues
Sends stop or fail with a sending-limit error
- A Microsoft 365 mailbox can send to about 10,000 recipients a day and about 30 messages a minute. Personal Outlook.com accounts have much lower limits, especially new ones
- Connect a second provider in MailAction as a Fallback so emails keep going out if Microsoft stops. If you regularly get close to the limit, Resend or SendGrid are a better fit for your volume
No delivery status for Microsoft emails
- Microsoft doesn’t tell MailAction whether an email was delivered, bounced or marked as spam, so the sent emails log only shows whether Microsoft accepted it. For delivery tracking, use an API provider like Resend, SendGrid, Mailgun or Postmark