A man works at a desk with three monitors displaying cloud security, messaging, and team management dashboards.
On September 25, 2026, Microsoft announced a redesigned Copilot app built around three new areas: Home, which combines Chat and Cowork; Code, which builds apps from plain-language descriptions; and Autopilot, a persistent agent. Home and Code will reach Frontier early-access organizations first, and Autopilot moves into private preview at the end of September. Most of the announcement describes previews, not a general release. The biggest practical change for IT is a new billing split: everyday Copilot chat stays on per-user licenses, while the agentic features run on usage-based billing. For administrators, cost control and governance matter more right now than the new tabs.

The announcement, posted on the Official Microsoft Blog by Jared Spataro, Chief Marketing Officer for AI at Work, arrived with a companion post on a new hosting layer called Microsoft Copilot Managed Runtime. Several outlets reported the rollout dates independently, including CNBC, GeekWire, Thurrott.com, Petri and Techzine. Together they show both the scale of Microsoft's plan and how much of it is still a preview.

Copilot Home Folds Chat, Cowork and Office Into One Starting Screen​

Home is the new default landing page in Copilot. From it, users can review recent activity, get suggestions and pick up unfinished work. It holds two modes. Chat handles quick questions, lookups and drafts. Cowork handles delegated, multi-step jobs that Microsoft says run end to end until they return a finished result. Microsoft's examples of delegated work include an RFP response, a launch kit, or a financial closing.

Microsoft also promises that users will soon stop choosing a mode at all: Copilot will send each request to Chat, Cowork or Code on its own. Techzine was skeptical and called automatic routing "a promise that sounds as ambitious as it is error-prone." Microsoft gave no date for it, so admins shouldn't plan around it yet.

The bigger change inside Home is Office in Copilot. Microsoft says users can ask Copilot to draft a brief, model a budget, build a deck, or open a file the team is already working on. The result is a real, editable Word document, Excel workbook or PowerPoint presentation that stays live for the whole team. GeekWire watched a demo: a Microsoft product manager had Copilot pull data into an Excel workbook, accepted her team's tracked changes in a Word document, and then had Copilot turn both into a PowerPoint deck without leaving the app. Microsoft also says co-workers can edit the same files at the same time from the regular Office apps.

The timing for Office in Copilot differs from the other features. GeekWire reports that Office in Copilot will roll out to consumers and Frontier customers in the coming weeks, which suggests it will reach consumers as well as businesses. Thurrott.com describes the new app as building on the old one, which will also keep the existing Office features of the previous Microsoft 365 Copilot app. Microsoft hasn't said which Office client versions, file types or license plans are included in the first wave.

Some improvements also land inside the Office apps themselves. PowerPoint can keep decks on-brand automatically, fine-tune slides and images, and apply a custom template. Excel shows what Copilot or a collaborator changed and why, and it recommends charts. Microsoft also describes Skills: reusable, role-specific expertise inside Microsoft 365 apps. Its examples are financial skills in Excel and legal skills in Word. Microsoft didn't publish availability details for these Office changes.

Copilot Code Turns App-Building Into an Office Task and Leaves GitHub Copilot to Developers​

Code is aimed at people who don't write software. Microsoft argues that knowledge work has always been organized around documents, spreadsheets and decks, and that small, purpose-built apps are becoming a fourth format. Users describe an app, tracker, dashboard, automation or workflow in plain language, and Copilot picks an approach and builds it. Results can range from desktop widgets and interactive dashboards to cloud-hosted internal apps shared with a team.

Petri confirms the technical basics: Code, which is powered by the same core technology used in GitHub Copilot, runs in a sandboxed environment and can be hosted within a customer's Microsoft 365 tenant. Microsoft says what users build is grounded in their work context through Microsoft IQ, its name for the enterprise context layer behind Copilot, and that plugins sync automatically. Several outlets treat Code as Microsoft's competitor to other companies' AI coding tools. Tom's Hardware says Code is an answer to ChatGPT's Codex and Anthropic's Claude Code.

Microsoft says professional developers keep using GitHub Copilot for daily work, with closer links to the wider Copilot platform. Thurrott.com adds that tasks started in Code will also sync with the standalone GitHub Copilot service. That means a business user's prototype can be handed to a developer without starting over.

Code's timing is inconsistent in Microsoft's own post. The summary says Home and Code begin rolling out to Frontier "in the coming weeks." The Code section says it arrives in Frontier at the end of the month, with broad availability in the coming weeks after that. Consumers get a separate track: Code will also be in preview for Microsoft 365 Premium and Pro subscribers later this year.

