We've now added support for Single Tenant apps to Microsoft Oauth2 SMTP configurations.
Quick primer for those of you unfamiliar with Microsoft SMTP structures:
When you create an app to handle SMTP, you have the option to select one of two options for the app:
- Single Tenant: Only open to people with accounts within your own Microsoft organization
- Multi-tenant: People within any Microsoft organization
When we first built our integration we assumed people would primarily be using multi-tenant setups. We learned quite quickly this was a faulty assumption--in fact, most of the customers who were interested in the feature wanted single tenant setups instead. So we've added support for single tenant apps, too!
The only difference in setting things up is that if you are using a single tenant application, you will fill in the Tenant ID field in the SMTP configuration.
If you're using multi-tenant, leave that field blank.
See Create a new SMTP service: Microsoft OAuth2 for more detailed instructions.
As a reminder to anyone using Microsoft-based Custom SMTP: Microsoft has been phasing out the basic authentication-styled SMTP we used to suggest. If you're using a Microsoft SMTP for Subscription emails or reader emails, you'll want to work with your Microsoft admin to shift to the new OAuth2 configuration to avoid any possible disruptions.
