Email: Support OAuth 2.0 with SMTP (Office 365/Outlook)
in progress
Viiky Ng
Business Problem
Microsoft deprecated Basic Authentication for certain Microsoft 365 tenants starting September 2021. As a result, customers are no longer able to use traditional username/password-based SMTP authentication.
This prevents some users from successfully configuring and connecting their Office 365 accounts via IMAP/SMTP in Respond.io.
Current Limitation
- Respond.io does not support OAuth 2.0 authentication for SMTP with Office 365.
- SMTP authentication currently relies on Basic Authentication (username/password).
- Tenants that have disabled Basic Authentication cannot connect their email accounts.
Desired Outcome
Support OAuth 2.0 authentication for SMTP with Office 365
A
Alyaa See
marked this post as
in progress
N
Nabilah Binti Salleh
Merged in a post:
Support for Microsoft 365 / Outlook as Email Channel
Ron Orlich
Please add native support to connect Microsoft 365 / Outlook mailboxes as an email channel in respond.io.
Right now Outlook / M365 cannot be used because it relied on Basic Authentication, which Microsoft deprecated. However:
Microsoft 365 holds ~45.5% of the SMB market share.
~75% of Fortune 500 companies use Microsoft 365.
Lack of Outlook/M365 support makes it hard for many companies to adopt email in respond.io without extra workarounds or separate providers.
It would be very helpful if respond.io could:
Support modern OAuth-based authentication for Microsoft 365 mailboxes; and
Allow connecting Outlook / M365 accounts directly as an email channel (send + receive).
This would remove friction for existing Microsoft 365 customers and make respond.io more attractive to larger organizations.