Copilot Managed Runtime Is the Governance Story Behind Code​

If anyone can build an app, IT needs a way to see and control those apps. Microsoft's answer is Copilot Managed Runtime, and it may matter more to administrators than Code itself. The companion blog post, by David Blyth, Vice President and General Manager for Managed Apps and Agents, says the runtime entered public preview on September 25. It describes a platform for running code inside the Microsoft 365 tenant boundary, governed by IT. This hosting solution allows Code to run securely within an organization's Microsoft 365 environment, under IT management, as Techzine summarized.

According to Microsoft, apps deployed to the runtime get:

  • Microsoft Entra identity and sharing, so sign-in and access follow existing tenant identities.
  • Organizational policies that control which connectors, data sources and approved endpoints an app can use, with auditing.
  • Automatic versioning and source control through Git, so a new version can be previewed while the current one stays available to users.
  • A central inventory in a new Apps experience in the Microsoft 365 admin center, where admins can review access, usage, health and policy.
  • Admin controls to enable or disable apps and review default policies in that same Apps experience.

The runtime is shared across Microsoft's app-building tools. It already hosts apps built in Copilot Cowork, Copilot Code and Copilot Studio, and Microsoft is opening it to third-party tools through an SDK and command-line interface. Those tools cover project scaffolding, data-connection definitions, typed TypeScript services for connectors, local previews, deployment and versioning. Lovable is the named example: its head of global partnerships says an app built with Lovable can now run inside a Microsoft tenant with the same sign-in, policies and app inventory as everything else.

For IT, this means one place to govern apps no matter which tool built them. Microsoft hasn't published details on sandbox isolation, data retention, or the full list of supported data sources. Until it does, admins should treat Microsoft's security description as a vendor claim to test in a pilot, not something already proven.

Autopilot Gives Scout an Identity, a Computer and a Standing Assignment​

Autopilot is the new name for Scout. The Frontier program page still lists Scout as a desktop app that monitors priorities and moves work forward across Microsoft 365 apps. In the new design, a user gives the agent a name, a role and a goal. It then watches channels, follows up on threads, runs recurring work and returns to projects days later without being prompted. Microsoft's example is running a full supplier review: building the schedule and workback plan, then handling prep, meetings, follow-ups and requests to stakeholders for updates.

Two outlets report what Scout is built on. Techzine writes that Autopilot was previously called Scout, an agent based on the open-source project OpenClaw. Thurrott.com also describes Scout as Microsoft's new personal work agent powered by OpenClaw. Microsoft's own announcement doesn't mention OpenClaw.

For security teams, the architecture is the important part. Microsoft says each Autopilot instance lives in the tenant with its own identity, memory, computer and workspace. It's cloud-hosted, so it keeps working when the user is offline. People can @mention it in Teams, Outlook, chats, channels and documents, like a colleague. Petri describes it as running while remaining subject to organizational permissions and governance controls.

An agent with its own identity that acts without a prompt and contacts stakeholders by itself is a new kind of account for identity and audit teams. Microsoft says permissions, audit and governance apply, and that users set the goal and the limits. It hasn't said how those limits are configured, what approval steps exist before the agent sends messages, or how its activity appears in audit logs. Autopilot is only entering private preview, so those details should come out through the preview before any wider release.


Usage-Based Billing Splits Copilot Pricing in Two​

The pricing change affects every Copilot customer, including those who never open the new tabs. Microsoft now separates two ways of paying. A user subscription license (USL) covers what Microsoft calls everyday AI: Copilot in Chat and in Word, Excel, PowerPoint, Outlook and Teams, plus model selection and new models. The license is built around Auto, which picks a model for each request based on accuracy, speed and cost.

Agentic work is billed separately. Microsoft says Cowork, Code, Autopilot, other long-running agentic features, and frontier models such as Astra and Fable all run on usage-based billing (UBB). CNBC notes the contrast with Microsoft's usual approach: rather than charging for subscriptions like it does for most of its software — the commercial Microsoft 365 Copilot costs $30 per user per month — Microsoft says clients will pay for the Cowork, Code and Autopilot portions of the new app based on usage.

