Deprecation of EWS APIs in Exchange Online

Microsoft has announced End-of-life of EWS APIs that is used to connect to Exchange Online. This is an ongoing deprecation and Microsoft will continue deprecating the least used EWS API. This impacts customers running bot for email automation that connect to Exchange Online using EWS API.

To know more about EWS API deprecation, see Upcoming API Deprecations in Exchange Web Services for Exchange Online.

We have released a new Microsoft 365 Outlook package with Automation 360 v.29 release which is based on the latest version of Graph API and will enhance Microsoft 365 package suite capabilities, see Microsoft 365 Outlook package.

To ensure that your existing bots that are using the existing Email package with the EWS option are supported after the EWS APIs are deprecated, we recommend that you replace the actions from the Email package with the actions from the new Microsoft 365 Outlook package to automate Outlook emails for Exchange Online. This package contains all actions similar to those available in the Email package. You can use the Microsoft 365 Outlook package instead of the Email package with EWS option to change from EWS API to Graph API, see EWS API deprecation FAQ.

Update bots using Email EWS option to Microsoft 365 Outlook package

EWS API workflow

You must update your bots that are using EWS API in the actions of the Email package and Email trigger before EWS API is deprecated.
Note: Ensure that you update your Bot Agent version to 21.250 (which was released with Automation 360 v.29) on your system.
To update the bots, perform the following steps:
  1. Run Bot Scanner to scan bots having Email action with EWS option. See Scan bots for Basic authentication.
  2. Edit the impacted bot by replacing each Email action with EWS option with the equivalent actions in the Microsoft 365 Outlook package. See Microsoft 365 Outlook package.
  3. Test the bot and ensure the result is same.