Getting Started

Connect Microsoft 365

Connect a Microsoft 365 or Outlook mailbox via OAuth or an app password, including the SMTP AUTH admin requirement.

You can connect a Microsoft 365 mailbox two ways: OAuth (one click, when available) or an app password over SMTP/IMAP. The app password path has an extra wrinkle on Microsoft: SMTP AUTH must be enabled for the mailbox by an admin, and many tenants have it off by default.

Option 1: OAuth (one click)

When OAuth connect is available, choose Microsoft in the Add mailbox flow, sign in with the mailbox you want to warm, and approve access. No hosts, ports, or app passwords needed. Continue with the quickstart to configure warmup.

Option 2: App password over SMTP/IMAP

Prerequisites

Two things must be true before this path can work:

  1. Two-factor authentication is enabled on the account. Microsoft only issues app passwords to accounts with 2FA (multi-factor authentication) turned on.
  2. SMTP AUTH is enabled for the mailbox. An admin does this in the Microsoft 365 admin center: UsersActive users → select the user → MailManage email apps → check Authenticated SMTP. It can also be enabled tenant-wide, but per-mailbox is the safer ask.

If SMTP AUTH is disabled, authentication fails no matter how correct your app password is — typically with an error mentioning "SmtpClientAuthentication is disabled for the Tenant". This is the single most common Microsoft 365 connection failure. Ask your admin to enable Authenticated SMTP for the mailbox first.

Create the app password

  1. Sign in to your Microsoft account security settings.
  2. Under additional security options, create a new app password (available once 2FA is on).
  3. Copy the generated password — it's shown once.

Enter the settings

In the Add mailbox flow, choose SMTP/IMAP and enter:

FieldValue
SMTP hostsmtp.office365.com
SMTP port587
IMAP hostoutlook.office365.com
IMAP port993
UsernameYour full email address
PasswordThe app password

Note the hosts differ between SMTP and IMAP — that's correct for Microsoft. Turn on use same credentials so the IMAP login reuses your username and app password, set your sender name, and run the connection test. It performs a real SMTP verification and IMAP login; nothing is saved until both pass.

Troubleshooting

"535 5.7.3 Authentication unsuccessful"

  • SMTP AUTH is disabled for the mailbox or tenant — the most likely cause. See the admin steps above.
  • You're using the account password instead of an app password.
  • Your tenant uses Security Defaults or a Conditional Access policy that blocks legacy authentication entirely. In that case app passwords won't work at all — use OAuth instead.

App password option missing

The option only appears when 2FA is enabled, and some tenants disable app passwords by policy. If you can't create one, OAuth is the way forward.

SMTP passes but IMAP fails

Check that IMAP is enabled for the mailbox (same Manage email apps panel as SMTP AUTH — look for IMAP), and confirm the IMAP host is outlook.office365.com, not smtp.office365.com.

IMAP access is required, not optional: your mailbox uses it to read and reply to warmup mail from the network. See how warmup works for what happens after you connect.

Next steps

With the connection test green, configure daily volume, reply rate, and working hours — details in the settings reference — then start warmup.