Sage 100

I think the answer is Sage's supported versions all support OAUTH which is what Microsoft supports going forward. If the customer wants to remain on an unsupported version of Sage 100 or otherwise is unable to use OAUTH they have options including SMTP2GO which offer access to SMTP servers ( for an added fee ).

I'm not a Microsoft technology expert. I thought some of these announcements dealt with tightening up when a company  could override the OAUTH requirement and allow for SMTP AUTH. My understanding - perhaps incorrect - is that the upcoming deadline removed the ability to continue using SMTP as an override.

Sage has a pretty good summary of how to enable OAUTH on both Gmail and Microsoft Office 365 / O365
Will Sage 100 lose ability to send emails thru Paperless Office once Microsoft disables Basic Authentication

It appears that Microsoft has extended their Basic Authentication Deprecation timeline to December 2026.

Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline

The_Exchange_Team

Platinum Contributor

Jan 27, 2026

We understand that many customers continue to face real challenges modernizing legacy email workflows and need sufficient time to adopt viable, secure alternatives. Based on customer feedback and visibility into adoption progress, we are refining the Exchange Online SMTP AUTH Basic Authentication Deprecation timeline to provide clearer milestones and additional runway.

• Now to December 2026: SMTP AUTH Basic Authentication behavior remains unchanged.
• End of December 2026: SMTP AUTH Basic Authentication will be disabled by default for existing tenants. Administrators will still be able to enable it if needed.
• New tenants created after December 2026: SMTP AUTH Basic Authentication will be unavailable by default. OAuth will be the supported authentication method.
• Second half of 2027: Microsoft will announce the final removal date for SMTP AUTH Basic Authentication.

These updates are intended to give customers with tenants in our service (all cloud environments) more time to plan, validate, and deploy modern authentication alternatives, while maintaining a clear path toward stronger default security.

Microsoft 365 Messaging Team

I think the answer is Sage's supported versions all support OAUTH which is what Microsoft supports going forward. If the customer wants to remain on an unsupported version of Sage 100 or otherwise is unable to use OAUTH they have options including SMTP2GO which offer access to SMTP servers ( for an added fee ).

I'm not a Microsoft technology expert. I thought some of these announcements dealt with tightening up when a company  could override the OAUTH requirement and allow for SMTP AUTH. My understanding - perhaps incorrect - is that the upcoming deadline removed the ability to continue using SMTP as an override.

Sage has a pretty good summary of how to enable OAUTH on both Gmail and Microsoft Office 365 / O365
Will Sage 100 lose ability to send emails thru Paperless Office once Microsoft disables Basic Authentication

As an alternative to using Office/O385/Exchange for sending out paperless emails, you can also use a standalone email sender. This is how people do marketing emails for example, we have "Google Workspace" for our email, and use a separate marketng emailer, they both use the same domain and are setup to do so.

So - I would recommend a transactional emailer - we use something called Mailgun internally, but  basically they give you a set of SMTP creds and post the emails to their server and this whole thing becomes irrelevant. Using exchange directly for transactional emails is not really great anyway.

It appears that Microsoft has extended their Basic Authentication Deprecation timeline to December 2026.

Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline

The_Exchange_Team

Platinum Contributor

Jan 27, 2026

We understand that many customers continue to face real challenges modernizing legacy email workflows and need sufficient time to adopt viable, secure alternatives. Based on customer feedback and visibility into adoption progress, we are refining the Exchange Online SMTP AUTH Basic Authentication Deprecation timeline to provide clearer milestones and additional runway.

• Now to December 2026: SMTP AUTH Basic Authentication behavior remains unchanged.
• End of December 2026: SMTP AUTH Basic Authentication will be disabled by default for existing tenants. Administrators will still be able to enable it if needed.
• New tenants created after December 2026: SMTP AUTH Basic Authentication will be unavailable by default. OAuth will be the supported authentication method.
• Second half of 2027: Microsoft will announce the final removal date for SMTP AUTH Basic Authentication.

These updates are intended to give customers with tenants in our service (all cloud environments) more time to plan, validate, and deploy modern authentication alternatives, while maintaining a clear path toward stronger default security.

Microsoft 365 Messaging Team

I think the answer is Sage's supported versions all support OAUTH which is what Microsoft supports going forward. If the customer wants to remain on an unsupported version of Sage 100 or otherwise is unable to use OAUTH they have options including SMTP2GO which offer access to SMTP servers ( for an added fee ).

