Running Bot Scanner to scan bots for EOL features

Automatically identify Automation 360 bots that are using Basic authentication mode in the Connect, Send, Forward, and Reply actions in the Email package and Email trigger, which are using IMAP, POP3, or EWS protocols.

Prerequisites

Ensure that the user credentials used to connect to the Control Room has the View content permission on the Bots folder.
The Bot Scanner utility connects to your Control Room using these credentials.
Ensure that you meet the software and hardware requirements for using the Bot Scanner.
See Scan Enterprise 11 or 10 bots using Bot Scanner.

Procedure

Download the Bot Scanner utility using the link provided in the following article: Everything about Basic Authentication deprecation in Microsoft Exchange online (A-People login required).
Extract the files from the zip file that you have downloaded and double-click the Automation_360_Bot_Scanner_For_EOL_Features.exe executable file to run the utility.
In the Bot Scanner page, click the drop-down and select one of the following:
- Bots using Email action with EWS option: To select the bots that have used the EWS protocols.
- Bots using Email action with Basic authentication: To select the bots that have used the Authentication type as Basic for both IMAP and POP3 protocols.
- Bots using Internet Explorer: To get the bots that have used Internet Explorer.
Note: Microsoft has deprecated EWS API for Exchange Online and has recommended that users move to Graph API. See Upcoming API Deprecations in Exchange Web Services for Exchange Online.
We recommend that you replace each email-related action with the equivalent new action in the Microsoft 365 Outlook package (based on Graph API) if your bots are impacted by the deprecation.
Click Continue.

In the Automation 360 Bot Scanner EOL features page, perform these steps:

Enter the Control Room URL that you want to connect to

Based on the authentication type configured in your Control Room, choose one of the following authentication methods in the Authentication Type field:


Authentication type	Steps
Active Directory	Enter the Username (Domain\\username). Enter the Password (domain user password).
Database	Enter the Username (Control Room database username). Enter the Password (Control Room database user password).
Single Sign-On	Enter the Username. Enter the API Key.

Click Test connection.
A connection success or failure message is displayed. Validate your credentials if the connection fails.
In the Select destination path field, enter the location where you want to save the generated report.
Click Scan bots.

Connect to your Control Room and select destination path to download the report

The scanner scans all the bots in your Control Room repository for Basic authentication mode usage in the Connect, Send, Forward, and Reply actions in the Email package and Email trigger. After the scan is complete, a report (.CSV file) is available in the destination path you selected for your review.

If a .CSV file already exists in the output folder, a message is displayed that the previous .CSV file will be deleted. When you click Continue, a new .CSV file is generated.
If the previous .CSV file is in use, a message is displayed that the file cannot be deleted. Close the file and click Scan bots.

Click Open report to analyze the report.
The report contains the following details:
- Task Bot name: Name of the Task Bot.
- Line number: The line number of the Connect, Send, Forward, or Reply actions that are using Basic authentication.
  For Email trigger, the line number will be empty.
- Package and action name: The Email package and action that is using Basic authentication.
- Searched text: The hostname of the Email server or the domain name of the EWS server for the respective action.
- Action and review message: Use this information to understand the action that you have to perform or the information that you have to review for the corresponding action containing Basic authentication.
  See Basic authentication scanning messages.
- Task Bot path: The path to the repository where the bot resides.

Next steps

After you identify the bots that are impacted due to Basic authentication, you can plan to update these bots in the Control Room repository to switch to OAuth 2.0 authentication. For more information on how to switch to OAuth 2.0, see Deprecation of Basic authentication in Exchange Online.