Explainer / Published 2026-10-26

Microsoft puts Home, Code, and Autopilot in a new Copilot

Microsoft’s September 25 update grouped chat, delegated work, app building, and a persistent agent in a new Copilot. As of October 24, Home view and Code are available through Frontier, while Autopilot remains Private Preview. Access depends on eligibility and, for organizations, administrator opt-in.

Conceptual workspace diagram showing a shared Home panel, a sandboxed app-building card, and an agent task awaiting review.
Conceptual editorial illustration; not a Microsoft Copilot screenshot.

THE SHORT VERSION

  • Microsoft announced Home, Code, and Autopilot on September 25. As of October 24, its current Copilot page lists Home view and Code in Frontier and Autopilot in Private Preview.
  • Home brings Chat and Cowork together and embeds editable Office work; Code is a sandboxed way to build apps, while Autopilot is a persistent agent still entering preview.
  • Organizations should track availability, inherited permissions, usage-based billing, and review points before making an agent part of a live workflow.

Three additions, one Copilot entry point

Microsoft announced Home, Code, and Autopilot for Copilot on September 25. Home is the new starting point, Code is a way to build software or small apps through natural-language requests, and Autopilot is a persistent agent intended to keep working across tasks. At launch, Microsoft said the experience would roll out through Frontier. As of October 24, its current Copilot page lists Home view and Code as Frontier features and Autopilot as Private Preview. The Frontier program gives early access before general availability. The current Frontier program page says business users need an eligible Microsoft 365 Copilot license and their organization must opt in; administrators control feature access, permissions, and usage-based billing. Eligible individual subscribers have a separate opt-in route in supported web apps.

Microsoft’s September 25 announcement set the original schedule: Code would start rolling into Frontier at the end of September, with broader availability in the following weeks. It described Teams’ shared-context @Copilot feature as a private preview planned for month-end and Autopilot as entering private preview in October. Windows Central’s coverage also noted that the rollout would not reach every user on day one. Those were launch plans, not a current availability guarantee.

Home joins chat with delegated Office work

Home brings Chat and Cowork into one starting point. Microsoft describes Chat as the place for quick questions, drafts, and lookups. Cowork handles work a user delegates, such as preparing an RFP response or customer briefing, then returns an editable result. The Home panel also shows recent activity and suggestions. For someone who moves between meetings, email, and documents, the practical claim is that the work can stay in one place rather than being rebuilt in each app.

Microsoft says Word, Excel, and PowerPoint are now built into Copilot. It also says role-specific Skills, such as financial skills in Excel and legal skills in Word, can be saved as reusable workflows for an organization. Skills guide a process; Code is for building a separate tool. A user can ask it to create or update a real document, workbook, or presentation, then collaborate on the same file with teammates. Windows Central describes Home as a dashboard that keeps work connected across Office apps and Teams. Those are product descriptions, not an independent measurement of time saved. Teams should still check where a file is stored, who can edit it, and which changes Copilot made before sharing a finished document.

Code is for building inside an organization’s environment

Code is aimed at people who want a small tool without starting with a programming language. Microsoft says a user can describe an app, workflow, or dashboard in plain language. The tool runs in a sandbox and can connect to live business data within the company’s Microsoft 365 environment. Microsoft also introduced Copilot Managed Runtime, an infrastructure layer for hosting code inside that environment under IT governance.

The distinction is useful for a team considering a spreadsheet helper or an internal dashboard. A generated app still needs an owner, an access policy, and checks against the source data. Microsoft’s announcement says Code shares underlying technology with GitHub Copilot, but ordinary users and professional developers have different workflows. Windows Central notes that Code is entering the Frontier program first, with broader availability expected later. The announcement does not establish that every generated app will be safe or correct without review. Microsoft also says Managed Runtime is meant to let teams share an app with colleagues and connect it to live data while IT retains governance, and it plans to open the runtime to third-party and pro-code developers. These are rollout plans, so confirm what the current tenant can use.

Autopilot is the part designed to keep going

Microsoft describes Autopilot as a persistent, proactive agent that can continue work when a user is away. The company says it can keep track of tasks and context across Microsoft apps. Its Home feature called Today is a related command center: it is planned to summarize missed email, meetings, and tasks, and can prepare a draft or propose a schedule change. Microsoft placed Autopilot in private preview for October and said it would also come to Outlook and Teams.

That future-tense wording sets a limit on what the September announcement proves. It documents the plan and preview schedule, not broad availability or successful completion of every long-running task. Windows Central reports that Autopilot can be assigned a role and a goal, and can use Microsoft 365 apps while the user is offline. Those details help readers picture the intended workflow, but the independent report is still coverage of a preview announcement, not a reliability study.

Shared context follows Teams permissions

Microsoft says @Copilot in Teams can use the shared context and permissions of a channel, group chat, or meeting. A user might ask why a decision was made, and Copilot can look across the conversation history. For a team, this could reduce the need to paste the same background into every request. Microsoft’s announcement says the feature was planned to enter private preview in Teams by the end of September.

The permission detail deserves a closer look before use. If Copilot sees the same channel context as a participant, administrators and team members need to know which channels the agent can reach and how a result will be shared. The announcement describes inherited permissions but does not provide a full permission matrix or retention policy for every context. Those details should be checked in the organization’s current Microsoft 365 documentation and tenant settings, particularly where private or regulated material appears in conversations.

Usage-based billing puts model choice in the cost discussion

Microsoft says longer-running agent work, including Cowork, Code, and Autopilot, uses usage-based billing. Administrators can set which model families different groups may use, manage spending policies through APIs, and review usage. End users can see credits used, balances, and usage history in Copilot. The company also described cost-management work in Agent 365 for Code and Copilot Managed Runtime.

These controls help a business set limits before it invites more people into an agent workflow. They do not answer the budget question by themselves. A pilot should record what task ran, which model was selected, how often it used tools, and whether someone had to repeat or correct the result. Microsoft’s announcement does not provide a universal per-task price because usage depends on the model and work performed. Teams should use the billing details shown for their own tenant rather than assume that agent use follows a flat seat fee.

Start with one workflow that has a clear review point

A sensible first pilot is a task whose result can be compared with an existing record. For example, a team could ask Copilot to draft a meeting brief from a channel and a set of approved documents, then check the cited decisions before sending it. A Code project could begin with a read-only dashboard against a non-sensitive dataset. An Autopilot task should pause before emailing an external person or changing a live schedule.

This keeps the trial focused on what Microsoft announced: connecting tasks, files, and app-building in one environment. Track whether the agent used the right context, whether the output needed edits, and whether permissions and costs behaved as expected. A private preview is an invitation to learn about an unfinished workflow. It is not evidence that a team can remove its usual review step.

Sources & reporting limits

  1. Introducing the new Copilot with Home, Code and Autopilot
  2. Microsoft just rethought its entire AI strategy: What the new Copilot means for Windows & your everyday workflows
  3. Microsoft Copilot: AI built for work
  4. Explore AI Early Access in Microsoft 365 | Microsoft Frontier
Keep the thread.

Follow Products to find related stories on your next visit.

THE WEEKLY EDIT

The week, made clear.

Stories worth understanding, brought together in one weekly edition.

Share this page

Instagram, TikTok & other apps

Copy the page link, then paste it where your chosen app supports links. You choose whether to send or publish.