Review the features and capabilities (from Automation Anywhere or third party) that are nearing deprecation to understand how they affect your automation and what action is required.

Definition: Deprecation refers to features or capabilities available in the current (latest) release that are planned to be removed or unsupported in a future release.

You can use the specified alternatives or updated versions when they are made available.

Third-party deprecations

The following table lists the upcoming third-party features that will be deprecated by the date mentioned:

Feature or capability Deprecation date Customer impact and recommendation Resources
UIAutomationPRoviderEnabled transition policy 2026 (Tentative) Google Chrome has announced plans to remove the UIAutomationPRoviderEnabled transition policy after version 146. To avoid potential Recorder web automation issues in Chrome v147 and later, we recommend updating your Recorder package to version 2.17.6 or later.
VBScript 2027 (Tentative) Microsoft is actively phasing out VBScript. Around 2027, VBScript will no longer be enabled by default. Eventually, it will be completely removed from future Windows versions. This is primarily driven by security concerns, as VBScript has been a common vector for malicious attacks.

With this deprecation, any Automation 360 automations utilizing the VBScript package will cease to function when VBScript is no longer supported or present on the OS. This means a hard stop for those bots leading to disruptions in automated processes.

To ensure continuity and avoid runtime failures, we recommend identifying the bots that uses VBScript package, re-implement the logic using JavaScript package, and validate the output before deprecating VBScript steps within the automation.JavaScript is a widely used, modern, and versatile scripting language, ensuring future compatibility and access to a vast ecosystem of libraries and community support.

For more intricate or specialized scripting needs, Automation 360 also supports the Python Script package. Python is a powerful and popular language often used for data science, machine learning, and complex integrations, offering even greater flexibility.
Amazon Linux 2 (AL2) operating system June 2026 Amazon will be ending the support for the AL2 operating system in June 2026. It is recommended that you update to Amazon Linux 2023 (AL2023) as this operating system optimizes boot time to reduce the time from instance launch to running your workload. These optimizations span the Amazon EC2 instance kernel configuration, cloud-init configurations, and features that are built into packages in the operating system such askmod and systemd.
Microsoft Windows 10 Operating system November 2025 Microsoft will be deprecating support for Windows 10 operating system and recommends that you move to Windows 11 operating system for the following reasons:
  • Continue to receive feature and security updates for Microsoft Windows and Office applications.
  • Avoid performance or reliability issues.
  • For environmental consistency

However, Microsoft has announced extended support for Windows 10 LTSC (Long-Term Servicing Channel) editions, Therefore, starting from Automation 360 v.39 release, installing or updating Bot Agent will not be certified for Windows 10 operating system (excluding LTSC versions). We recommend that you update your Bot Runner devices to Windows 11 before deploying your automations.
Microsoft Azure ACS deprecation April 2, 2026 Microsoft is retiring Azure ACS and recommends migrating to their modern authentication platform, Microsoft Entra (formerly Azure AD).

Recommended: The Automation 360 SharePoint package is fully compatible with Entra. Simply set up your OAuth clients and use them within the SharePoint package to ensure a smooth transition and avoid any disruption to your SharePoint automations.

 Azure ACS Deprecation

Automation Anywhere deprecations

The following table lists Automation Anywhere features that will be deprecated by the date mentioned:

Feature or capability Deprecation date Customer impact and recommendation Resources
Cost per execution/transaction failure field in Opportunity page in CoE Manager January 2026 This deprecation changes how failure costs are calculated on the Opportunities page. To improve accuracy and better assess automation performance, the failure cost per execution or transaction will be calculated individually for each automation within an opportunity.
Bot Insight (Cloud) January 2027 Automation Anywhere will discontinue Bot Insight, with end-of-life (EOL) effective December 2026 for On-Premises deployments and January 2027 for Cloud deployments.
After the EOL dates, Bot Insight will no longer be supported or available. After Bot Insight reaches EOL:
  • Technical support will no longer be available.
  • Customers will no longer be able to log support cases through A-People.
  • No enhancements, bug fixes, patches, or security updates will be provided.
  • Product access, training materials, and documentation will be removed.
Automation Anywhere strongly recommends completing your transition before these EOL dates.

Customers using Bot Insight must transition to the Automation Command Center (ACC) for reporting and operational visibility. ACC reporting capabilities are included with the core platform and provide a modern, scalable alternative.

Recommended migration path
  • ACC Reporting: Centralized reporting and insights for automations. For more details, see Automation Command Center.
  • CoE Manager: Customizable dashboards are planned for release in Q2 2026, with additional business insights are available through CoE Manager. For more details, see CoE Manager.
 <<link to BI FAQ page>>
Bot Insight (On-Premises) June 2027

Automation Anywhere API deprecations and EoLs

The following table lists Automation Anywhere Control Room APIs that will be deprecated and discontinued by the dates mentioned. For more information on the API deprecation policy, see API deprecation policy.

Feature or capability Deprecation date EoL date Customer impact and recommendation Resources
v1 Bot Scheduler APIs With v.34 release In January 2028 The v1 Bot Scheduler APIs (/v1/schedule/automations) will be deprecated.

Recommended: Use the v2 Bot Scheduler APIs /v2/schedule/automations that will be available with the v.34 release.

 Automations API
v3 Work Load Management (WLM) APIs With v.34 release With v.41 release The following v3 Work Load Management (WLM) APIs are getting deprecated:
  1. POST/v3/wlm/workitemmodel
  2. GET /v3/wlm/workitemmodels/{id}
  3. GET /v3/wlm/queues/{id}
  4. POST /v3/wlm/queues/{id}/consumers
  5. POST /v3/wlm/queues/{id}/participants
  6. PUT /v3/wlm/queues/{id}/members/{userId}
  7. POST /v3/wlm/queues/{id}/file
  8. PUT /v3/wlm/queues/{id}/workitems/{workItemId}
Recommended: Use the v4 WLM APIs that will be available with the v.34 release:
  1. POST/v4/wlm/workitemmodel
  2. GET /v4/wlm/workitemmodels/{id}
  3. GET /v4/wlm/queues/{id}
  4. POST /v4/wlm/queues/{id}/consumers
  5. POST /v4/wlm/queues/{id}/participants
  6. PUT /v4/wlm/queues/{id}/members/{userId}
  7. POST /v4/wlm/queues/{id}/file
  8. PUT /v4/wlm/queues/{id}/workitems/{workItemId}
 Workload Management API

Completed deprecations: For a list of features already deprecated, see Completed feature deprecations.