Microsoft Copilot Can Keep Working While Users Are Away

In its September 25, 2026 announcement, Microsoft introduced a redesigned Copilot app with Home, Code and Autopilot. Autopilot is designed to continue delegated work while its user is away, but access is limited: Home and Code are rolling out in stages through Frontier, while Autopilot is set to expand to private preview at the end of the month.

GeekWire’s September 25 report says Code was already with a small group of Frontier customers and that most new features would reach users gradually. The practical division is straightforward: Home combines Chat and Cowork, Code builds apps and automations from a request, and Autopilot is intended to keep carrying out an assignment without a fresh prompt for each step. Their different release stages matter as much as their different jobs.

What is available, and to whom?

The announcement combines capabilities already available in parts of Copilot with new experiences still being introduced. The distinction is between access to an existing component and access to the redesigned place where Microsoft intends to bring those components together.

Home — staged Frontier rollout: The new starting point brings conversational Chat and delegated Cowork work into one place. Its availability follows the rollout of the redesigned experience; having access to Chat or Cowork does not, by itself, mean the new Home view has reached an account.
Code — limited access, then a wider Frontier rollout: A small Frontier group already has it. Microsoft plans to extend it within Frontier at the end of the month, followed by broader availability in the coming weeks. A preview for Microsoft 365 Premium and Pro subscribers is planned for later in the year.
Autopilot — private preview: The agent is meant to monitor relevant work, handle recurring tasks and continue an assignment while its user is away. Its next stated access stage is an expanded private preview, not a general release.
Supporting integrations — different stages: Fabric IQ grounding is generally available in Chat and Cowork, but its connection to Code is still planned through Frontier. Copilot Managed Runtime, the hosting foundation for apps built with these experiences, is in preview.

Home brings conversation and delegated work together

Home is designed as the place to start or resume work in Copilot. Chat handles immediate questions, lookups and drafts. Cowork accepts a defined assignment and works toward a result that the user can review and refine. The redesigned Home view is intended to show recent activity and suggestions alongside those modes, so a person can return to work already in progress.

Office in Copilot adds another distinction: Word documents, Excel workbooks and PowerPoint presentations can be created or edited within the Copilot experience while remaining editable in the Office apps. That integration is rolling out to consumers and Frontier customers. Automatic routing of a request to Chat, Cowork or Code is described as a future capability, so the new starting point should not be mistaken for a promise that Copilot already chooses among those modes for every user.

Code builds tools rather than another document

Code is aimed at a different output from Home’s drafts and files. A user can describe an app, tracker, dashboard or automation in ordinary language, and Copilot is intended to build a purpose-built solution. The examples range from a desktop widget to an internal app that a team can share. This is a way to make a work tool inside Copilot, rather than a new name for GitHub Copilot’s developer workflow, although the two use the same underlying technology.

Where that tool runs is part of the enterprise proposition. Code works in a sandboxed environment, and Copilot Managed Runtime is intended to host resulting apps inside a company’s Microsoft 365 environment, where IT can govern them. The runtime is itself in preview. A generated app’s potential to connect to live data or be shared across a team therefore needs to be read alongside the rollout status of both Code and its hosting foundation.

Autopilot is the unattended part of the promise

Autopilot is the capability behind the headline’s claim that Copilot can keep working without its user present. A person gives the agent a role, goal and boundaries; it is designed to follow conversations, perform recurring work and return to an assignment later without waiting for another prompt. Cloud hosting is what allows that work to continue when the person is away from their computer.

For organizations, the intended design places an Autopilot inside their tenant with its own identity, memory, computer and workspace. It can participate through Teams, Outlook, chats, channels and documents, with permissions, audit and governance attached to its activity. Those are described product capabilities, not evidence that an organization can deploy Autopilot broadly today or that its performance on sustained assignments has been independently established.

Licenses and administrators shape access

Frontier eligibility is another boundary. Microsoft’s Frontier guidance says enterprise and business users with a Microsoft Copilot license can try available Frontier features, subject to availability and their organization’s admin settings. Eligibility does not bypass a staged rollout, and Frontier access does not grant entry to a private preview.

Administrators also have controls over what agent work can use and cost. The new plugin registry is intended to let IT approve and manage plugins centrally. For usage-based work, administrators can set spending policies, route requests for additional credits through approval workflows and limit which model families groups may use. Cowork, Code and Autopilot fall under usage-based billing, separately from everyday Copilot features covered by a user subscription license.

The published timetable leaves Autopilot at private-preview expansion, with no general-release date for the unattended agent. Home and Code have rollout plans, but their appearance in any particular organization still depends on deployment and administrative settings. That is the current limit on Microsoft’s promise of work that continues after a user steps away.