Automate a legacy admin task with Computer use
An operations team has to copy approved information between a legacy web portal and Microsoft 365, but the portal has no suitable API or connector. A Copilot Studio Agent uses Computer use to navigate the portal and prepare the repetitive updates while higher-impact steps remain supervised.
Where the action happens
Copilot Studio / Computer use / Windows or web application
Product or feature needed
Copilot Studio Computer use with virtual mouse and keyboard
AI required
Yes
Extra credits
Yes - Copilot Studio and Computer use consumption/capacity can apply
Technical skill
High
Risk level
High - UI automation can interact with live systems and must be tightly scoped, monitored and supervised
Licence dependency
Copilot Studio access plus the environment/machine requirements for Computer use.
Credit dependency
Copilot Studio/Copilot Credit and related execution capacity may apply depending on configuration.
UK availability
preview
What it can do
- Interact with websites and Windows applications when a suitable API or connector is unavailable.
- Navigate menus, select controls and enter text using a virtual mouse and keyboard.
- Adapt to some interface changes that would break rigid screen-coordinate automation.
- Provide detailed activity/transcript logs and screenshots for review where configured.
Limitations
- Prefer a supported API, connector or deterministic automation when one exists; UI automation adds operational uncertainty.
- The Agent can make the wrong selection or act on an unexpected screen state, so consequential steps need human supervision.
- Computer use has platform and environment limitations and should be tested against representative real-world screens.
- Do not use a maker's broad personal account as the convenient execution identity for a shared production automation.
Prerequisites
- A justified use case where no suitable API or connector is available.
- A dedicated or deliberately scoped account/environment with least-privilege access.
- Representative test cases, including error and unexpected-screen scenarios.
- Activity logging/monitoring and a named operational owner.
- Human approval or supervision before consequential changes where appropriate.
Workarounds
If a supported API, standard/premium connector or normal Power Automate action can perform the same task reliably, use that instead of Computer use.
No premium licensing needed. External dependency: API / connector availability.
Notes
Use Computer use as a fallback for systems without suitable APIs/connectors, not as the default integration pattern.
Watch-outs for Organisational Agents
- Do not jump to Copilot Studio just because the word Agent sounds more advanced; use it when the use case genuinely needs actions, channels, integrations or stronger lifecycle control.
- Admins can govern environments, connectors, data movement and publishing through Power Platform controls.
- Distinguish the Entra Agent ID used for authentication from any persistent Microsoft 365 working identity the Agent may be given.
- Prefer deliberately scoped sources and identities; do not allow a shared Agent to rely silently on the maker's personal credentials.
- Where an Agent can take a consequential action, use human approval for the relevant tool call or a separate approval step where available.
- Use Computer use when a suitable API/connector is unavailable, not merely because UI automation is easy to demonstrate; use least privilege, representative testing, logs and human supervision.
- Treat reusable Skills as shared organisational logic with ownership, testing and change control.
- Self-learning recommendations do not publish themselves: review the evidence, configure deliberately, test and publish through normal change control.
- External-facing Agents need clear boundaries, handoff routes and monitoring.
- Published Agents should have named business and technical owners, approved sources, test/evaluation evidence, review dates and retirement criteria.
Sources
- https://learn.microsoft.com/en-us/microsoft-copilot-studio/computer-use
- Automate web and desktop apps with computer use checked 2026-10-06
- Monitor computer use checked 2026-10-06
- Computer use FAQ and safeguards checked 2026-10-06
Last checked: 2026-10-06
Community feedback
Has your organisation tried this? Confirm whether it's possible, whether it's useful, and share any tips.
0
Confirmed possible
0
Reported not possible
0
Found it useful
0
Not useful
Loading feedback…