Skip to content

Commit 3be447e

Browse files
authored
Clarify terminology in CyberArk connection article
Updated terminology from 'machine' to 'device' for clarity.
1 parent c9cfaa5 commit 3be447e

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

support/power-platform/power-automate/desktop-flows/ui-automation/ui-rdp-automation/cyberark-connection-not-supported.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,17 +7,17 @@ ms.date: 11/20/2025
77
---
88
# CyberArk connections aren't supported for RDP automation
99

10-
This article helps you resolve an issue in which you can't connect to a machine through CyberArk when you use Remote Desktop Protocol (RDP) automation in Microsoft Power Automate for desktop.
10+
This article helps you resolve an issue in which you can't connect to a device (computer or virtual machine) through CyberArk when you use Remote Desktop Protocol (RDP) automation in Microsoft Power Automate for desktop.
1111

1212
## Symptoms
1313

14-
When you try to connect to a machine through CyberArk by using RDP automation, the Power Automate agent for virtual desktops doesn't establish communication with Power Automate for desktop, and you receive the following error message:
14+
When you try to connect to a device through CyberArk by using RDP automation, the Power Automate agent for virtual desktops doesn't establish communication with Power Automate for desktop, and you receive the following error message:
1515

1616
> A device attached to the system is not functioning.
1717
1818
:::image type="content" source="media/cyberark-connection-not-supported/rdp-connection-failed.png" alt-text="The error message that you receive when you try to connect through CyberArk.":::
1919

20-
However, when you connect directly to the machine by using RDP without CyberArk, the connection works as expected, and Power Automate for desktop successfully communicates with the agent.
20+
However, when you connect directly to the device by using RDP without CyberArk, the connection works as expected, and Power Automate for desktop successfully communicates with the agent.
2121

2222
## Cause
2323

@@ -27,7 +27,7 @@ CyberArk creates a nested remote connection path. This condition interferes with
2727

2828
To resolve this issue:
2929

30-
- Use a direct RDP connection to the target machine instead of connecting through CyberArk.
31-
- Make sure that the Power Automate agent for virtual desktops is running and correctly registered on the machine.
30+
- Use a direct RDP connection to the target device instead of connecting through CyberArk.
31+
- Make sure that the Power Automate agent for virtual desktops is running and correctly registered on the device.
3232

3333
[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]

0 commit comments

Comments
 (0)