Cowork Moves Into the Mainstream — and Into Your Analytics
Copilot Cowork is now a first-class part of the Microsoft 365 Copilot app. Per the September 23 release notes, users switch from Chat to Cowork, describe an outcome, and Cowork gathers context from email, meetings, chats, files, and business data, works across tools, and returns finished results. Multi-step actions still require user approval, and everything runs under existing Microsoft 365 security, privacy, and compliance controls. Cowork sits next to Chat on the new Home screen, and Microsoft says Copilot will soon route requests between Chat, Cowork, and Code automatically.
The October 6 release added the measurement layer admins have been asking for: Copilot Analytics now reports Cowork adoption and impact metrics in the Copilot dashboard and the Consumption dashboard, with export. Analysts also get new Consumption and Person queries in advanced insights. Together these let you see who is delegating work, how much it costs, and whether it pays off.
Cowork entry points become visible to licensed users by default in October for standard-release tenants and November for deferred tenants. Expect questions from users before you have a policy in place.
What to do: Open the Copilot dashboard this week, baseline Cowork usage, and decide whether to pilot with a named group before the entry point appears for everyone.
Usage-Based Billing and Spending Policies Arrive
The biggest operational change is financial. Microsoft is splitting Copilot into two billing tracks: "everyday AI" stays under the per-user Copilot license, while advanced and agentic work — Cowork, Code, Autopilot, frontier models, and advanced SharePoint and OneDrive capabilities — runs on usage-based Copilot Credits. Rollout of usage-based billing begins in Q4 2026.
Critically, nothing billed on credits works in a tenant until an admin creates a spending policy (Microsoft 365 admin center, Copilot, Cost management). Entry points are visible to everyone, but they consume nothing until a policy exists. The new FinOps for AI preview adds a dashboard, API-managed spending policies, approval routing, and the ability to assign model families and effort levels by user group. Copilot Studio agents join the FinOps scope in October.
A related setting — a "Request access / Learn more" experience for users who hit a credit-gated feature — arrives for standard customers in October and deferred customers in November. Set your default before it rolls out.
What to do: Create a conservative default spending policy now, then widen it by group as you see real consumption data.
Federated Connectors, Outlook Triage, and Planner Agent Go GA
On September 23, federated Copilot connectors reached general availability. They use the Model Context Protocol (MCP) to retrieve third-party data in real time under the user's own identity, without storing or indexing customer data. They are supported in Researcher, Microsoft 365 Chat, and Copilot in Excel. On October 6, admins also gained the ability to edit query string and user identity mapping rules on existing connectors without opening a support ticket.
Other agentic additions in the same window include expanded Outlook triage actions (delete, move, copy, categorize, and manage rules and folders in natural language, with confirmation before acting on more than five emails or changing inbox rules), a Planner Agent chat for task discovery and in-plan updates, declarative agents in classic Outlook for Windows, and Vision in Copilot for analyzing shared screens and live camera feeds during voice sessions.
Copilot Search and Chat also merged: Chat now runs directly from Search results for follow-up questions. In PowerPoint, Windows users can create custom skills, and Mac users can reference SharePoint and OneDrive files by name when building decks.
What to do: Inventory which third-party systems your teams use most, and pilot one federated MCP connector with a small group — paying attention to how user-identity permissions behave.
Autopilot, Code, and Managed Runtime: What's Next
Last week's redesign continues to roll out. Autopilot (formerly Scout) is a persistent, proactive agent with its own directory identity, memory, and cloud workspace that keeps working while you are away. It remains in private preview, expanding, and requires a Microsoft 365 Copilot license. Code is reaching Frontier customers with broader availability in the coming weeks, letting business users describe apps and automations built in a sandbox.
Copilot Managed Runtime, in public preview, is Microsoft-operated hosting for apps built in Code, Cowork, and Copilot Studio, with Entra sign-in and organizational policies controlling which connectors, data, and endpoints those apps can reach. Microsoft also says "Today," a proactive command center, and @Copilot in Teams are entering private preview.
Because Autopilot agents get their own identity, they should be governed like employees: scoped access, owners, and review cycles.
What to do: Draft an identity and access policy for agent identities before Autopilot reaches your tenant, and decide who may build and publish apps on Managed Runtime.
Copilot Studio and SharePoint Housekeeping
In Copilot Studio, app- and intent-first agent creation begins rolling out in October: makers choose the application first, then configure capabilities. Makers also get a cost breakdown for evaluation generation, test runs, and model grading, now generally available and reaching tenants through October. No admin configuration is required, but the visibility helps makers budget credit usage.
Separately, Copilot in SharePoint and OneDrive reaches general availability from late September, phasing into tenants afterward. Everyday capabilities stay on the standard license while agentic, at-scale work moves to credits. Existing PowerShell opt-outs for the SharePoint Copilot preview are honored only until November 1, 2026; after that they must be managed through SharePoint site AI settings. A new SharePoint Advanced Management report also shows item-level permissions for the "Everyone" and "Everyone except external users" groups — valuable oversharing hygiene before agents start reading more content.
What to do: Migrate any SharePoint Copilot opt-outs to site AI settings before November 1, and run the new Everyone-permissions report to find oversharing.