Microsoft has redesigned Copilot around three connected capabilities: Home for chat and delegated work, Code for building apps and automations, and Autopilot for persistent work that continues without repeated prompting.
Autopilot—previously called Scout—is a cloud-hosted agent with its own identity, memory, computer, and workspace. Microsoft says it can monitor channels, follow up on conversations, run recurring workflows, contact stakeholders, and resume projects days later. It operates across tools including Teams and Outlook while remaining subject to tenant permissions, auditing, and governance.
The accompanying Code experience uses technology from GitHub Copilot to create dashboards, workflows, desktop widgets, and internal apps inside a sandboxed environment. Microsoft’s new Copilot Managed Runtime provides tenant-controlled hosting for solutions built through Code, Cowork, and Copilot Studio.
Autopilot is scheduled to expand into private preview at the end of September. Home and Code will begin rolling out through Microsoft’s Frontier program over the coming weeks.
Why it matters
This release moves enterprise agents beyond isolated conversations and toward durable responsibility. The important product layer is not only model intelligence: Microsoft is packaging identity, memory, execution infrastructure, organizational context, permissions, auditing, and cost controls around an agent that can keep working in the background.
For builders, it is another strong signal that persistent execution and governance are becoming standard requirements for production agents—not optional infrastructure added after a prototype. That same shift is visible in AWS’s production agent runtime, where isolation, startup speed, state, and resource control are treated as platform concerns.