---
title: "Copilot's Home, Code and Autopilot: roles, pricing, rollout"
description: "Microsoft's Copilot reorganization (Home / Code / Autopilot) by role, pricing and rollout schedule, with governance questions for large enterprises."
url: https://udon-dev.com/en/notes/copilot-home-code-autopilot/
lang: en
published: 2026-09-26
topic: [microsoft-365, ai]
tags: ["copilot", "microsoft-365", "ai-agent", "governance", "frontier-program"]
---

# Copilot's Home, Code and Autopilot: roles, pricing, rollout

- Microsoft announced that it is reorganizing Copilot around three pillars: Home, Code and Autopilot
- Home is the combined entry point for Chat and Cowork, Code builds apps in natural language for non-developers, and Autopilot is a personal agent that keeps working on its own
- Everyday Chat use is covered by a per-user monthly license (flat rate), while agent work such as Cowork, Code and Autopilot is pay-as-you-go (Copilot Credits)
- Home and Code roll out through the Frontier program within a few weeks, and Autopilot rolls out in stages as a private preview from the end of the month
- Before deploying at a large company, sort out permission design, cost control (FinOps for AI) and the division of roles with Copilot Studio

On September 25, 2026, Microsoft [announced a major overhaul of Copilot on its official blog](https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/).

It reorganizes individual features, such as Chat, Cowork and Office integration, into **three pillars: "Home", "Code" and "Autopilot"**.

## What each pillar does

### Home: the combined entry point for Chat and Cowork

**Home** is Copilot's new starting point, and it merges the previous Chat and Cowork into one.

- **Chat**: for conversational use, such as questions you want answered right away and drafting
- **Cowork**: for handing off larger pieces of work, such as responding to an RFP, building a set of documents or pulling together financial results

In the image on the official blog, Copilot's screen has three tabs along the top: Home, Code and Autopilot. Opening Home shows menu items such as "New chat", "Search", "Library" and "Plugins".

（図: The Copilot screen. Three tabs, Home, Code and Autopilot, run along the top, and under Home the menu lists "New chat", "Search", "Library" and "Plugins". The background shows PowerPoint, Excel, Outlook and Teams icons and the words "The AI built for work"）
Source: [Introducing the new Copilot, with Home, Code, and Autopilot (Microsoft blog)](https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/)

Along with this, "Office in Copilot" lets you use Word, Excel and PowerPoint features directly from inside Copilot.

### Code: building apps in natural language for non-developers

**Code** lets business staff who aren't developers build dashboards, automations and simple business apps in natural language.

In the image on the official blog, the Code tab lists "New session", "My tasks", "Customize" and "Automations". The input box holds the request "Make a dashboard of our pipeline by region and stage". The intended use is to describe in writing what you want built.

（図: The Code tab in Copilot. On the left, the menu lists "New session", "My tasks", "Customize" and "Automations", and the input box in the center contains "Make a dashboard of our pipeline by region and stage"）
Source: [Introducing the new Copilot, with Home, Code, and Autopilot (Microsoft blog)](https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/)

It uses the same underlying technology as GitHub Copilot, but is positioned differently. Software developers are expected to keep using GitHub Copilot, and Code is presented as a way for business departments to build small business apps themselves.

Apps you create run on a new runtime, **Copilot Managed Runtime**. According to the announcement, it is a foundation that runs code safely inside your own Microsoft 365 environment. IT stays in control, while other users can share apps with colleagues, connect them to real data and access them from anywhere. This foundation is common not only to Cowork and Code but also to apps built in Copilot Studio, discussed below.

### Autopilot: an agent that stays resident and keeps working

**Autopilot** is a resident personal agent that keeps working without waiting for instructions. The announcement stresses three traits: "persistent, proactive and personal".

One example given is handing off a whole business process that runs over a period of time, such as a supplier review. You can call it with an @mention from places like Teams. It is also said to have its own identity, memory and workspace in the tenant, and to run with permission management, auditing and governance in place.

In the image on the official blog too, the Autopilot input box reads "Run the supplier review". Below it, "What's been happening" lists the work Autopilot has done so far in chronological order. The menu on the left is "Overview", "Routines" and "Plugins".

（図: The Autopilot tab in Copilot. On the left, the menu lists "Overview", "Routines" and "Plugins", the input box in the center reads "Run the supplier review", and below it, "What's been happening" shows a history of work）
Source: [Introducing the new Copilot, with Home, Code, and Autopilot (Microsoft blog)](https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/)

## Pricing

Pricing falls broadly into two mechanisms.

| Billing model | What it covers |
| --- | --- |
| Per-user monthly license (flat rate) | Basic features included in the flat rate, such as everyday Chat |
| Usage-based, pay as you go | Features where an agent does the work, such as Cowork, Code and Autopilot. They consume "Copilot Credits" |

Within the monthly license, an "Auto" feature that automatically picks the best model for each request is also described.

Because agent features are pay-as-you-go by default, note that **the design means cost grows the more you use them**. With that in mind, "**FinOps for AI**" is also introduced, which lets admins visualize and control spending policies and usage.

## Rollout schedule

- **Home and Code**: rollout begins within a few weeks through the Frontier program
- **Autopilot**: the private preview expands from the end of the month (end of September 2026)

The Frontier program is Microsoft 365's early-access program, which rolls features out to eligible organizations in stages. In the information I reviewed, I couldn't confirm details such as how to join the Frontier program or its registration steps.

## What to think about when deploying at a large company

Each of the three pillars has different users and a different scope of permissions.

### Permission design and tenant management

Autopilot is described as having "its own identity, memory and workspace in the tenant", which means another kind of managed object besides people's accounts.

- Who can create and stop an Autopilot
- The scope of permissions given to an Autopilot (which data it can access, which actions it can run)
- How to inventory and audit the agents that have been created

You will need to decide these management processes in advance, while checking the features in Copilot Managed Runtime and the Microsoft 365 admin center.

### Cost control (FinOps for AI)

Since Cowork, Code and Autopilot are pay-as-you-go, cost rises as use spreads. Setting spending policies and visualizing usage through FinOps for AI is a feature to turn on from the early stage of a rollout.

Per-department usage caps, and how alerts are designed for unexpectedly high usage, are things to test in a validation environment before a company-wide rollout.

### Choosing between this and Copilot Studio

Microsoft already has **Copilot Studio**, for building custom AI agents with no-code or low-code. The announcement explains that apps built in Cowork and Code and apps built in Copilot Studio run on the same Copilot Managed Runtime foundation. The foundation is shared, but the announcement I reviewed doesn't clearly address the division of roles itself, meaning when to use Code or Autopilot versus Copilot Studio.

As a general way to sort it from what is known now, these differences seem reasonable.

| | Main use | Intended builder |
| --- | --- | --- |
| Copilot Studio | Carefully built agents, including custom flows and external system integration | Business department staff to specialist teams |
| Code | Dashboards, simple apps and automations in natural language | Non-developer business staff |
| Autopilot | A resident agent you give a goal and let keep working | Individuals and teams that "have" an Autopilot |

> [!WARNING]
> In the information I reviewed, I couldn't confirm how agents and flows already built in Copilot Studio will be treated as Code and Autopilot roll out (whether they will be merged or stay managed separately). If you have existing Copilot Studio assets, check the official information yourself.

The Frontier program and private preview are still at an early stage, so the official terms of availability and management feature details are expected to be updated in future official information. When considering a rollout, check the [Microsoft blog](https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/) for the latest.