Connecting legacy desktop apps to Copilot Studio with RPA and CUA
Diesen Beitrag auf Deutsch lesen
Compare deterministic Power Automate RPA with Computer Use Agents, including Dataverse retrieval, machine setup, environment requirements and preview risks.
TL;DR
Copilot Studio can access legacy desktop data through a scheduled cloud flow, a Power Automate desktop flow and a custom Dataverse table. Computer Use Agents offer direct, vision-based interaction, but require a US-based environment, a configured machine and a dedicated account. Enabling Computer Use removes that machine from standard desktop flow connections.
Original by James Papadimitriou, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Choose deterministic RPA for stable, high-volume or mission-critical interfaces, and use Computer Use when screens change or decisions require visual reasoning.
- Admins/CoE: Verify the environment is US-based, register the machine, enable Computer Use in Power Automate settings and check existing connections first.
- Security/Compliance: Use a dedicated Computer Use account and treat the preview status, lack of SLA and machine connection breakage as deployment risks.
Frequently asked questions
What happens when a Power Automate machine is enabled for Computer Use?
Enabling Computer Use removes the machine from standard desktop flow connections and breaks existing connections tied to that machine.
Which Power Platform environment is required for Copilot Studio Computer Use?
Computer Use currently requires a US-based Power Platform environment. The target machine also needs Power Automate Machine Runtime installed and registered.
Is Copilot Studio Computer Use suitable for mission-critical production workloads?
No. Computer Use is in preview, has no SLA guarantees and is not recommended for mission-critical production workloads.