Microsoft Copilot Home, Code and Autopilot (25 Sep 2026): Buyer Checklist for the New Copilot App

September 28, 2026 admin

Verdict: On 25 September 2026, Microsoft introduced a reworked Copilot experience built around three capabilities: Home (Chat + Cowork + Office in Copilot), Code (natural-language apps/automations on GitHub Copilot tech with Managed Runtime), and Autopilot (persistent agent formerly called Scout). Home and Code start in the Frontier program; Autopilot expands to private preview near month-end. For Microsoft 365 buyers, treat this as a licensing and FinOps checklist — not a free feature dump.

Best for: IT and AI leads already standardizing on Microsoft 365 Copilot who need a rollout plan for agentic work.
Not for: Teams without M365 Copilot eligibility chasing a consumer chatbot SKU.

Based on Microsoft’s official blog dated 25 Sep 2026 — Frontier/private-preview gates, USL vs usage-based billing, and regional availability can change. Confirm live in your admin center and contract.

What shipped

Home becomes the starting point where Chat (quick turns) and Cowork (delegated end-to-end tasks) meet, with Word/Excel/PowerPoint documents created and edited inside Copilot and kept in sync with Office apps. Code lets non-developers describe widgets, dashboards, and internal apps that run in a sandboxed Microsoft Copilot Managed Runtime inside the tenant. Autopilot is a named, goal-driven agent with its own identity/memory that keeps working in Teams/Outlook without constant prompts. Fabric IQ / Dynamics / Power Platform grounding and a unified plugin registry are part of the same wave. Read the source post: 25 Sep 2026 Microsoft Blog.

Buyer checklist

1. Map entitlement — confirm which users are on Microsoft 365 Copilot / Premium / Pro SKUs that actually receive Frontier or preview bits.
2. Separate USL vs UBB — blog frames everyday Chat/Office Copilot on user subscription licenses, while Cowork, Code, Autopilot and frontier models run on usage-based billing; model both lines.
3. Turn on FinOps early — Agent 365 cost controls, credit approvals, and end-user usage visibility are called out; set budgets before Autopilot fan-out.
4. Pilot Home on one department — validate Office-in-Copilot sync and sharing before org-wide muscle memory shifts.
5. Scope Code + Managed Runtime — decide who may publish tenant apps; involve security for sandbox and data access reviews.
6. Autopilot permissions — treat it like a service account: least privilege, audit, clear human owners.
7. Plugin registry governance — IT approval workflow for Microsoft/partner/custom plugins.
8. Calendar Ignite follow-ups — Microsoft points to Ignite (17–20 Nov 2026) for more; do not freeze architecture before then if you can wait.

Strengths

Unifies chat, delegated work, building, and persistent agents in one Copilot app story.
Office-in-Copilot reduces copy/paste between chat and real files.
Explicit FinOps messaging acknowledges agentic spend risk.
Tenant-hosted runtime keeps Code closer to enterprise controls.

Limits

Frontier/private preview timing means uneven seat availability.
Usage-based agent features can blow budgets without guardrails.
Not a replacement for GitHub Copilot developer workflows — those continue in parallel.
Third-party meeting-note tools still compete outside the Microsoft graph.

Who should act

M365 Copilot customers should stand up a joint IT/FinOps pilot this month: Home for knowledge workers, Code for one internal tool, Autopilot for one recurring process with tight permissions. Orgs without Copilot licenses should wait — this announcement does not create a free Autopilot tier.

Bottom line

Best next step is entitlement + FinOps readiness, then a narrow Frontier pilot of Home/Code before Autopilot scale. Confirm live SKU access and usage-billing policies — and keep a human owner on every agent identity. Versus bolting on three separate startups, Microsoft’s bet is one governed surface; the price of that bet is disciplined credit control.