Copilot's New “Autopilot” Is Not Windows Autopilot: What the 25 September Relaunch Actually Ships

The problem: one word, two unrelated products, zero GA

Satya Nadella's announcement described Copilot as "a new OS for work" and listed four components. It reads like a shipping product. It is not one.

For an endpoint team this creates two concrete problems in the same week.

Problem one is naming. There are now two Microsoft products called Autopilot, and they have nothing in common — not a portal, not a licence, not a support team.

Here is what that looks like in practice. A ticket arrives:

Before October, that meant one thing: Sarah's new laptop failed to provision. From October, it could equally mean the AI agent stopped drafting her meeting notes. Same word, two teams, two completely different investigations. The device team picks it up, spends twenty minutes checking Entra and Intune, finds nothing wrong, and only then discovers it was never their ticket.

Microsoft has not published anything to help you tell them apart. The Windows Autopilot known issues page was last updated on 8 September 2026 and does not mention the new agent, a rename or a deprecation. The launch blog does not mention Windows Autopilot either. Neither product acknowledges the other exists.

Problem two is billing. The announcement quietly confirmed that the new long-running agents do not bill the way Copilot has billed until now. That change has a date attached to it, and the date is close.

What actually shipped, and at what stage

This is the table that was missing from the coverage. Every status below is taken from Microsoft's own announcement.

Why it happens: Scout got renamed, and the licence model forked

The Autopilot name

This did not happen overnight. It happened in two steps, and the first one was back in June.

On 2 June 2026 at Build, Microsoft introduced a whole category of agents. Their words: "Today we are introducing a new category of agents called Autopilots." The first product in that category was not called Autopilot — it was called Scout. Microsoft said: "We are also introducing Microsoft Scout, our first Autopilot agent." We covered it at the time in our Scout write-up.

So in June, "Autopilot" was a category, and "Scout" was the product. Confusing, but survivable.

On 25 September 2026 Microsoft collapsed the two. From the launch blog, verbatim: "Autopilot, previously called Scout, is your digital teammate." The category name became the product name.

Microsoft did not retire or rename Windows Autopilot to make room, so both products keep the name.

What the new Autopilot actually does

It helps to see a real example, because once you do, the gap between the two products is obvious.

Microsoft's own examples of the work this agent takes on: scheduling meetings across time zones, flagging the meetings that matter, writing your prep materials, spotting deliverables coming up, blocking time in your calendar for them, and noticing when a decision has stalled. Microsoft describes it as an agent that "keeps working even when you're not", and one you "@mention like a colleague".

In other words: it is a digital assistant that manages your working day. Windows Autopilot turns a factory-fresh laptop into a managed corporate device. There is no overlap whatsoever — which is exactly why sharing a name is such a problem.

The licence fork

Until now, Microsoft 365 Copilot was overwhelmingly a per-user subscription story: buy a seat, the user gets Copilot. The relaunch formalises a split that has been building since Cowork went GA.

• User Subscription Licence (USL) still covers Copilot in Chat and across Word, Excel, PowerPoint, Outlook and Teams, plus model selection.
• Usage-Based Billing (UBB) covers Cowork, Code and Autopilot — the long-running agentic capabilities — metered in Copilot Credits.

Put plainly: the three features Microsoft led the announcement with are the three your existing licence does not cover. If every user in your tenant has a full Microsoft 365 Copilot licence today, you still cannot use Autopilot or Code until someone sets up credits and agrees to pay per use.

The practical difference is how the bill behaves. A per-user licence is a fixed, predictable number you agreed in advance. Credits are metered — the cost depends on how much work the agents do, which is not something you set at purchase time.

How to verify: what is actually live in your tenant today

Ignore the announcement for a moment. Here is what you can check right now, and what you will find.

1. Check which services are currently metered

Microsoft's own documentation, last revised 10 September 2026, lists exactly three services under usage-based billing in the Microsoft 365 admin center:

• Cowork
• Apps built with Copilot Cowork
• Work IQ API

Code and Autopilot are not on that list yet. They were announced as usage-based, but the admin surface has not caught up. That gap is the whole reason the next check matters.

