AI applications · Workplace tools · Original analysis

Microsoft’s new Copilot splits work across Home, Code and Autopilot

The new structure combines conversation, creation and ongoing work. The rollout and the boundary between them still matter.

Microsoft Copilot wordmark.
Microsoft Copilot wordmark. Credit: Microsoft · Public domain. Resized and converted to WebP; padded to 16:9 without cropping.

Microsoft announced a new Copilot experience with Home, Code and Autopilot on September 25, 2026. Home brings Chat and Cowork together, Code supports building solutions, and Autopilot is described as a persistent proactive agent. The announcement also introduces AI spending-management capabilities.

Microsoft says Home and Code will begin rolling out through its Frontier program in the coming weeks, while Autopilot expands to private preview at the end of the month. Those stages should not be described as universal availability for every Microsoft account.

Different modes need different acceptance criteria

Microsoft describes Office capabilities within Copilot for creating and updating editable documents, workbooks and presentations. Code uses underlying GitHub Copilot technology, while Autopilot targets work that continues outside an active conversation. The product names organize intended workflows, but they do not remove the need to check the resulting work.

A document draft can be reviewed for meaning and source accuracy. A workbook also needs correct formulas, units and references. An application needs working behaviour, access controls and a maintenance owner. A single prompt may begin all three, but the evidence required to accept them is different.

Related sources: Microsoft introduces Copilot Home, Code and Autopilot ↗

Persistent work requires visible ownership

When a task continues in the background, the team should know what information it reads, what it can change and when a person is required. Assign a clear owner for reviewing results and updating instructions. A stale assumption can remain influential after the original conversation ends.

Track the difference between a suggestion, a prepared change and an applied change. For shared files, keep versions or an inspectable record so collaborators understand what happened. The useful result is a maintained artifact that the team can use, rather than an impressive demonstration that nobody can confidently edit.

How to evaluate the rollout in a Canadian workplace

Confirm the tenant, licence and program access for the feature being tested. Include English and French documents if the team works bilingually. Check sharing permissions before giving an agent access to a broad set of files, and measure whether the new workflow reduces correction and coordination effort.

The September announcement sets out a direction and a staged release. Future product documentation should resolve the exact access and operating details. A small trial with a real editable deliverable can show whether Home, Code or Autopilot improves the team’s work without hiding responsibility for the outcome.

Sources and editorial method

We use the linked original statements and reports to distinguish documented facts from our analysis. Company announcements describe their authors’ plans and claims; they are not independent verification of future outcomes. This article is dated and will be revised if material evidence changes. Read our editorial standards and corrections process.

  1. Microsoft introduces Copilot Home, Code and Autopilot ↗ — September 25, 2026; feature descriptions and Frontier/private-preview rollout plans.