Outlook Email Authentication Changes and Impact on Omada Controller

Outlook Email Authentication Changes and Impact on Omada Controller

Outlook Email Authentication Changes and Impact on Omada Controller
Outlook Email Authentication Changes and Impact on Omada Controller
2 weeks ago - last edited 2 weeks ago

This Article Applies to:

 

All Omada SDN Controllers.

 

Background

 

Microsoft has recently updated its authentication policy for Outlook.com, which requires the use of modern authentication methods such as OAuth2. This change is part of a broader industry shift towards more secure email handling practices. As a result, basic authentication, which involves sending usernames and passwords, is being deprecated and will no longer be supported by Outlook.com services.

 

Issue Description/Phenomenon:

 

Due to this policy change, Omada Controller will no longer be able to configure Outlook as a mail server for sending emails, notifications, and logs.

 

Affected email domains include:

@outlook.com

@outlook.office.com

@hotmail.com

@live.com

@msn.com

Country-specific suffixes: such as @outlook.in (India),  @outlook.de (Germany), etc.

 

Temporary Solution:

 

Switch to an Alternative Email Service: We suggest temporarily using another email service like Gmail, which is known to work with Omada Controller.

 

In the meantime, we are working on updating the Omada SDN Controllers to support OAuth2 and other modern authentication methods. 

 

We apologize for any inconvenience this may cause and appreciate your understanding as we work to ensure Omada Controller remains compatible with the latest security standards and email service requirements.

Thank you for your patience and continued support. We are committed to providing you with the best possible experience and will keep you informed as we make progress on this matter.

 

 

We are planning to fix this issue at Omada SDN controller v 5.15.24, and the ETA is April 2025.

 

 

 

Update Log

 

Jan 3rd, 2025:

 

Provide the ETA of the fix time.

 

Dec 31st, 2024:

 

Release of this post.

 

 

Feedback:

 

If this was helpful, welcome to give us Kudos by clicking the thumbs-up button below.

 

If the solution doesn't work for you, your case is probably different from what is described here.

In that case, please feel free to click Start a New Thread and elaborate on the problem so that we can try to help you further.

 

Thank you for your great cooperation and patience!

TP-Link Support Team

Wish you a happy life and smooth network usage! 
  3      
  3      
#1
Options
2 Reply
Re:Outlook Email Authentication Changes and Impact on Omada Controller
2 weeks ago

  @Vincent-TP 

 

 wouldn't creating an app password be the work around rather than changing email providers?

 

https://learn.microsoft.com/en-us/entra/identity/authentication/howto-mfa-app-passwords

  0  
  0  
#2
Options
Re:Outlook Email Authentication Changes and Impact on Omada Controller
2 weeks ago

Hi  @b101 

 

We are discussing about configure outlook.com as the mail server of Omada controller, not SAML SSO.

 

Happy New Year!

Wish you a happy life and smooth network usage! 
  0  
  0  
#3
Options