2. Find the Cost management dashboard

This is the blade that governs all of it. Sign in to the Microsoft 365 admin center as a Global administrator or Billing administrator and navigate to:

If you have never set this up, you will see a Get Started button rather than a policy list. That is the safe state — nothing is metered, and nothing new can be auto-added, because there is no policy to add it to.

If you have set it up, open each policy and go to the Select agents and services step. That is where the next check lives.

3. Check the Auto-apply new services toggle

This is the single most important setting in this entire post. Microsoft's wording is unambiguous: "By default, the Auto-apply new services toggle is selected for spending policies." And: "When the setting is on, newly supported Microsoft Copilot services and agents are automatically added to the policy."

Read that against the previous check. Code and Autopilot are announced as usage-based, but they are not on the supported-services list yet. When Microsoft adds them — and the docs say "Microsoft will add more agents and services over time" — every policy with this toggle on picks them up automatically. No admin action, no approval step, no email.

Here is the sequence, using a setup most tenants already have:

Nothing there is a bug. Every step is the documented default. That is what makes it worth checking now rather than reading about it on an invoice.

4. Check whether you are exposed to the CSP default change

If you buy through a Cloud Solution Provider, there is a hard date. Per the September 2026 Partner Center announcements:

Starting November 2, 2026, new Microsoft 365 Copilot Business licenses that you purchase through Cloud Solution Provider (CSP) include usage-based billing by default. Pay-as-you-go is the default billing configuration.

Three specifics worth pulling out of that. It applies to new purchases of M365 Copilot Business, standalone and bundles. It sets pay-as-you-go as the default configuration, not prepaid. And Microsoft states the licences "include the Azure subscription setup needed for usage-based billing" — so an Azure subscription gets wired in as part of the purchase.

5. Audit who can actually change any of this

The role model here is split in a way that surprises people. Billing method and spending policy are different permissions:

To see who currently holds those roles, run this against Microsoft Graph. It reports the members of each role that governs Copilot spend, so you know exactly who can commit your tenant to metered consumption.

Connect-MgGraph -Scopes 'RoleManagement.Read.Directory','Directory.Read.All'

# Roles that can create spending policies or set a billing method
$targets = 'Global Administrator','Billing Administrator',
             'AI Administrator','License Administrator'

# NOTE: Get-MgDirectoryRole returns only ACTIVATED roles. A role that has
# never been assigned is absent from the list, not empty. That is expected.
$all = Get-MgDirectoryRole -All

$targets | ForEach-Object {
    $role = $all | Where-Object DisplayName -eq $_
    if (-not $role) {
        [pscustomobject]@{ Role = $_; Member = '(role not activated)'; UPN = '' }
        return
    }
    Get-MgDirectoryRoleMember -DirectoryRoleId $role.Id -All | ForEach-Object {
        $u = Get-MgUser -UserId $_.Id -ErrorAction SilentlyContinue
        [pscustomobject]@{
            Role   = $role.DisplayName
            Member = if ($u) { $u.DisplayName } else { '(non-user principal)' }
            UPN    = $u.UserPrincipalName
        }
    }
} | Sort-Object Role, Member | Format-Table -AutoSize

Anyone in the first two rows of that output can attach an Azure subscription to a spending policy. Anyone in the third can widen a policy's scope. Both are budget decisions wearing an admin-role costume.

The fix: four things to do before this lands

Step 1 — Disambiguate "Autopilot" in your own documentation

Do this first because it costs nothing and it prevents months of confused tickets.

1. Search your knowledge base, runbooks and ITSM templates for the bare word Autopilot.
2. Replace every instance that refers to device provisioning with Windows Autopilot, written in full.
3. Add a single disambiguation line to your Autopilot landing article: "Windows Autopilot provisions devices. Copilot Autopilot is an unrelated Microsoft 365 agent. This article covers Windows Autopilot only."
4. Tell your service desk before October. The first ticket saying "Autopilot isn't working" that turns out to be about a Teams agent will otherwise get routed to your device team and sit there.

