Microsoft shipped Computer-Using Agents (CUAs) to general availability in Copilot Studio on May 13, 2026 — the Tech Community blog post by Mustapha Lazrek made it official, and the Power Platform 2026 release wave 1 plan lists “Automate web and desktop apps with computer use” as GA from the May 7 wave. Together that closes the loop for citizen developers who’ve been running their automations on the technical-preview side since last May.
If you live in Power Automate Desktop or UiPath Community Edition today, this is the question worth answering this week: should you migrate? Here’s a 20-minute walkthrough that ports a real automation across, plus the three RPA patterns CUA still can’t replace.
What just changed
Until last Wednesday, Computer-Using Agents in Copilot Studio were a technical preview — useful for proofs of concept, not for the citizen-developer use case that pays the bills. The GA flip changed three things:
- All commercial Power Platform geographies are covered (per the Tech Community blog). Sovereign clouds and air-gapped environments are still out of scope, but the typical SMB or enterprise Power Platform tenant is in.
- Enterprise-ready governance is wired in: Azure Key Vault for credential storage, Microsoft Purview surfacing audit logs and action history, allow-lists for websites and applications, DLP policies inherited from your Power Platform tenant, human-in-the-loop checkpoints for sensitive steps.
- Model choice matters. Microsoft documents support for both OpenAI and Anthropic models for computer use; community-sourced reporting names OpenAI’s Computer-Using Agent and Claude Sonnet 4.5 as the GA-tier production options, with newer Anthropic models (Sonnet 4.6, Opus 4.6) flagged as experimental. The official Microsoft pages don’t enumerate the exact model SKUs in one place — confirm in your tenant’s model picker before assuming a specific lineup.
There’s also an April 2025 bidirectional UiPath integration that didn’t go away — the official Microsoft Copilot blog post “Announcing Agentic Automation with Bidirectional Integration between Microsoft Copilot Studio and UiPath” still describes the supported pattern. You can embed UiPath agents inside Copilot Studio agents and vice versa, which means migration isn’t necessarily “rip and replace” — it can be hybrid for as long as you need.
The 20-minute migration walkthrough
The scenario: a real automation a citizen developer at a mid-market company already runs in Power Automate Desktop or UiPath Community Edition. We’ll port a vendor-portal task: log in to a supplier portal, look up an invoice by number, download the PDF, and attach it to a SharePoint document library.
This is the canonical CUA test case because every part of it (browser navigation, form fill, file download, SharePoint upload) is in scope for the GA release. If your bot does these things, it ports cleanly. If it does something else, work through the same five steps with your task and see where it breaks.
Step 1: Create the agent shell (3 min)
In Copilot Studio (the same place you’ve been building chatbots for the last two years), create a new agent. Description: “Vendor invoice retrieval bot.” Skip the conversational starters — this agent doesn’t talk; it acts.
Make sure generative orchestration is enabled in the agent’s settings. CUA depends on it. If your tenant admin has it locked off, you’ll need to escalate before going further.
Step 2: Add the Computer Use tool (3 min)
In the agent editor, the documented flow per Microsoft’s Tech Community blog is:
- Open the agent → Tools → Add tool → Add new computer use
- Pick the model from the dropdown. If both OpenAI’s CUA and Claude Sonnet 4.5 appear, default to Claude Sonnet 4.5 for tasks involving nuanced UI reasoning (complex forms, ambiguous error states); use OpenAI’s CUA when the task is more deterministic (filling a known form in a known order). Anthropic models may require your admin to enable external model access first.
- Name the tool descriptively:
vendor_portal_invoice_lookup. The name shows up in audit logs, so make it human-readable.
Step 3: Describe the task in plain English (5 min)
This is the “write the brief” step. CUA reads natural-language descriptions and decomposes them into clickable steps; the better your description, the fewer failure modes you have to debug.
Sample brief:
“Open the vendor portal at https://portal.examplevendor.com. Sign in using the credentials stored in Azure Key Vault under
vendor_portal_creds. Navigate to the Invoices tab. Enter the invoice number provided as input into the search field. Click Search. When the invoice appears, click the Download PDF button. Save the downloaded file with the original filename. Upload the file to the SharePoint document library athttps://contoso.sharepoint.com/sites/finance/Vendor_Invoices/. Confirm the upload succeeded by checking that the file appears in the library.”
Three things make this brief work: it names the URL explicitly, it points at Key Vault by reference (not embedded creds), and it includes a success check (“confirm the file appears in the library”). CUA without the success check will declare victory on a half-completed task.
Step 4: Configure the execution environment (5 min)
CUA runs on a machine. Microsoft documents two patterns:
- Bring-your-own-machine: a Power Automate machine in your tenant that has the browser and any thick-client apps installed. Works for desktops and bring-up servers; fragile if the machine reboots mid-run.
- Windows 365 Cloud PC pool: isolated VM capacity that spins up on demand for the agent to run on. Better for security (the execution environment is ephemeral), worse for latency and credential management.
For most citizen-developer scenarios the Cloud PC pool is the right answer. Configure it through the Power Platform admin center; assign your agent to the pool you provisioned.
While you’re in admin settings, build the allow-list. The agent should be permitted to navigate to https://portal.examplevendor.com and https://contoso.sharepoint.com. Nothing else. The allow-list is the cheapest blast-radius control you have — use it.
Step 5: Test once, then promote (4 min)
In Copilot Studio’s test pane, give the agent a real invoice number it can look up. Watch what it does. The Tech Community blog explicitly notes that the new monitoring view surfaces what the agent “saw, clicked, and why,” which lands in both Purview and Dataverse — you’ll be able to audit the run trace if anything looks off.
If the test passes, publish. The agent is now callable from any other Copilot Studio agent, from Power Automate flows, from Teams (if you publish to Teams as a channel), or from UiPath Studio (if you’ve installed the bidirectional integration). Most citizen-developer setups call it from a single Power Automate flow scheduled nightly.
That’s the migration. The first one takes about 25 minutes of focused work end-to-end; the second takes 10.
What this means for you
The decision depends on what RPA you already run and who owns it.
If you’re a citizen developer with 1-3 Power Automate Desktop flows: port them this month. The CUA model handles dynamic UIs better than the brittle selector-based flows you’ve been maintaining. The first port takes a Saturday; the rest take an hour each.
If you’re an RPA developer with 10-20 UiPath flows: don’t migrate yet. The bidirectional integration means your existing UiPath assets work alongside Copilot Studio agents — keep what’s stable, build new agents in Copilot Studio for the dynamic-UI work UiPath struggles with. Migrate only when a flow breaks for an unrelated reason (UI redesign at the target site, e.g.).
If you’re on UiPath Community Edition for cost reasons: Copilot Studio CUA is plausibly cheaper, depending on your volume. Microsoft’s per-step credit pricing isn’t published in primary docs — community-sourced reports name 5 credits per step for standard GA models and 15 for premium experimental models. Run a 30-day pilot with one real flow, log the credits, project the cost. If it’s lower than your Community-edition upgrade path, migrate.
If you’re at an IT-buyer scale (200+ users with Power Platform licenses): CUA is in your existing Microsoft 365 / Power Platform billing — there’s no separate SKU to buy beyond what you’re already paying. The licensing question is whether your existing Power Platform per-user license covers the credits at your projected volume. It usually does for moderate usage; very heavy usage can blow past the included credits. Forecast before you scale.
If you’re a Big 4 advisory client with an existing UiPath estate: the conversation with your advisor is whether to consolidate. Most clients we’ve talked to are not consolidating — they’re running the bidirectional integration and adding Copilot Studio agents on top of the UiPath base. The “rip and replace” sell from Microsoft sales is real; the practical answer is hybrid.
If you’re a student or career-changer learning automation: Copilot Studio CUA is the cleaner thing to learn in 2026 than UiPath classic. The market is moving toward AI-driven UI automation; the prompt-engineering skill transfers across tools; the citizen-developer pattern is what most non-tech hires will be doing. UiPath classic is still a hireable skill but is moving into legacy-system territory.
What CUA still can’t replace
Five things to plan around — or to keep on UiPath for.
Virtualized desktop environments. If your automation runs against an app in Citrix XenApp, VMware Horizon, or a published-app environment where the screen is essentially a remote pixel stream, CUA struggles. The vision model can read what’s on the screen, but click latency and DOM-less interaction degrade reliability. UiPath’s CV-based selectors handle Citrix more robustly. Plan to keep Citrix automations on UiPath.
Java thick-client apps from 2007. Legacy banking apps, legacy ERP systems, anything Swing-based — CUA’s vision model recognizes the buttons, but the apps don’t fire standard accessibility events, so the agent struggles to confirm whether a click landed. The official Microsoft docs don’t enumerate this as an unsupported environment, but the practitioner pattern is consistent. Keep these on traditional RPA selector-based tools.
Electron apps with non-standard widgets. Many internal corporate tools (Slack, Notion, some Teams sidecar apps) are Electron-based and use custom widgets that don’t behave like standard Windows controls. CUA’s vision-based identification works, but it’s slower and less reliable than DOM-based identification would be. For Electron apps with a public API or webhook, prefer the API over CUA.
Hardware-attached automations. Anything involving USB-connected scanners, label printers with proprietary drivers, RFID readers, or physical-button keypads — CUA can’t see them. Keep these on traditional RPA with vendor-specific connectors.
High-precision OCR on scanned documents. CUA can read on-screen text, but it isn’t the right tool for digitizing scanned PDFs at production scale. Use Azure Document Intelligence (or your existing OCR stack — Tesseract, Abbyy, etc.) for the OCR step, then hand the structured output to CUA for the subsequent UI workflow.
The bottom line
CUA in Copilot Studio at GA is what citizen-developer RPA should have looked like all along. The dynamic-UI handling is the real win — your bots don’t break when the vendor changes their portal layout. The natural-language brief replaces the brittle selector chain that used to drive 60% of RPA maintenance hours.
The hybrid path is the honest answer for most teams: Copilot Studio CUA for the dynamic and the new, UiPath or Power Automate Desktop for the legacy and the stable, with the bidirectional integration knitting them together. The “all your RPA is now in Copilot Studio” story is the Microsoft sales pitch; the “the right tool for each automation” story is the practical roadmap.
If you want the structured way to learn this — agent design patterns, governance setup, the Copilot Studio model picker — the Microsoft Copilot course covers the broader product. For automation-specific workflows, the AI Business Automation course walks the citizen-developer rollout end to end. If you’re more interested in n8n-style workflow automation for non-Microsoft stacks, the automation workflows course covers that adjacent space.
Sources
- What’s new in Copilot Studio: May 2026 updates and features — Microsoft Copilot Studio Blog
- Automate web and desktop apps with computer use — Microsoft Learn
- Microsoft Copilot Studio 2026 release wave 1 — Microsoft Learn
- Announcing Agentic Automation with Bidirectional Integration between Microsoft Copilot Studio & UiPath — Microsoft Copilot Studio Blog
- Improve complex UI automation with computer-using agents — Microsoft Copilot Studio Blog
- Microsoft’s Computer-Use Agents in Copilot Studio Reach GA — Windows News
- Copilot Studio Computer-Use Agents: GA Deep Dive 2026 — DigitalApplied
- UiPath Announces Bi-directional Integrations with Microsoft Copilot Studio — UiPath
