Outlook and Microsoft 365 mailbox sending solves the same customer-trust problem as Gmail: review request emails come from the customer's real address instead of the agency sender.
This guide is specifically about the customer-side Outlook flow. Agency-side SMTP remains covered in the SMTP for Agencies guide.
What you need first
- An Outlook.com, Hotmail, or Microsoft 365 account
- The account password, or an App Password if 2FA is enabled
- The customer plan must have `Email Provider` enabled
| Account type | Daily limit |
|---|---|
| Outlook.com or Hotmail | 300 emails per day |
| Microsoft 365 | 10,000 emails per day |
What the agency has to do first
From the agency side, go to `Business -> Billing & Revenue -> Plans`, edit the customer plan, and enable `Email Provider` in the campaign settings.
Prepare the password
If the Microsoft account does not use 2FA, the normal password can work. If 2FA is enabled, the customer should create an App Password through Microsoft security settings before starting the wizard.
What the customer setup flow looks like
Like the Gmail flow, this setup is intentionally stripped down so business owners do not have to think about SMTP hosts, ports, or encryption.
- Choose Outlook from the two large provider cards
- Enter the Outlook or Microsoft 365 email address
- Enter the account password or App Password
- Verify the connection and send a test email
What happens after setup
Once Outlook is connected, that mailbox takes priority in the 3-tier email routing system and review request emails start going out from the customer mailbox.
- Recipients see the customer's real Outlook or Microsoft 365 address
- This usually improves trust and open rates
- Customer-owned Outlook sending does not consume the normal customer plan email credits
Common issues
- Using the normal password when 2FA requires an App Password
- Hitting Outlook.com daily limits on smaller accounts
- Shared mailbox sending limits being exhausted across too many uses