Microsoft Rebuilds Copilot Around Home, Code and Autopilot

Microsoft is reorganizing Copilot around three jobs: Home for asking questions and delegating work, Code for building internal apps, and Autopilot for work that continues without a fresh prompt. The September 25 announcement (opens in new tab) also puts Word, Excel and PowerPoint inside Copilot and sketches a proactive view called Today. Satya Nadella introduced the update on X (opens in new tab) as an “OS for work.” The immediate questions for a team are which parts it can access, what an agent can reach and how the metered work is paid for.

From a chat window to a place to build

Home is set to bring Copilot Chat and Cowork together as it starts rolling out through the Frontier early-access program (opens in new tab) in the coming weeks. Chat handles the immediate question or draft; Cowork takes a delegated, multi-step task and returns a result. Office in Copilot is designed to create or update editable Word documents, Excel workbooks and PowerPoint presentations, with changes kept in sync with the Office apps. Microsoft says automatic routing of a request to Chat, Cowork or Code is coming soon, not a feature every user gets with this announcement. Cowork itself reached general availability in June (opens in new tab), which is different from the rollout status of the new Home experience.

Code, scheduled to reach Frontier at the end of September, is the builder-facing addition. Describe a tracker, dashboard, workflow or small app, and Microsoft says Copilot will choose a form and build it. Microsoft says it uses the same underlying technology as GitHub Copilot, runs in a sandboxed environment, and can host apps within a company's Microsoft 365 tenant. That does not make Code a replacement for GitHub Copilot's developer workflow; the launch post explicitly keeps developers using GitHub Copilot while connecting their work to the wider Copilot platform.

Copilot Managed Runtime (opens in new tab) is the hosting layer behind those apps, now in public preview. It supplies a Microsoft-operated host, Entra identity, governed data connections, versioning and an app inventory in the Microsoft 365 admin center. Microsoft says apps built through Cowork, Code and Copilot Studio use this foundation, and is opening an SDK and CLI path for outside development tools. A generated app is only useful to an IT team if its data access, connectors and users can still be managed after the demo.

Scout becomes a cloud-hosted Autopilot

Autopilot, whose private preview Microsoft says will expand at the end of September, is a persistent, cloud-hosted agent with its own identity, memory, workspace and computer inside a tenant. Microsoft describes assigning it a role and goal, then letting it watch channels, follow up on threads and resume recurring work. It is designed to appear in Teams, Outlook, chats and documents, with organizational permissions and audit controls applying to its actions. These are Microsoft's described capabilities (opens in new tab), not generally available behavior.

Microsoft introduced Scout in June (opens in new tab) as its first agent in the Autopilots category. Its earlier desktop experience was experimental, available to selected preview customers and Frontier organizations under additional setup requirements. The September announcement renames Scout Autopilot and describes a cloud-hosted experience, but does not say that earlier Scout access automatically carries into the expanded private preview.

Code is also slated for broader availability in the weeks after its Frontier debut and a preview for Microsoft 365 Premium and Pro subscribers later in 2026. A new plugin registry is rolling out now, with availability across supported surfaces in the coming weeks. The separate Today view is designed to prepare a catch-up across mail, calendar, Teams and tasks; it is due in private preview in October. Invoking @Copilot in Teams is due for private preview by the end of September. Those are Microsoft's announced schedules (opens in new tab), not dates when every tenant receives the features.

The bill changes with the job

Microsoft sells everyday Chat and in-app Office use under a user subscription license (USL). The license is also required before an organization can use metered capabilities such as Cowork, Code and Autopilot; usage-based billing is in addition to, not a replacement for, the subscription. For enterprise customers, those services remain off until an administrator creates a spending policy in the Microsoft 365 admin center, and Microsoft says nothing is billed before that. The company's September 25 pricing explanation (opens in new tab) describes budgets, user-level caps within group policies, model-family controls and end-user views of Copilot Credit usage. Cowork's earlier launch (opens in new tab) published a pay-as-you-go rate per credit, but neither announcement gives a single fixed price for an Autopilot task or a Code app.

The immediate evaluation is therefore practical: check whether your tenant is enrolled in Frontier (opens in new tab), which of these previews your administrator has enabled, what identities and data sources an app or agent can reach, and which work is metered. The announcement puts more of the work loop inside Copilot, but the dates, permissions and billable runtime determine when that loop is useful to a real team.