Microsoft 365 / Outlook works the same way as Gmail in our integration: we don't send through your Outlook mailbox. Microsoft's hosted email service isn't optimised for automated outbound and applies throttling/deliverability rules that don't fit AI follow-up sequences.
Instead, outbound automation goes through a Mailgun-authenticated sending subdomain on your business domain. Your team keeps using Outlook for human work, replies route back to our unified inbox, and follow-up sequences halt automatically when a human jumps in.
Popular workflow recipes
When this happens → do thatTriggers & Actions
3 triggers · 3 actionsAI sequence halts; reply visible in both Outlook and unified inbox.
Suppress contact from future sends.
Standard Mailgun-side handling.
Routes through Mailgun-authenticated sending subdomain.
Team keeps using Outlook for one-to-one human replies.
AI sequences pause when a teammate replies.
How to connect Outlook / Microsoft 365
~10 minutes- Microsoft 365 mailbox API access is not used because Microsoft's per-mailbox sending rules are not designed for automated outbound at scale.