At Microsoft, our business operations teams help move work from quote to cash, support product launches, manage compliance, and coordinate partner processes. Much of that work spans globally distributed teams, multiple applications, and high-volume transaction flows. It’s an environment where automation has already made a substantial impact. But some of the remaining work still depends on people navigating interfaces, applying validations, and moving information across systems originally designed for human operators. That gap has become an important testing ground for AI-powered digital workers. Microsoft Business Operations, the Windows 365 product group, and our team in Microsoft Digital, the company’s IT organization, are working together to give those digital workers a secure, managed environment to perform computer-use tasks. Digital workers are AI agents with their own managed identity that can work across apps much like an employee does. The result is a process centered on Windows 365 for Agents, with our Business Process Outsourcing (BPO) AI Toolkit providing the workflow, knowledge, and agentic capabilities around it. We’re currently rolling this process out in phases. A pilot in one Microsoft Business Operations operating unit is now live, and we plan to extend it across our organization in the coming months. YouTube video: How Microsoft uses Windows 365 for Agents to automate business processesYouTube video: How Microsoft uses Windows 365 for Agents to automate business processes This video explores how Windows 365 for Agents enables digital workers to operate across different Windows applications, including legacy tools that lack reliable APIs, and accomplish business tasks with human oversight. (For a transcript, please view the video on YouTube: https://youtu.be/4bfWVo4lseo.) The need to give digital workers a secure, managed computer APIs, connectors, and deterministic automation continue to be useful for many tasks. But they can’t cover every enterprise workflow. In some cases, applications don’t expose a reliable API. In others, important validations live in the user interface, or the process depends on a desktop application built for people. Windows 365 for Agents gives AI agents—whether built by Microsoft, partners, or in-house teams—secure, on-demand Cloud PCs when they need to work in apps and interfaces the way a person would. In our case, we’re using it to support digital workers. A digital worker can check out a managed Cloud PC on demand, interact with desktop applications and files, complete its work, and return the machine to the pool for the next agent task. “Windows 365 gives the digital worker an enterprise-managed, enterprise-secure, and enterprise-visible device. The platform is already there, so line-of-business developers don’t have to build all the management and telemetry themselves.” Dave Rodriguez, principal product manager, Microsoft Digital For our operations scenario, the important point is parity: the digital worker operates in the same kind of Windows interface as a human counterpart, while authenticating through an agent-specific model. As a result, we can manage the agent with enterprise controls and constrain its access to the resources required for the task. That foundation changes the operational conversation. Instead of treating agent computer-use as an isolated script, the teams can consider device posture, identity, access, observability, support, and lifecycle management as part of one operating model. “Windows 365 gives the digital worker an enterprise-managed, enterprise-secure, and enterprise-visible device,” says Dave Rodriguez, principal product manager in Microsoft Digital. “The platform is already there, so line-of-business developers don’t have to build all the management and telemetry themselves.” The BPO AI Toolkit has reduced human touch by 75% and cut cycle time from 25 to 10.3 hours, while completing thousands of orders with no rework. With Windows 365 for Agents, the team has a path to further reduce human touch by up to 95% and processing time to four hours. A repeatable foundation for a variety of different scenarios The question then becomes: How do we activate digital workers efficiently? Our internal BPO AI Toolkit, built on Microsoft technologies, supports this objective by giving us a way to spin up digital workers quickly and easily. Microsoft Business Operations is using the toolkit with Dynamics 365, while its reusable capabilities provide a foundation for applying the same approach across other BPO scenarios. It provides a framework that includes an agentic UI, agentic memory, prebuilt agents, and digital twins, with a desktop layer to provide a computer for digital workers through Windows 365 for Agents. “AI’s greatest opportunity lies at the intersection of repetition and scale. By moving beyond isolated task automation to a digital workforce, we can scale operations without scaling human effort, freeing people to apply judgment, solve complex problems, and drive innovation.” Shashi Lanka Venkata, partner engineering manager, Commerce Platforms The toolkit helps teams capture operational knowledge, configure agents for specific business processes, and keep people focused on exceptions and decisions instead of routine execution. Agentic memory turns tribal knowledge into structured operational intelligence that agents can access on demand. Prebuilt agents provide enterprise-ready capabilities that teams can reuse instead of rebuilding workflows. An agentic UI reduces context-switching time, helping operators focus on decisions and exceptions. Digital Twins measures real end-to-end process performance and continuous improvement. Agent Desktop provides secure access anywhere. “AI’s greatest opportunity lies at the intersection of repetition and scale,” says Shashi Lanka Venkata, partner group engineering manager in Business Commerce Platforms. “By moving beyond isolated task automation to a digital workforce, we can scale operations without scaling human effort, freeing people to apply judgment, solve complex problems, and drive innovation.” But scale only pays off when the work being scaled is sound. That’s why Microsoft Business Operations pairs continuous improvement with AI. Before a digital worker takes on a workflow, the team first checks that the process steps, data, and policies behind it are worth automating. Once a process is ready, digital workers can take it on at a volume that people alone can’t match. “If you go straight into applying AI to bad, complex processes, poor data, or inefficient policies, you’re not going to deliver the step-change outcome you want. That’s why we describe our transformation approach as CI + AI.” James O’Connor, corporate vice president, Operations Service Center For example, we’re exploring opportunities for digital workers to take on high-volume order processing, including orders with tens of thousands of lines. Using Windows 365 for Agents, those digital workers can run on multiple Cloud PCs at the same time to distribute the work and increase processing throughput. Building a workflow around people and agents With the process simplified and ready for automation, the next step is putting the digital worker to work. “If you go straight into applying AI to bad, complex processes, poor data, or inefficient policies, you’re not going to deliver the step-change outcome you want,” says James O’Connor, corporate vice president of the Operations Service Center. “That’s why we describe our transformation approach as CI + AI.” Our BPO AI Toolkit provides a repeatable foundation for creating digital workers, while Windows 365 for Agents provides their operating environment. A process expert records how the digital worker should perform work. The toolkit helps convert that knowledge into structured process instructions, policies, reusable agent capabilities, and an execution plan. When a transaction enters the queue, an orchestrating agent can call the required skills and use Windows 365 for Agents when the job requires a desktop or browser interface. People stay part of the workflow throughout. The digital worker records evidence as it works and escalates exceptions with context. The human employee who reviews the exception shouldn’t need to reconstruct the process from the beginning. They only have to understand what the agent completed, what blocked progress, and what will happen after control returns to the workflow. That distinction is essential for sensitive operational work. The goal is autonomy with accountability so that routine steps can move through the system while people retain responsibility for gray areas, any necessary approvals, and business decisions. Learning from our role as Customer Zero As we’ve implemented Windows 365 for Agents internally, our Microsoft Digital team brought device management, identity, administration, and service-management experience to the engagement. Microsoft Business Operations supplied the process knowledge and implementation needs. And the Windows 365 product group used that feedback to understand what enterprise customers will need from the platform. “How are you going to lifecycle-manage a digital worker, observe it while it’s running, and retire it when it’s no longer providing value? You need the cleanup mechanism at the other end so you don’t create unnecessary security risk or operational clutter.” Dan Kaufman, partner group software engineering manager, Microsoft Digital The work highlighted the importance of planning for the full lifecycle before scale makes gaps difficult to bridge. That includes onboarding, ownership, permissions, cost allocation, monitoring, and retirement. “How are you going to lifecycle-manage a digital worker, observe it while it’s running, and retire it when it’s no longer providing value?” says Dan Kaufman, a partner group software engineering manager in Microsoft Digital. “You need the cleanup mechanism at the other end so you don’t create unnecessary security risk or operational clutter.” Some of the hardest problems had little to do with the agents themselves. Once the project reached execution, the teams had to work out how to provision Cloud PCs for digital workers, assign identities and licenses, and handle billing. Adding or removing those Cloud PCs meant manual steps for tenant administrators, which works for one team but not for dozens. Our tenant administration team helped unblock provisioning, and we’re working with Microsoft 365 FinOps on usage limits and cost allocation as agent usage grows. We also learned that least-privilege access can’t be an afterthought. For example, we might give a digital worker that enters orders the rights to create an order but not cancel or delete one. In one implementation, Microsoft Digital worked with networking and security teams to scope Global Secure Access to just the endpoints a digital worker needed, rather than giving it the same broad access as an employee. Over time, repeatable role-based profiles can make that model easier to apply across digital workers that perform similar functions. Finally, the engagement created a faster feedback loop between the internal customer and the product team. Product engineers could see where application compatibility, access controls, auditing, administration, and support roles needed to come together. For example, we’ve asked for the step-by-step audit recording the toolkit builds today to become a platform capability, along with role-based administration for the people who support digital workers. Meanwhile, the operations team gained a governed path for extending AI into workflows that still depend on Windows applications and user interfaces. Preparing to scale responsibly We now have a clearer model for where Windows 365 for Agents belongs in a workflow, and it’s not for every task. If an API or connector can complete a step reliably, teams can use it. But when a digital worker needs to interact with desktop applications, browsers, on-premises applications, or UI-based validations, a managed Windows Cloud PC becomes the execution environment. The broader lesson is that digital workers need more than an agent definition. They also need a simplified process, an identity and access model, a secure computer to act, evidence of what they did, people who own exceptions, and an operating model that covers cost and lifecycle management. “When organizations start applying agents to real business processes, the environment matters: it needs to be manageable, secure, observable, and ready to scale.” Phil Gerity, partner group product manager, Windows 365 for Agents For Microsoft, business operations has provided a practical area to prove these patterns. The work is repeatable enough to measure, demanding enough to expose real enterprise requirements, and important enough that we can’t defer security and accountability. By combining process expertise, IT operations, product engineering, and managed Windows Cloud PCs, we’re establishing a foundation that customers can adapt to their own high-volume workflows. “Windows 365 for Agents is about giving digital workers an enterprise-ready place to operate,” says Phil Gerity, partner group product manager for Windows 365 for Agents. “When organizations start applying agents to real business processes, the environment matters: it needs to be manageable, secure, observable, and ready to scale.” Key takeaways As you consider digital workers for your own business operations, keep these lessons from our Customer Zero work in mind: Start with process improvement. Simplify the workflow and identify repeatable, high-friction work before choosing an agent architecture. Use the simplest execution method that fits. Use APIs and deterministic automation when they exist and give digital workers managed computers when the task requires the agent to work across desktop applications, browsers, authenticated websites, files, and legacy systems. Implement least-privilege access from the beginning. Create reusable access patterns around the digital worker’s function and domain instead of copying a human employee profile. Keep people responsible for exceptions and decisions. Give reviewers the context, evidence, and next steps they need to take control efficiently. Plan the complete lifecycle. Define ownership, provisioning, observability, cost allocation, support, and retirement before scaling. Create fast Customer Zero feedback loops. Bring business, IT, security, and product teams together so that implementation lessons can improve both the deploymen