Outbound from your Microsoft 365 mailbox
Same model as Gmail: your mailbox, your domain, your reputation. Connected over OAuth with no stored credentials.
Auth
Microsoft OAuth
Warmup
Paced automatically
Reply sync
Two-way, threaded
Suggested cap
~50 sends per mailbox per day
What it does
Sequences send through your Microsoft 365 or Outlook account. Replies are detected and mirrored onto the contact record, sequences stop on reply, and warmup runs on the same mailbox before campaign volume is permitted.
Microsoft's filtering behaves differently from Google's, and recipient mix matters: a list weighted towards Outlook-hosted domains behaves differently from one weighted towards Gmail.
Setting it up
- Set up a separate sending domain in Microsoft 365, distinct from your primary.
- Publish SPF, DKIM and DMARC, then confirm each passes on a test send.
- Connect the mailbox in Autocloz through Microsoft OAuth.
- Run warmup for at least 21 days before campaign volume.
- Monitor bounce and complaint rates; pause the ramp if either climbs.
Limits worth knowing
- Microsoft 365 applies tenant-level throttling that Autocloz cannot raise.
- Some tenants have outbound restrictions set by an administrator that need lifting first.
- Shared mailboxes are not suitable for sequence sending.
- Microsoft is generally stricter than Google on new-domain traffic, so ramp more conservatively.
Common questions
Does this work with on-premise Exchange?
The integration targets Microsoft 365. On-premise setups vary too much to support reliably.
Can I use a shared mailbox?
Not for sequences. Use a dedicated user mailbox so reputation and limits are attributable.
Why is my Outlook deliverability worse than Gmail?
Microsoft weights new-domain traffic more harshly. A slower ramp and stricter list hygiene usually close the gap.
Connect Outlook in a few minutes
Free forever, up to 5 users, no card.