The Copilot platform shifted on multiple fronts this week. Microsoft consolidated work around Copilot Home and Projects, GitHub expanded governed agent orchestration, finance teams gained specialized skills, and cloud-backed sessions began moving across applications and devices.

For IT leaders, the signal is clear: the theme this week is governed continuity. Copilot is moving beyond isolated prompts toward persistent work, routed models, connected tools, delegated execution, and policies that follow users across surfaces.

1. Copilot Home — Persistent Work Replaces Chat Silos

Microsoft’s October 2026 Copilot update says Copilot Home will bring Chat and Cowork into a shared experience. Projects will consolidate related chats, files, tasks, meetings, instructions, and generated outputs rather than leaving that context scattered across separate interactions.

Microsoft also says reusable skills are expanding from Cowork into Copilot Chat. Users will be able to create skills with natural language, discover skills shared by colleagues or their organization, and decide when those skills run.

This is not merely a navigation redesign. It is a shift toward reusable organizational context, where instructions and artifacts can persist beyond a single conversation.

Meanwhile, Microsoft says users can create and edit Word, Excel, and PowerPoint files inside Copilot Workspaces. Audio Overview is also gaining topic-based episodes, sensitivity-label support, and additional content types.

What this means for IT leaders: Treat Projects and shared skills as managed workspaces, not personal productivity features. Your rollout plan needs ownership rules for project content, skill publication, sensitivity labels, and lifecycle management before persistent contexts spread across departments.

2. Autopilot — Delegated Work Enters the Governance Queue

Microsoft’s October update says Autopilot, its long-running delegated-work experience, is rolling out to Frontier users in November 2026. Agent 365 is positioned to provide governance, risk assessment, usage visibility, and business-value measurement for these agent activities.

The timing matters. Long-running agents create a different control problem from chat because work can continue after the initiating interaction. Approval boundaries, connected data, and outcome review therefore become operational requirements rather than optional safeguards.

Microsoft also says Agent Mode is becoming the default in Copilot for Word, Excel, and PowerPoint. In parallel, Copilot Chat now offers access to multiple models with automatic routing, according to Microsoft’s fiscal 2026 third-quarter earnings materials.

This is not a collection of isolated assistants. It is an execution layer moving into the productivity suite.

What this means for IT leaders: Use the November Frontier rollout to define delegated-work policies before wider adoption. Your controls should distinguish between interactive assistance, artifact creation, and long-running execution, with separate review requirements for each category.

3. Copilot Fusion — Model Routing Becomes a Managed Layer

The Microsoft Cloud Blog reported that GitHub Copilot Fusion reached general availability with Single, Cascade, and Critique workflows. Administrators and users can select Standard, High, or Max effort levels, while Fusion can coordinate cloud and on-device models across Copilot CLI, the Copilot app, and VS Code.

The same report says GitHub added GPT-6.1 Terra across Copilot and Microsoft Foundry. GitHub positions it as a lower-cost option for routine agentic coding and terminal work, while Foundry supports text and image inputs, the Responses API, and up to 1 million input tokens.

Model choice is becoming an orchestration policy. A single default model is no longer an adequate enterprise strategy when effort levels, routing patterns, cost profiles, and local execution can vary by task.

Enterprise controls are expanding alongside that routing layer. The Microsoft Cloud Blog reported general availability for repository plugin defaults, enterprise plugin policies, approved marketplaces, and managed settings across VS Code, Copilot CLI, and the Copilot app. Managed Fusion configuration is currently Windows-only, according to OurSignal.

What this means for IT leaders: Inventory where model selection is automatic, user-controlled, or centrally managed. Establish approved effort levels and plugin marketplaces by workload, then document the Windows-only management limitation for mixed-device environments.

4. Sessions and Automations — Copilot Crosses Surfaces

AI Agent Store reported that cloud-backed Copilot sessions can persist across the web, mobile, the Copilot app, VS Code, Slack, Teams, and Copilot CLI. The same outlet reported preview connectors for roughly 26 services, including Slack, Figma, Notion, Sentry, Linear, Cloudflare, and Vercel.

Connect-once authorization reduces repeated setup, but it also concentrates access. A persistent session carrying context between collaboration tools, development environments, and terminals creates a broader governance boundary than an IDE-only assistant.

OurSignal reported public previews for Copilot Projects and computer use. Projects can incorporate context from tools such as Slack and Figma, while computer use can interact with approved desktop applications on macOS and Windows with user approval.

Copilot Automations extend the same pattern into cloud workflows. The Agent Daily reported that automations can start manually, on schedules, from events, or through an API. OurSignal also reported shared automations that can continue independently of their creator.

What this means for IT leaders: Review connector authorization, session retention, desktop approvals, and automation ownership as one control plane. Shared automations need service ownership and offboarding procedures so workflows do not become dependent on an individual creator.

5. Finance and Billing — Specialization Meets Cost Control

Microsoft announced more than 25 finance skills and partner plugins on October 29, spanning accounting, capital markets, and broader finance workflows. Microsoft says finance skills in Excel are generally available, while accounting capabilities in Excel and Cowork remain in Frontier.

CFO Dive reported integrations involving QuickBooks, Xero, Zoho Books, FactSet, Morningstar, LSEG, and S&P Global. Microsoft’s October update also lists finance-oriented capabilities for planning, modeling, investment research, and transaction materials.

This specialization changes the adoption case. Finance deployments now require validation against established controls for source data, spreadsheet changes, research provenance, and approval authority.

Cost governance is changing as well. Sherweb reported that new Microsoft 365 Copilot Business purchases are scheduled to enable tenant-level usage-based billing beginning December 1, 2026. That creates a near-term procurement checkpoint for organizations evaluating new purchases.

GitHub Copilot’s command-line experience also retains a practical reliability concern. GitHub issue #5302 reports agents frequently generating invalid PowerShell on Windows and requiring retries. This was a real workflow defect, not a cosmetic inconvenience.

What this means for IT leaders: Separate finance validation from general Copilot adoption, review purchasing plans before December 1, and include Windows PowerShell retry rates in CLI pilots. Usage billing and unreliable command generation can both alter the expected cost of automation.

Strategic Next Steps (for IT Leaders)

  1. Classify execution modes. Separate chat, artifact creation, delegated work, computer use, and cloud automation in your Copilot governance model.
  2. Audit connected context. Record which Projects, sessions, connectors, plugins, and automations can access organizational data.
  3. Set routing policy. Define acceptable models, Fusion effort levels, plugin marketplaces, and local-versus-cloud execution paths.
  4. Prepare for billing changes. Review planned Copilot Business purchases and tenant-level cost controls before December 1, 2026.
  5. Test operational reliability. Validate Windows PowerShell generation, approval flows, shared automation ownership, and offboarding behavior before broad deployment.

The platforms are converging around agents. The controls are diverging by surface, model, connector, and execution mode. IT leaders now need one governance architecture that covers all four.