I'm not a Microsoft technology expert. I thought some of these announcements dealt with tightening up when a company  could override the OAUTH requirement and allow for SMTP AUTH. My understanding - perhaps incorrect - is that the upcoming deadline removed the ability to continue using SMTP as an override.

Sage has a pretty good summary of how to enable OAUTH on both Gmail and Microsoft Office 365 / O365
Will Sage 100 lose ability to send emails thru Paperless Office once Microsoft disables Basic Authentication

Oh, hadn't heard of Mailgun.  Lots of us use smtp2go.

As an alternative to using Office/O385/Exchange for sending out paperless emails, you can also use a standalone email sender. This is how people do marketing emails for example, we have "Google Workspace" for our email, and use a separate marketng emailer, they both use the same domain and are setup to do so.

So - I would recommend a transactional emailer - we use something called Mailgun internally, but  basically they give you a set of SMTP creds and post the emails to their server and this whole thing becomes irrelevant. Using exchange directly for transactional emails is not really great anyway.

It appears that Microsoft has extended their Basic Authentication Deprecation timeline to December 2026.

Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline

The_Exchange_Team

Platinum Contributor

Jan 27, 2026

We understand that many customers continue to face real challenges modernizing legacy email workflows and need sufficient time to adopt viable, secure alternatives. Based on customer feedback and visibility into adoption progress, we are refining the Exchange Online SMTP AUTH Basic Authentication Deprecation timeline to provide clearer milestones and additional runway.

• Now to December 2026: SMTP AUTH Basic Authentication behavior remains unchanged.
• End of December 2026: SMTP AUTH Basic Authentication will be disabled by default for existing tenants. Administrators will still be able to enable it if needed.
• New tenants created after December 2026: SMTP AUTH Basic Authentication will be unavailable by default. OAuth will be the supported authentication method.
• Second half of 2027: Microsoft will announce the final removal date for SMTP AUTH Basic Authentication.

These updates are intended to give customers with tenants in our service (all cloud environments) more time to plan, validate, and deploy modern authentication alternatives, while maintaining a clear path toward stronger default security.

Microsoft 365 Messaging Team

Oh, hadn't heard of Mailgun.  Lots of us use smtp2go.

As an alternative to using Office/O385/Exchange for sending out paperless emails, you can also use a standalone email sender. This is how people do marketing emails for example, we have "Google Workspace" for our email, and use a separate marketng emailer, they both use the same domain and are setup to do so.

So - I would recommend a transactional emailer - we use something called Mailgun internally, but  basically they give you a set of SMTP creds and post the emails to their server and this whole thing becomes irrelevant. Using exchange directly for transactional emails is not really great anyway.

It appears that Microsoft has extended their Basic Authentication Deprecation timeline to December 2026.

Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline

The_Exchange_Team

Platinum Contributor

Jan 27, 2026

We understand that many customers continue to face real challenges modernizing legacy email workflows and need sufficient time to adopt viable, secure alternatives. Based on customer feedback and visibility into adoption progress, we are refining the Exchange Online SMTP AUTH Basic Authentication Deprecation timeline to provide clearer milestones and additional runway.

• Now to December 2026: SMTP AUTH Basic Authentication behavior remains unchanged.
• End of December 2026: SMTP AUTH Basic Authentication will be disabled by default for existing tenants. Administrators will still be able to enable it if needed.
• New tenants created after December 2026: SMTP AUTH Basic Authentication will be unavailable by default. OAuth will be the supported authentication method.
• Second half of 2027: Microsoft will announce the final removal date for SMTP AUTH Basic Authentication.

These updates are intended to give customers with tenants in our service (all cloud environments) more time to plan, validate, and deploy modern authentication alternatives, while maintaining a clear path toward stronger default security.

Microsoft 365 Messaging Team

I think the answer is Sage's supported versions all support OAUTH which is what Microsoft supports going forward. If the customer wants to remain on an unsupported version of Sage 100 or otherwise is unable to use OAUTH they have options including SMTP2GO which offer access to SMTP servers ( for an added fee ).

I'm not a Microsoft technology expert. I thought some of these announcements dealt with tightening up when a company  could override the OAUTH requirement and allow for SMTP AUTH. My understanding - perhaps incorrect - is that the upcoming deadline removed the ability to continue using SMTP as an override.

Sage has a pretty good summary of how to enable OAUTH on both Gmail and Microsoft Office 365 / O365
Will Sage 100 lose ability to send emails thru Paperless Office once Microsoft disables Basic Authentication