TMWSuite/TMW.Suite SMTP remediation
Microsoft is phasing out Basic Authentication for Client Submission (SMTP AUTH) in Exchange Online, which is the method your current TMW Operations version uses to send emails.
According to this official announcement, Microsoft will start rejecting email submissions using Basic Auth on March 1, 2026, with complete retirement (100% rejection) by April 30, 2026.
After April 30, 2026, any attempt by your current version of TMW Operations to send emails via Microsoft 365 will fail unless one of the options described below is implemented.
Only customers using Microsoft 365 to send email from one or more TMWSuite or TMW.Suite products need to upgrade or choose another option described below. Customers using an on-premise mail server or an existing third-party solution should contact their mail provider regarding any changes to Basic Auth support.
Options to maintain email functionality
You must choose one of the following options before March 1, 2026.
Upgrade to TMW Operations 2026.1 or later (strongly recommended)
Trimble strongly recommends upgrading to the general availability release of TMW Operations 2026.1 or later.
Version 2026.1, scheduled for release in January 2026, includes support for SMTP OAuth 2.0, which is Microsoft’s required new standard. This is the most secure and sustainable solution for Microsoft 365.
| Applying service packs or version patches to existing installations is not recommended. |
Use an SMTP relay
If you cannot upgrade your TMW Operations instance before March 1, you can set up an SMTP relay/connection with Microsoft 365. Note that this method requires a static, non-spam-blocklisted IP address and demands constant attention to maintain your IP’s reputation.
For more information, see How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 on the Microsoft documentation website.
Switch to a third-party SMTP provider
If you cannot upgrade your TMW Operations instance before March 1, you can change your configuration settings to use a secure third-party SMTP provider. Several large customers successfully use external providers, such as SMTP2GO, that offer robust and reliable transactional email services.