Microsoft's product leadership has also signaled its priorities. Jacob Andreou, Microsoft's executive vice president for Copilot, told CNBC that "this product is at its best when it's just optimizing for user value and for the quality of the output and what it's able to deliver." Cost efficiency is less important, he said. Microsoft is optimizing these features for output quality, not cost, so budget control falls to the customer. The announcement gives no per-task prices or credit rates.

Microsoft's answer is a set of FinOps for AI tools in Agent 365, its agent management layer. Cost management already covered Cowork and the Work IQ APIs, and it now extends to Code and Copilot Managed Runtime. Support for agents built in Copilot Studio is planned for October. Admins can:

  • Manage spending policies at scale through an API.
  • Send end users' credit requests into existing approval and automation workflows.
  • Choose which model families each group of users can access. Those limits also restrict which models Auto can pick.
  • See which Cowork tasks produce the best results, so they know where to expand or cut back usage.

End users will see their credit usage, remaining balance and usage history directly in Copilot.

Fabric IQ, Dynamics 365 Grounding and a Plugin Registry Expand What Copilot Can Reach​

Copilot's access to business data is also expanding, and here the release status varies. Fabric IQ, which brings in data context including what Microsoft counts as more than 20 million Power BI semantic models, is generally available today in Chat and Cowork. Code support for Fabric IQ is coming through Frontier. Grounding in Dynamics 365 and Power Platform data and workflows is rolling out in public preview over the next month. Microsoft's example is a salesperson whose proposal pulls in deal history and support tickets. Microsoft hasn't said which Dynamics 365 workloads are included or what setup they need.

A new plugin registry is rolling out now and should be generally available across supported Copilot surfaces in the coming weeks. It puts Microsoft, partner and custom plugins in one catalog. IT approves and manages plugins centrally, and developers publish once to reach every supported Copilot surface. Microsoft hasn't listed which surfaces count as supported.

Two more features come after this wave. Today is a personalized overview in Home covering mail, calendar, Teams threads, meetings and tasks, with drafts, schedule changes and follow-ups prepared in advance. It enters private preview in October and will later come to Outlook and Teams. A team version of @Copilot in Teams, which uses the shared context and permissions of a channel, group chat or meeting, is due in private preview by the end of September.

What this means for you​

Most organizations can wait on the new tabs but should start setting cost and governance policy now. Everything announced except Fabric IQ in Chat and Cowork is a Frontier, private preview or public preview release. Frontier also has conditions. For business users, Microsoft requires a Microsoft 365 Copilot license, an organization that has opted in, and a work-account sign-in. Admins turn on Frontier in the Microsoft 365 admin center, assign eligible users, and decide how usage-based billing and Copilot Credits apply. Separately, Microsoft 365 Pro, Premium, Personal and Family subscribers can opt in through Copilot Settings in Word, Excel or PowerPoint on the web by turning on "Preview Frontier features."

If your tenant is already in Frontier, UBB exposure is the setting that needs attention first, because Cowork, Code and Autopilot all bill by usage. Microsoft's Frontier page also notes that if Cowork doesn't appear in Agent management in the admin center, the admin account itself must be enrolled in Frontier through Copilot settings.

  • Check whether your tenant is enrolled in Frontier before Home and Code arrive, and limit access to a pilot group if billing policies aren't ready.
  • Set model-family restrictions and spending policies in Agent 365 before users try Code or Autopilot, because those restrictions also limit what Auto can choose.
  • Review the new Apps experience in the Microsoft 365 admin center, including its default policies, because apps built in Cowork, Code and Copilot Studio will show up there.
  • Treat each Autopilot instance as its own identity when planning permissions and audits, and ask how its outbound messages are approved during the private preview.
  • Expect Fabric IQ grounding in Chat and Cowork today, but treat Dynamics 365 and Power Platform grounding as public preview arriving over the next month.

Microsoft is using this redesign to move Copilot from a per-seat assistant to a platform that builds apps, runs agents and bills by usage. Copilot Managed Runtime and the Agent 365 cost controls are the pieces that determine whether IT can keep that manageable. The next checkpoints are close together: Autopilot and team @Copilot previews by the end of September, Today and Copilot Studio cost management in October, and more detail expected at Microsoft Ignite, November 17–20 in San Francisco and online. Administrators should arrive at Ignite with pilot data on what Cowork and Code actually cost their users.


Update: Additional details (September 25, 2026)​

GeekWire reports that usage-based services are off by default. Administrators can set spending limits for the whole organization, groups, or individual users through Agent 365.

It also says each Autopilot has its own email address as well as its own identity and memory inside the Microsoft 365 environment.