Microsoft Copilot Studio Brings Computer-Using Agents to the Enterprise - DevOps.com

"For years, IT and DevOps teams have wrestled with the same stubborn problem: how do you automate workflows in systems that were never built for automation? Legacy apps, vendor portals, and proprietary line-of-business platforms rarely offer APIs. That means someone, usually a human, ends up clicking through screens, entering data, and completing transactions by hand."

"The simplest way to think about it: computer use gives an agent the same tools a person has - a browser, a screen, a keyboard, and the ability to read what's on the page and take the next logical step. That's a meaningful shift. Most automation tools rely on brittle, selector-based scripts that break the moment a UI changes. Instead, the computer uses a tool that relies on vision and reasoning to navigate live UIs - adapting when layouts shift, fields move, or workflows branch."

"In practical terms, this means agents can now handle workflows that previously required manual workarounds or expensive integration projects. For organizations with deep investments in proprietary platforms or third-party portals, workflows that previously required either a multi-quarter integration project or an army of contractors clicking through screens can now be handed to an agent. For enterprise IT teams, this can also reduce pressure to modernize or rebuild legacy systems before automation can begin."

"Microsoft points to Graebel, a global mobility and relocation services company, as an early example of what this looks like in production. Working with GET AI and Microsoft, Graebel built and deployed the Graebel Service Order Agent in Microsoft Copilot Studio. The agent monitors designated mailboxes and interprets unstructured service-order emails us"

Legacy systems often lack APIs, forcing humans to click through vendor portals and proprietary platforms to complete transactions. Computer use in Microsoft Copilot Studio provides agents with the same tools a person uses: a browser, a screen, and a keyboard, plus the ability to read what appears on the page and choose the next step. This approach reduces brittleness because navigation relies on vision and reasoning rather than fixed selector-based scripts. Agents can adapt to UI changes, moved fields, and branching workflows. As a result, organizations can automate processes that previously required workarounds, long integration projects, or large contractor teams, including workflows tied to proprietary platforms. Graebel used this capability to build a service order agent that monitors mailboxes and interprets unstructured emails.

Read at DevOps.com