Microsoft did not ship another Chat skin. It shipped a teammate SKU with a different bill.
On September 25, 2026, Jared Spataro’s official Microsoft Blog introduced the new Copilot with three capabilities: Home, Code, and Autopilot. Home is the starting point where Chat and Cowork sit together, with Office in Copilot bringing Word, Excel, and PowerPoint into that surface. Code lets people describe apps, trackers, dashboards, and workflows in natural language, then run them in a sandboxed tenant environment powered by the same underlying technology as GitHub Copilot, with Microsoft Copilot Managed Runtime as the hosting layer. Autopilot, previously called Scout, is the persistent, proactive, personal agent: own identity, memory, computer, and workspace inside the tenant, visible in Teams, Outlook, chats, channels, and documents, cloud-hosted so it keeps working when you are away.
The Verge’s Tom Warren, CNBC’s Jordan Novet, and Windows Central’s Daniel Rubino all filed the same day on the three-tab split, the Scout rename, and the usage-based bill for Cowork, Code, and Autopilot. This is a primary-source review, not a hands-on test, and Frontier and private preview limits are real. The wrong read is “try Copilot again.” The right read is role, goal, permissions, and a spend fence before anyone @mentions a digital teammate in a customer channel.
What it is
Autopilot is the product Microsoft is selling as a digital teammate. Spataro’s blog: give it a name, a role, and a goal, and it goes to work. Watching channels, following up on threads, running recurring work, picking a project back up days later without waiting for a prompt. The supplier-review example is the operator metaphor: schedule and workback plan, prep, meetings, follow-ups, stakeholder outreach for updates. It lives in the tenant with its own identity, memory, computer, and workspace, grounded in Microsoft IQ, with permissions, audit, and governance behind @mentions the way a colleague would appear.
Home is not Autopilot. Home is Chat for instant work plus Cowork for delegated end-to-end tasks (RFP response, launch kit, customer briefing), plus Office in Copilot so drafts land as real editable Word, Excel, and PowerPoint artifacts synced with the Office apps. Coming soon, Microsoft says Copilot will route the job to Chat, Cowork, or Code without a mode picker.
Code is not Autopilot either. Describe an app, tracker, dashboard, or workflow; Copilot builds it on GitHub Copilot tech; Managed Runtime hosts it in the tenant under IT governance. Spataro: Code to Frontier at month end, broader availability in coming weeks, Premium/Pro preview later this year. Managed Runtime is already in preview inside Code.
The Scout lineage matters for operators who already wrote June tickets. Omar Shahine’s June 2, 2026 Copilot blog introduced Autopilots as a category of always-on agents with their own identity, and Microsoft Scout as the first Autopilot agent, with governed Entra identity, desktop reach, and Frontier / private preview gates. September 25 renames that Scout product Autopilot and parks it as a first-class tab beside Home and Code. Category language from June became the SKU name in September. Do not inventory Scout and Autopilot as two purchases.
What changed
Three surfaces, one app. Warren restates the tabs: Home, Code, Autopilot. Nadella’s “OS for work” line and Spataro’s Office comparison are the marketing ceiling. Operators should ignore the ceiling and read the SKU split.
USL versus UBB is the pricing architecture. Spataro: everyday AI (quick answers, drafts, summaries, analysis) rides a user subscription license covering Copilot in Chat and across Word, Excel, PowerPoint, Outlook, and Teams, plus model selection, with Auto routing for accuracy, speed, and cost. Agentic work and frontier models (Astra, Fable named in the blog) ride usage-based billing. Cowork, Code, and Autopilot are explicitly on UBB. Microsoft Learn’s USL/UBB page (accessed September 28) matches: UBB experiences consume Copilot Credits and require a USL for access. Admins must set up a billing policy before users can use UBB experiences.
FinOps for AI moves into the admin center. Spataro: Agent 365 cost management expands beyond Cowork and Work IQ APIs to Code and Managed Runtime, with Copilot Studio agents planned for October. Admins get spending policies with API access, credit-request routing into approval workflows, and model-family controls that also shape Auto. Leaders can see which Cowork tasks drive outcomes. Users can view credit usage and balances in Copilot. Learn’s Cost Management docs cover org and per-user limits, alerts, capacity packs, pay-as-you-go, P3 pre-purchase, custom approval routing, and monitoring by policy, group, user, agent, and service.
Rollout is staggered, not GA theater. Spataro and Verge agree: Home and Code start in Frontier in the coming weeks; Autopilot expands to private preview at month end. Code Premium/Pro preview later this year. Today (proactive Home command center) enters private preview in October. @Copilot in Teams with shared channel context is private preview by end of month. If your plan assumes Monday morning GA for every marketer, rewrite it.
Context and plugins expand under Microsoft IQ. Fabric IQ grounds Chat and Cowork in Power BI semantic models (GA; Code via Frontier soon). Dynamics 365 and Power Platform grounding rolls in public preview over the next month. A plugin registry for Microsoft, partner, and custom plugins rolls now, IT-approved, with broader GA in coming weeks.
What works
A clean operator contract for Autopilot. Name, role, goal, boundaries, @mention surface, tenant identity, audit. That is an access-control and RACI worksheet, not a prompt library. Teams that already staffed agent identity reviews for other vendors can reuse the checklist.
Cloud-hosted persistence is the product difference versus a Chat tab. Spataro and Warren both stress that Autopilot keeps running while you sleep. Recurring supplier reviews and follow-up loops are the use cases that make that claim operationally meaningful. Chat stops when you stop. Autopilot is sold as the thing that does not.
USL / UBB split forces an honest budget conversation. CNBC notes commercial Microsoft 365 Copilot at $30 per user per month as the subscription backdrop, and that Cowork, Code, and Autopilot portions bill on usage. Learn and the September 2026 Copilot Credits Guide put a stick on PAYG: $0.01 per Copilot Credit, credits pooled at tenant level, P3 prepaid tiers with discounts. Everyday Chat and Office stay on the seat. Long-running agents do not hide inside that seat.
FinOps controls exist before Autopilot scales. Spending policies, per-user caps, alerts, credit request routing (including external workflows like ServiceNow), and Auto-apply toggles for new services are documented in Learn. That is enough to build a fence before Frontier users invent one.
Office in Copilot closes the export tax for Home work. Real editable Office artifacts synced with the apps cut version sprawl. That benefit belongs to Home, not Autopilot. Keep the tickets separate.
What breaks
Frontier and private preview are not production. Autopilot end-of-month private preview and Home/Code Frontier timing mean most Microsoft 365 orgs do not have a stable GA Autopilot seat this week. Pilots need named preview tenants, not a company-wide enablement blast.
No billing policy, no UBB. Learn is blunt: admins must set up a billing policy before users can use AI experiences that require usage-based billing. Turning on Autopilot curiosity without Cost Management setup produces blocked users and Slack threads, not digital teammates.
UBB without a per-user fence is a runaway credit story. Learn recommends monthly per-user limits so one person cannot burn the tenant pool. Autopilot is designed to keep working when you are away. That is also how credits keep burning when you are away. Recurring goals without kill criteria are a FinOps incident waiting for a calendar invite.
Identity without a role map is a coworker with a login and no homework. Giving an agent a login is an access-control decision. Autopilot makes that demand inside Microsoft 365: Entra-visible actor, permissions, audit, human sign-off for sensitive actions (Scout’s June enterprise framing). If security has not approved an agent identity pattern, Autopilot is not a marketing experiment. It is a directory change.
Home / Code / Autopilot collapse kills procurement. Buying “more Copilot” as one line item funds Chat seats, Code sandboxes, and always-on agents from one mental budget. USL and UBB will disagree with that spreadsheet. CNBC’s Andreou line that cost efficiency matters less than output quality is a vendor preference, not your CFO’s.
Evidence limits. No hands-on Autopilot run for this review. No Autopilot-only rate card in the pages verified here. Cowork credit buckets (models, runtime, context, tools) in the Credits Guide are the closest public planning language. Treat Autopilot spend as estimate-plus-fence until Microsoft publishes Autopilot-specific estimators.
Who it is for
Primary: Microsoft 365 Copilot customers (USL in place) with Frontier or private-preview access, a security team willing to govern agent identities, and a FinOps or IT owner who can stand up Copilot Credits spending policies before marketing or ops @mentions an Autopilot in a live channel.
Secondary: GTM, marketing ops, and agency leads who own recurring coordination (launch workbacks, partner reviews, briefing packs) and need a teammate pattern, not another Chat prompt pack.
Not the buyer this week: Orgs without a Copilot USL, Cost Management admin rights, or preview access. Also not buyers whose brief is “make Chat smarter” or “replace GitHub Copilot for developers.” Code is a knowledge-worker sandbox. Developers keep GitHub Copilot for day-to-day engineering, per Spataro.
Pricing and limits (documented)
| Lane | What it covers (documented) | Bill shape |
|---|---|---|
| USL | Chat; Copilot across Word, Excel, PowerPoint, Outlook, Teams; Auto model routing; some models with fair use / limits | Fixed per-user subscription |
| UBB | Cowork, Code, Autopilot; new long-running agentic capabilities; frontier models (Astra, Fable named) | Copilot Credits; USL still required for access |
| Credits meter | PAYG listed at $0.01 per Copilot Credit; tenant-pooled; P3 prepaid tiers with volume discounts | Azure / admin-center governed |
| Admin gate | Billing / spending policy required before UBB experiences work | Cost Management in Microsoft 365 admin center |
| Rollout | Home/Code: Frontier coming weeks; Autopilot: private preview end of month; Code Premium/Pro preview later this year | Preview, not broad GA |
CNBC’s $30 per user per month commercial Copilot figure is the subscription context reporters used on September 25. Confirm current list with your account team. Do not invent an Autopilot monthly sticker from this review.
What to do this week
- Label the SKU in the roadmap. Write Autopilot (formerly Scout), persistent teammate, UBB. Do not file it under Chat refresh. Keep Home (Chat + Cowork + Office in Copilot) and Code on separate lines.
- Confirm entitlement before demos. USL assigned? Frontier or Autopilot private-preview path named? Billing policy active in Cost Management? If any answer is no, stop the screen recording.
- Stand up the spend fence first. Create or tighten a spending policy that covers Cowork, Code, and Autopilot (including any new agentic service Auto-apply would pull in). Set a monthly policy limit and a per-user limit. Turn on threshold alerts. Decide whether Auto-apply new services stays on for agentic SKUs.
- Write the role card before the name. One Autopilot only: role, goal, systems it may touch, channels it may post in, human approval gates, kill criteria, owner. Supplier-review style work is fine. Customer-facing send without approval is not a week-one test.
- Route credit requests into a real workflow. Learn supports custom request policies that redirect into internal portals or ServiceNow. Marketing should not approve its own runaway credits in a side DM.
- Brief security on identity. Autopilot is an Entra-visible actor with memory and a computer. Reuse your agent identity checklist: who provisions, what it can touch, how you revoke, what audit looks like in a QBR.
- Separate Cowork pilots from Autopilot pilots. Cowork is delegated task completion on UBB. Autopilot is persistent proactive presence on UBB. Same credit pool, different operating model. One pilot owner each.
- Tell GTM what changes this week. The marketer move inside Microsoft 365 orgs is not a new Chat prompt pack. It is deciding which recurring launch or partner workflow deserves a named teammate with a credit budget, and which work stays on USL Chat and Office in Copilot until Autopilot leaves private preview.
Autopilot is not a tab you casually open after lunch. It is a persistent teammate SKU with its own identity and a usage-based bill. Staff the role, the permissions, and the spend fence, or you will staff it like Chat and discover the invoice first.
