As a managed service provider, we're evaluating our strategy now that Microsoft plans to end support for Basic SMTP authentication in late 2026. This change will affect devices and applications that aren't compatible with OAuth 2.0 or the Microsoft Graph API, which includes many printers and older systems. Currently, our printers are set up for Direct Send using an MX record and Exchange connectors. Our applications have transitioned to the Microsoft Graph API, and where possible, we've implemented OAuth 2.0 on our websites. We're trying to figure out the most future-proof solution moving forward. Would switching to an external SMTP service like Smtp2Go be a smart move?
1 Answer
One reliable solution for older devices and printers is to set up your own internal relay. This way, your devices can send emails to this relay without needing OAuth, and the relay can manage the authentication processes with services like Smtp2Go or even handle migrations to OAuth later on. It's a bit of a hassle, but worth it for keeping things running smoothly even if Microsoft changes things up again.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures