How can the Robot credentials be defined in Orchestrator when using Azure AD to login to the VM?
Issue Description: When configuring the Robot credentials in Orchestrator following the usual method, the "Robot does not exist" error will persist in UiPath Assistant or Studio.
The output of the "whoami" command will still return the username under the domain\username format, but this exact output or the email will not be enough in the robot setup configuration.
Sample "whoami" output: domain\username
Sample email address of the same user: email@example.com - defined in Azure Active Directory (AAD)
Root Cause: AAD account for the Robot user, domain/ username format was throwing "invalid credentials" error.
- The Robot credentials must be defined using the format: "azuread\email address" like in the below screenshot,