Completed feature deprecations
- 最終更新日2026/02/13
Review the features and capabilities (from Automation Anywhere or third party) that are already deprecated and review how they affect your automation.
For a list of features nearing deprecation, see Upcoming feature deprecations.
Third-party deprecations
The following table lists third-party features that are already deprecated:
| Feature or capability | Deprecation date | Customer impact and recommendation | Resources |
|---|---|---|---|
| Manifest V2 based extensions | June 2025 | Manifest V3 extension enhances privacy,
security, and performance. It brings several structural changes
to how extensions are handled by the browser. In Automation 360 v.25, we published the new Google Chrome and Microsoft Edge Manifest
V3 extension. Starting from Automation 360 v.26 and later releases Manifest V2 extension will not be certified. Therefore, we recommend that you migrate the browser extension from Manifest V2 to Manifest V3. |
|
| Microsoft Windows 7 and Windows 8 (or Windows 8.1) operating systems | June 2025 | Microsoft will be deprecating the support
for Windows 7 and Windows 8 (or Windows 8.1) operating systems.
In order to continue receiving feature and security updates for
Windows and Office applications, and avoid performance or
reliability issues, Microsoft recommends that you move to a
supported Windows operating system and have an environmental
consistency. Starting from Automation 360 v.37 release, installing or updating Bot エージェント will not be certified for these operating systems. |
End of support for Windows 10, Windows 8.1, and Windows 7 |
| Microsoft SQL Server 2014 | December 23, 2024 | Microsoft has announced the end of support
for Microsoft SQL Server 2014 version.
Starting from Automation 360 v.35 release, support
for installing or updating Control Room on the
Microsoft SQL Server 2014 will not be
available. Microsoft recommends using a newer and supported version to experience the latest features and have an environmental consistency. |
Azure ACS Deprecation |
|
Google Less Secure Apps (LSAs) deprecation |
September 30, 2024 | Google has announced the deprecation of
Less Secure Apps (LSAs) to connect to Google Workspace using a
username and password as this authentication is not secure and
does not meet the industry's best practices. Google recommends using a more secure OAuth2-based authentication to connect to Gmail. If you are using Automation 360 to automate Gmail using Email and Email Trigger パッケージ with Basic authentication, then you will be impacted by this deprecation. The Automation 360 v.32 and prior versions of the Email パッケージ provides you an option to switch from Basic authentication to OAuth2 - PKCE. However, the same option is not available in the Email Trigger package. To help reduce the risk of deprecation, from Automation 360 v.33, we have enhanced the Email and Email trigger パッケージ with a new Control Room managed OAuth2 mode of authentication that you can use to automate Gmail. This authentication mode is secure and uses the centralized access token management from the Control Room. For details, see アクション E メールのパッケージの接続 Recommended: Use the Bot スキャナー utility to help you scan and identify the impacted Bot that use the E メール and Email trigger パッケージ to automate Gmail. You can then update the impacted Bot by replacing the Basic authentication with Control Room managed OAuth2 authentication mode. |
|
| Oracle database support | September 27, 2024 | From Automation 360v.34, we
have deprecated the support for installing Control Room on the Oracle Database. Microsoft SQL Server is the only database type
that will be available for installing Control Room. Note: If you are using Oracle
database, ensure that you migrate to SQL database. For more
information, see Migrate from Oracle to SQL Database (A-People login required).
|
Deprecation note added to Automation 360v.34 Release Notes: |
| Microsoft Windows Server 2012 and 2012 R2 Standard and Datacenter | March 2024 | Starting from Automation 360
v.32, we have deprecated the use of Microsoft Windows Server 2012 and 2012 R2. Microsoft
ended the support for Microsoft Windows Server 2012
and 2012 R2 in October 2023. We recommend that you update your operating system to one of the supported versions to experience the latest features and have an environmental consistency. See Operating system, environment, and platform supported for Control Room. |
Windows Server 2012 and 2012 R2 end of support |
| Tegaki API OCR engine | October 2023 | From Automation 360v.30, we have deprecated use of Tegaki API OCR engine for data extraction in Automation 360 IQ Bot. We recommend using the Google Vision OCR engine instead. |
Deprecation note added to Automation 360 v.30 Release Notes: Document Automation and IQ Bot v.30 release . |
| Transport Layer Security (TLS) 1.0 and TLS 1.1 | April 2023 |
Automation 360
クラウド deployments currently support the
following TLS protocol versions:
Note: For Automation 360
クラウド deployments, the changes will be
effective as part of the クラウド
deployment configurations, not as part of the Automation 360 release.
|
Deprecating TLS 1.0 and TLS 1.1 |
|
Manifest V2 based extensions by Google See also: Overview and timelines for migrating to Manifest V3 |
January 2023 |
Automations that use Google Chrome Manifest V2 based
extensions will stop working sometime after June 2023. The
deprecation timelines of Manifest V2 based extensions are
currently under review and subject to change by Google.
Recommended: Switch to Manifest V3 based extensions for Google Chrome and Microsoft Edge.
Releases:
|
|
|
EWS API |
March 31, 2022 |
Automation 360 currently uses
EWS API in E メール
パッケージ and Email trigger for the EWS option to
connect to Exchange Online hosted on Azure Cloud and access
emails from Microsoft 365. Microsoft has recommended that customers move to a REST-based Graph API, which is more secure and scalable compared with the legacy SOAP-based EWS API. Therefore Automation 360 will provide support for Microsoft 365 Outlook パッケージ based on Graph APIs which will enable you to switch from EWS API to Graph API from an upcoming release. This deprecation by Microsoft might impact Bot for email automations (E メール パッケージ and Email trigger) that connect to Exchange Online using EWS API. Note that there is no immediate impact on your existing Bot and they continue to run properly. Recommended: Update the impacted Bot by replacing each email-related アクション with the equivalent new アクション in the Microsoft 365 Outlook パッケージ, planned in the upcoming release if your Bot are impacted by the deprecation. |
|
| October 2022 |
Bot for email automations (E メール パッケージ and trigger) that connect to Exchange Online by using IMAP, POP3, or EWS protocols with Basic authentication will be impacted. Recommended: Update the impacted Bot by replacing each email-related アクション with OAuth 2.0.
Released:
|
||
| Internet Explorer EOL | June 2022 |
Customers who are running IE-based Bot on Windows 10 Semi-Annual Channel are impacted. Releases with tools to convert IE-based Bot
to Microsoft Edge with IE mode:
|
Automation Anywhere deprecations
The following table lists Automation Anywhere features that are already deprecated:
| 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. | |
| Discovery Bot | November 2025 |
This deprecation impacts 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
プロセス ディスカバリー
クラウド offering: プロセス ディスカバリー
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). |
| 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: |
| Document Automation support for Google Custom Document Extractor (CDE) | September 2025 | This deprecation will impact customers who are using Google CDE in Document Automation. With this deprecation, users can continue to use their existing learning instances that are using Google CDE. However, users will not be able to create new learning instances with Google Document AI (User-defined) as the provider. We recommend that such customers use 標準フォーム with Azure AI Document Intelligence. See Document Automationを使用して標準フォームにカスタム モデルを作成する. | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| Presentation page in CoE Manager | July 2025 | This deprecation will impact customers who
are using the presentation page inCoE Manager.
Use the platform dashboards option in the left panel menu that
offers the same experience as the presentation page. The
platform dashboards can be used to export data and charts for a
specific time period. Users who have created such data in the presentation page must re-create the same using the platform dashboards option. |
|
| Applications option in CoE Manager | July 2025 | This deprecation will impact customers
utilizing the Applications option in
Admin-Program and
Opportunity pages in CoE Manager. To capture application costs with
greater granularity (yearly or monthly), use the
Additional costs option on the
Opportunity page. These costs are
normalized to a daily benefit or loss and factored into the
benefits realized calculation. Users with existing data in the Applications option must manually recreate it in the Additional costs option on the Opportunity page. |
|
| 標準フォーム support in IQ Bot | With Automation 360 v.37 release
(June 2025) |
This deprecation will impact customers who
are using 標準フォーム in IQ Bot
deployments. We recommend that such customers evaluate the
transition plan for moving from IQ Bot to Document Automation. See IQ Bot から Document Automation: 移行プラン. Note: Contact your Customer Service representative or the account
management team for more details.
These are some
key points for the IQ Bot deprecation:
|
-- |
| AISense Recorder | With Automation 360 v.36
release (April 2025) |
Starting from Automation 360
v.36 and レコーダー
パッケージ 4.0.x, the AISense Recorder will no longer be supported on devices that use special
versions of Microsoft Windows, that is, the Windows N and K
versions. Note: Use a レコーダー
パッケージ version earlier than 4.0.x to use AISense Recorder in Windows N and K
versions.
|
|
Power BI connector using
V1/Authentication
|
With v.34 release (September 2024) |
Power BI connector that uses
v1/authentication will be discontinued and
will stop working from Automation 360 v.34.Note: If you are using Automation 360 v.33 version and have issues
connecting with the BI connector, contact your Automation
Anywhere Customer Success Manager (CSM) for
assistance.
Recommended: Use the Power BI
connector with |
-- |
| Support for .xls format in Excel の高度な操作 パッケージ | June 2023 | Starting from Automation 360 v.29, the .xls format will no longer be supported in the Excel の高度な操作 パッケージ. For all the supported file formats, see Excel の高度な操作 パッケージ. | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| Migrating Enterprise 11 bots to Automation 360 |
April 2025 |
This deprecation will impact customers planning to migrate Enterprise 11 bots to Automation 360. We recommend that customers use a version earlier than v.35 for the migration. |
For more information about migration, see the 移行コンテンツ section |
| Connect Learning Instances from IQ Bot feature in Document Automation | January 2025 | This deprecation will impact customers who are using the Connect Learning Instances from IQ Bot feature in Document Automation. We recommend that such customers use the IQ Bot - Document Automation Bridge パッケージ to use the IQ Bot learning instances in Document Automation. See IQ Bot - DA ブリッジ パッケージ. | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| CyberArk vault integration in IQ Bot オンプレミス | December 2024 |
This deprecation impacts customers using IQ Bot オンプレミス deployments connected to their CyberArk vault and want to update to v.35 release or later. We recommend that customers who need to continue to use CyberArk vault integration to switch to Document Automation オンプレミス deployment. See Control Room オンプレミスのインストール. |
For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| Cloud Migration Utility | October 21, 2024 | This deprecation will impact customers who are using Enterprise 11 and are planning to use the Cloud Migration Utility to migrate to Automation 360 クラウド. The Cloud Migration Utility will be supported for releases we plan to deliver up to October 2024. We recommend that such customers use the utility to migrate to the latest available Automation 360 クラウド GA release before October 21, 2024. | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| Descoped language support | September 2024 |
Beginning with Automation 360 v.34, the User Interface for Automation Anywhere product will no longer support Traditional Chinese. In addition, updated release documentation will no longer be available in this language. |
-- |
| Enterprise 11 Control Room to Automation 360 オンプレミス update tool | With v.34 release (planned for September 2024) | This deprecation will impact customers who are planning to update from Enterprise 11 Control Room to Automation 360 オンプレミス deployment, which currently uses the installer package's update option. This update tool is scheduled for deprecation from Automation 360 v.34 release. We recommend customers to complete the update to Automation 360 before September 30, 2024. | Enterprise 11 から Automation 360 オンプレミス への移行の準備 |
| クラウド-enabled deployment model | April 2024 | This deprecation will impact customers who are on a クラウド-enabled deployment model. We recommend that such customers move to Automation 360 クラウド or オンプレミス before the deprecation. | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| Reactivation Threshold | March 2024 | This deprecation will benefit customers as it removes the threshold or limit on the number of work items to be queued before the automations are executed. For more information, see 標準キューを作成 | For assistance, contact Automation Anywhere support: Open a support case (A-People login required). |
| Automation 360 IQ Bot Community Edition | November 28, 2023 |
Automation 360 IQ Bot Community Edition will no longer be available from November 28, 2023. Use the Document Automation Community Edition for enhanced intelligent document processing. Users who have created automations using Automation 360 IQ Bot will need to rewrite them using Document Automation. |
To learn more, refer to Document Automation . |
|
Descoped language support |
June/July 2023 |
Beginning with Automation 360 v.29, the User Interface for Automation Anywhere product will no longer support Italian, Russian, and Simplified Chinese languages. In addition, updated release documentation will no longer be available in these three languages though older documentation will be accessible. |
-- |
| IQ Bot 抽出 package | This package is deprecated from Automation 360 v.26. Document Automation provides all the capabilities provided by the IQ Bot 抽出 package. To move your bots from the IQ Bot 抽出 package to Document Automation, see Move from IQ Bot Extraction package to Document Automation. | Archived Documentation (PDF): | |
| Set session variable アクション | Year 2022 | This アクション is deprecated and is no longer available for new Bot. Existing Bot using this アクション will not be impacted and will continue to run. You can use a global session to specify a session name for use across multiple Bot. |
To learn more, refer to Bot 間でのセッションの共有 |
| EST, HST and MST time zones | October 2022 | The EST, HST or MST time zones will no longer be supported while scheduling a タスク Bot, API タスク, or a process. | オートメーションをスケジュールする | API タスク をスケジュール設定 |
|
IQ Bot 抽出 パッケージ |
October 2022 |
From Automation 360 v.25, the IQ Bot 抽出 パッケージ no longer supports pre-trained machine learning model for invoice data extraction but will continue to support learning instance group based-training extraction. Recommended: Use the new command パッケージ called ドキュメント抽出, released in v.25 as part of Document Automation. Released: Automation 360 v.25 |
IQ Bot 抽出 パッケージから Document Automation への移動 |
|
IQ Bot - Tesseract OCR v3 |
October 2022 | For all existing learning instances trained
using Tesseract OCR v3, we recommend that you plan to
train them with alternative OCRs (including Tesseract4 OCR) before you update to v.26. Note that
Automation 360 IQ Bot
クラウド customers will receive the v.26
release by default from October 2022. Released: Automation 360 v.26 |
-- |
| G-Suite Apps | September 2022 | From Automation 360 v.26, the
GSuite Apps パッケージ no longer supports using the
Connect and
Disconnect
アクション to establish a connection with the Google
server and automate tasks.
Recommended:For specific
G-Suite applications, the functionality of the G-Suite Apps
パッケージ is available in the following
G-Suite パッケージ:
|
Google パッケージの接続アクション |
| Automation Anywhere Mobile app | July 2022 | The Automation Anywhere Mobile app is deprecated and will not be updated to subsequent versions of iOS and Android. The mobile app is no longer available and no further support will be offered. A replacement product is currently not available. | Archived Documentation (PDF): EN-US |
| Automation Anywhere for Excel | January 2022 |
Automation Anywhere for Excel has been deprecated. The plug-in is no longer available to download as a product. However, support will be offered to current customers already using the product. A replacement product as a plug-in for Microsoft Excel is not available. However, as an alternative, new customers can develop Bot for Excel within the Automation 360 Automation Workspace and use input variables to allow specifying file names, worksheets, and ranges for Bot to operate on. In Automation Anywhere for Excel, this action was triggered from within the Excel application, whereas now, this action is taken from the Automation Anywhere Control Room. |
Documentation: Archived docs for RPA Bots for Excel v2.0 |
| IQ Bot [ローカルデバイス] package | September 2021 | This package is deprecated from Automation 360 v.22 (Build 10526). We recommend using Document Automation with the ドキュメント抽出 package that provides all the capabilities provided by the IQ Bot [ローカルデバイス] package along with some improvements. | Archived Documentation (PDF): IQ Bot [Local Device] package (Archived PDF) |
| Process package | January 2021 | The Process package is no longer supported
with the Create a Request action as this has been replaced by
the AARI web package (now renamed to Process Composer package) in Enterprise A2019.18. Recommended: Use the Create a Request action in Process Composer package. |
New: Process Composer パッケージ
Deprecated: プロセス パッケージ |
| Human-Bot Collaboration 11.3.x | August 2020 |
Human-Bot Collaboration (HBC) 11.3.x was
deprecated from August 2020 with the release of Enterprise
A2019.15.
Recommended: Migrate to Automation 360 to use the ビジネスユーザー向け Automation Co-Pilot (Automation Co-Pilot) that includes Desktop and Web.
Note: For this migration, there is no
automated migration path between HBC 11.3.x and Automation Co-Pilot because of an absence of
parity between the two products (including sets of
features).
|
New: ビジネスユーザー向け Automation Co-Pilot
Deprecated: Enterprise 11: Human-Bot Collaboration |
Automation Anywhere API deprecations and EoLs
The following table lists Automation Anywhere Control Room APIs that are already deprecated and discontinued by the dates mentioned:
- API deprecation indicates that an API is no longer recommended for use but is functional. Developers are encouraged to migrate to newer, supported versions of the API. The API will be available till the End of Life (EoL) date to enable a smooth transition.
- API EoL (End of Life) indicates the date when the API will cease to function, and will no longer be available for use. Developers should have completed their migration to the newer, supported versions of the API before this date.
| Feature or capability | Deprecation date | EoL date | Customer impact and recommendation | Resources |
|---|---|---|---|---|
| v1 Authentication API | November 2023 | With v.33 release (June 2024) | From Automation 360 v.33, the
Authentication APIs: POST
v1/authenticationand POST
v1/authentication/token are discontinued and
will stop working.
Recommended:Use the v2 versions of
the Authentication APIs: POST
|
|
| v1 User Management API | November 2023 | With v.33 release (June 2024) | From Automation 360 v.33, the
User Management APIs: v1/usermanagement are
discontinued and will stop working.
Recommended:Use
the v2 versions of the User Management APIs
|
|
| v3 Migration API | November 2023 | With v.34 release (planned for September 2024) |
From Automation 360 v.31, the v3 Migration APIs
(
Recommended: Use the v4 version of the Migration API
|
|
| v2 Activity List API | June 2022 | With v.27 release (January 2023) | From Automation 360 v.25, the
Activity List API (v2/activity/list) is
deprecated.
Recommended: Use the v3 version of the
Activity List API Note: If you want
to get the
botOutVariables or
callbackInfo, use
/v3/activity/execution/{id}
Bot 実行オーケストレータ API V3
. |
Bot 実行オーケストレータ API V3 |
See also: Automation 360 ソフトウェア ライフサイクル ポリシー .