If you run Autopilot device preparation (APDP) alongside classic Windows Autopilot, you now have three similarly-named things in play. Spell all three out in full, every time.

Step 2 — Decide the Auto-apply question deliberately

There is a genuine choice here, and it is not automatically "turn it off".

• Leave it on if the policy is a tightly-scoped pilot group with a hard monthly limit and you want new agents available to them without a change request. That is a reasonable stance for an innovation group.
• Turn it off on any policy scoped to All users, any policy with no monthly limit, and any policy whose billing method is a production Azure subscription. Microsoft's own documentation says it plainly: "Turn off Auto-apply new services for any policy that shouldn't automatically govern future supported services or agents."

To change it on an existing policy: Copilot › Cost Management › Configuration, open the policy, go to the Select agents and services tab, and clear the toggle.

Step 3 — Set a limit before you need one

When you activate a spending policy the wizard offers Don't limit monthly spending and Limit monthly spending. It also offers an optional per-user monthly limit, and Microsoft explicitly recommends setting it "to prevent runaway spending of Copilot Credits by one individual user".

Long-running agents change the risk profile of that optional setting. Autopilot is described by Microsoft as an agent that "keeps working even when you're not" — consumption is no longer bounded by someone sitting at a keyboard. Set the per-user limit.

Two behaviours to know before you design the policy layout:

• Users in multiple policies do not stack. The system picks one policy by highest per-user limit, then largest overall policy limit, then most recently created. The chosen policy "applies in full and settings from other policies aren't combined."
• Moving a user between Entra groups does not reset consumption. Credits consumed under the old policy still count against the new policy's limit for that billing period. This is deliberate, to stop a group move being used as a budget reset.

Step 4 — If you buy via CSP, act before 2 November 2026

1. Confirm with your CSP whether you have M365 Copilot Business purchases planned on or after 2 November 2026.
2. If so, confirm which Azure subscription will be attached, and whether it is one you would have chosen.
3. Ask your CSP to confirm the preset monthly limit that ships with the default configuration — Partner Center tells partners to "familiarize your teams with the upcoming change and the preset monthly limit", so a figure exists.
4. Model expected consumption with the Copilot Credit Estimator before the renewal conversation, not after the first invoice.

Proof it worked

You have four checks, and each has a concrete pass state.

Naming. A search of your knowledge base for the bare word "Autopilot" returns zero results that are not qualified as either Windows Autopilot, Autopilot device preparation, or Copilot Autopilot.

Auto-apply. In Copilot › Cost Management › Configuration, open each policy's Select agents and services tab. Every policy scoped to All users, or with no monthly limit, shows the toggle cleared:

Roles. The PowerShell above returns a list you recognise, with no unexpected principals holding Global Administrator or Billing Administrator.

Consumption. On the Overview tab you can see total credits used and active users. Note the refresh cadence when you are validating: the Overview tab refreshes every 4 hours and the Consumption tab every 2 hours. A change you make now will not be reflected instantly, so do not conclude a policy failed because the dashboard has not moved.

And when Autopilot actually arrives

The signal that this stops being theoretical is Code and Autopilot appearing in the Agents and services view on the Consumption tab, or in the service list on the Select agents and services step. Until they show up there, no amount of announcement coverage means your tenant can consume them.

References

• Introducing the new Copilot with Home, Code and Autopilot — The Official Microsoft Blog, 25 September 2026
• New Microsoft Copilot brings Home, Code and Autopilot together — Microsoft Source EMEA
• Introducing Microsoft Scout: your always-on personal agent — Microsoft AI at Work Blog, 2 June 2026 (the post that named the "Autopilots" category)
• Usage-based billing and cost management for Copilot Credits — Microsoft Learn, revised 10 September 2026
• Managing AI experiences enabled by usage-based billing — Microsoft Learn, revised 10 September 2026
• September 2026 Partner Center announcements — usage-based billing default on from 2 November 2026
• Windows Autopilot known issues — Microsoft Learn, last updated 8 September 2026
• About administrator roles in the Microsoft 365 admin center — Microsoft Learn