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?
3 Answers
Direct send via MX records indeed doesn’t require SMTP authentication. However, I'd suggest transitioning to modern services like HVE or Azure Communication Services. These options are generally more reliable for handling email without the risk associated with aging systems. Have you assessed how critical this issue is for your overall operations?
Absolutely, using outside services like Smtp2Go is a solid choice. Alternatively, deploying an on-prem server such as Xeams could work well too. It allows your devices to send emails without authentication, and then it takes care of the OAuth communication with Microsoft, keeping your setup flexible and future-ready.
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.
We're just starting to dig into it, but with a mix of older and newer systems, I want to make sure we're prepared for the transition! Any particular recommendations on transitioning without major disruptions would be helpful!