Important update regarding Nintex Kryon RPA's integration with Exchange Online

NintexJason
Nintex Employee
Nintex Employee
0 0 124

Microsoft has previously announced a change to the ‘basic authentication’ option that some of our Nintex Kryon RPA customers may have utilized to connect to Exchange Online within automations initiated by Email Triggers and/or send emails via Email Advanced Commands.  Specific information on this change is available via the Exchange Online blog here https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic...

 

Starting with the 21.4 release of Nintex Kryon RPA, we introduced capabilities to utilize the new ‘modern authentication’ options favored by Exchange Online to ensure customer solutions would work long after basic authentication was disabled by Microsoft starting October 1, 2022.  In most scenarios, if you upgraded to Nintex Kryon RPA release 21.4 (or later) to utilize modern authentication with Exchange Online you likely will not be impacted by this change.

 

How will this change affect me?

If you are a Nintex Kryon RPA customer who utilizes Email Triggers or Email Advanced Commands in your automations and you also use Exchange Online as your email server, you will be impacted by the disabling of basic authentication within your Exchange Online tenant if you have not yet upgraded to Nintex Kryon RPA 21.4 (at a minimum) and configured your Email Triggers or Email Advanced Commands as described here: https://help.nintex.com/en-US/kryonrpa/21.04/default.htm#AdvancedCommands/Appendices/Working_with_Mi...

 

Additionally, if you are a customer looking to change to modern authentication and your organization requires the use of Multi-factor Authentication (MFA), we are aware of challenges in support of these scenarios and are working on fix packs to address this in the coming months.

 

How can you mitigate this change?

If you are a customer who utilizes Exchange Online with your deployment of Nintex Kryon RPA and makes use of Email Triggers or Email Advanced Commands and are in any of the below scenarios, you can take the following steps:

  • Using a version of Nintex Kryon RPA prior to 21.4
  • Using a version of Nintex Kryon RPA 21.4 (or later) but have not configured your Email Triggers or Advanced Commands to utilize Exchange Online modern authentication
  • Using a version of Nintex Kryon RPA 21.4 (or later) and your organization requires the use of Multi-factor Authentication (MFA) for applications connecting to Exchange Online

 

1) Request an extension – Microsoft customers who utilize Exchange Online and still require basic authentication have the opportunity to run a ‘self-service diagnostic’ that will defer Microsoft from disabling basic authentication in their tenant through January 1, 2023

 

While this extension is not permanent, it should mitigate any issues you may incur between October 1, 2022 and the end of the calendar year.

 

Find out more information about basic authentication extension options for Exchange Online in the Microsoft Tech Community article here: https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-deprecation-in-exchan...

 

2.) Upgrade Nintex Kryon RPA to the latest supported version – by upgrading and re-configuring your Email Triggers and/or Email Advanced Commands to utilize modern authentication you should not be impacted by the basic authentication change within Exchange Online. You can find a list of support for recent versions of Nintex Kryon via Nintex Help, here: https://help.nintex.com/en-US/platform/KryonSupport/KryonRPASupport.htm 

 

As previously noted, for a subset of customers looking to utilize Multi-factor Authentication (MFA) with Exchange Online, we are working on fix packs for this scenario and we will provide more guidance as these fix packs become available.

 

If you are unsure if you are affected by this change or you still have questions don’t worry, we’re here to help. Please contact your account manager with any questions or concerns about the coming change.

 

Thank you, 
Your Nintex Product Team