Copilot Studio agents can now operate legacy screens
Microsoft made computer-using agents generally available in Copilot Studio on May 26. These agents can interact with websites and desktop applications through the user interface when the underlying system lacks an API. Microsoft also announced a redesigned workflows experience in early release environments. The new canvas lets teams combine fixed workflow steps, approvals, business logic, AI-powered actions, and agent nodes in one place. The same update includes real-time voice agents becoming generally available in North America through Dynamics 365 Contact Center, but the most relevant change for Power Platform builders is the move from chat-only agents toward agents that can operate existing screens.
For Power Apps builders, the impact is not that every awkward process should now be wrapped in an agent. The useful shift is that Copilot Studio can cover gaps where a team is stuck with a vendor portal, old desktop app, or legacy web screen that has no clean connector. That makes data and process design more important, not less. If a SharePoint list, canvas app, or approval workflow already has unclear fields and exception rules, a computer-using agent will only make those weaknesses harder to see. The best use case is a well-understood process with poor integration options, not a messy process that nobody has simplified yet.
Analysis
Before using a computer-using agent, map the process as if you were training a new teammate: exact screen, required field, expected result, and exception path. If you cannot describe those steps clearly, the agent will inherit the same messy process your users already struggle through.
Citation
This executive briefing was curated and analyzed by Collab365. To reference this analysis, please attribute: "This briefing is available on Collab365 Spaces (spaces.collab365.com)".