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
VBScript Around 2027 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.
Microsoft Windows 10 Operating system October 2025 Microsoft will be deprecating support for Windows 10 operating system. Microsoft 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 (including LTSC). 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
Process Composer former (legacy) editor September 2025 This deprecation will impact customers who are using the Process Composer former (legacy) editor to create and design process automations. We recommend that such customers use the new process editor that provides all the previous capabilities along with additional features and an improved user experience. For more information about the discontinuation of the legacy editor and the features of the new editor, review the following resources:
Discovery Bot November 2025

This deprecation will impact customers using Discovery Bot.

For customers interested in continuing with task mining and help to discover opportunities for automation within your organization, we recommend exploring our Automation Anywhere Process Discovery Cloud offering: Process Discovery
Note: Reach out to your Customer Service representative or the Account Management Team to get more details.
These are some key points for the Discovery Bot deprecation:
For assistance, contact Automation Anywhere support: Open a support case (A-People login required).
IQ Bot Cloud March 2026 This deprecation will impact customers who are using IQ Bot Cloud deployments. We recommend that such customers evaluate the transition plan for moving from IQ Bot Cloud to Document Automation. See IQ Bot hasta Document Automation: Plan de transición.
Note: Contact your Customer Service representative or the account management team for more details.
These are some key points for the IQ Bot deprecation:
  • End of maintenance and support for any development, patches, bug fixes, technical support, or security updates.
  • Product documentation will be available on the Automation Anywhere public documentation portal till March 2026: Automation 360 IQ Bot Cloud.
 IQ Bot Cloud End of Life - Frequently Asked Questions
Document Automation support for Google Custom Document Extractor (CDE) September 2025 This deprecation will impact customers who are using Google CDE in Document Automation. We recommend that such customers use Standard Forms with Azure AI Document Intelligence. See Crear modelos personalizados en Document Automation mediante Standard Forms.
These are some key points for the Google CDE deprecation:
  • End of maintenance and support for any development, patches, bug fixes, technical support, or security updates.
  • Product documentation will be available on the Automation Anywhere public documentation portal till September 2025.
 For assistance, contact Automation Anywhere support: Open a support case (A-People login required).

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 Política de obsolescencia de API.

Feature or capability Deprecation date EoL date Customer impact and recommendation Resources
v1 Bot Scheduler APIs With v.34 release With v.39 release 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.40 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 Obsolescencia de funciones completadas.