According to a September 1, 2022 blog post, Microsoft will allow a one time extension through 12/31/2022 users who have not yet met the requirement to use OAuth for more secure login to MAPI, RPC, Offline Address Book (OAB), Exchange Web Services (EWS), POP, IMAP, Exchange ActiveSync (EAS), and Remote PowerShell.

Furthermore, in a 9-9-2022 blog post Microsoft clarifies that SMTP AUTH will NOT be disabled for active users of the authentication method. The company does urge users to adopt OAuth as a more secure method but clarifies that SMTP AUTH is not shutting down. At least not as of 9/9/2022.

From Microsoft blog post 9-1-2022

One-Time Re-Enablement
Today we are announcing an update to our plan to offer customers who are unaware or are not ready for this change.
When we turn off basic auth after October 1st, all customers will be able to use the self-service diagnostic to re-enable basic auth for any protocols they need, once per protocol. Details on this process are below.
Once this diagnostic is run, basic auth will be re-enabled for those protocol(s). Selected protocol(s) will stay enabled for basic auth use until end of December 2022. During the first week of calendar year 2023, those protocols will be disabled for basic auth use permanently, and there will be no possibility of using basic auth after that.

For more information on the Microsoft OAuth requirements please visit their website here.

The following Sage 100 versions currently meet the requirement use OAuth with Microsoft.

• 2021.4+
• 2022.1+

Sage has begun to contact customers via their online knowledgebase and alert them about an upcoming change. In order for your Sage 100 accounting software to continue contacting the Sage licensing servers you must be on a supported version of Sage 100.

From the Sage KB 116278

In the summer of 2023, Sage will be making changes to your license verification to utilize a current Transport Layer Security (TLS) protocol recommended by third-party standards organizations. This measure is required as older versions of TLS do not meet current security standards and can pose a security risk. If you have a subscription business care plan and are not on a Supported Version of Sage 100, your software will convert to read-only mode.

What does this mean?:

Sage will be updating their internal licensing servers to use TLS 1.2. This is a a widely adopted security protocol designed to facilitate privacy and data security for communications over the Internet.

Previous versions ( prior to Sage 100 2019 ) utilize only older TLS 1.0 or 1.1. Starting in the summer of 2023 you will need to be on a supported version of Sage 100 which offers TLS 1.2 or your ability to maintain a license is jeopardized as Sage states that those who are not on current versions will find their system converted to a read-only mode.

Recommendation:

Our recommendation is upgrade to Sage 100 2021.4+ or 2022.1+ for maximum compatibility.

Resources:

Using Microsoft Exchange with Sage 100 and Paperless Office ( KB 116280)
Sage 100 product licensing and Transport Layer Security ( KB 116278 )

Sage 100 Supported Versions