One Copilot, three ways to work: what Microsoft's new Copilot means for your organisation

Today Microsoft introduced the new Copilot, reorganised around three tabs: Home (Chat and Cowork), Code and Autopilots (Scout). It completes a consolidation that has been visible for months. Over the summer, Microsoft began folding its consumer and Microsoft 365 Copilot apps into a single app with one name, one icon and one web address. Today's announcement shows what that single app is for.

Microsoft sums up the change in one line: ‘Copilot is moving from helping individuals complete tasks to enabling organisations to build, run and govern AI-powered business processes’. For leaders who have spent the past two years trying to turn Copilot licences into measurable outcomes, that shift matters.

What's new?

Home brings together the ways people already work with Copilot. Chat is there to assist, Cowork takes on delegated multi-step tasks, and the Office apps are there to create, refine and collaborate. The chat window, the agent and the document, now sit in one place instead of across separate tools.

Autopilot is for automation. It lets people discover, configure and manage always-on, cloud-based agents. Each agent has its own identity and tool access and completes work end to end without being prompted every time. Microsoft's first-party Autopilot, formerly known as Scout, uses Microsoft 365 tools and Work IQ to keep work moving in the background, and is available through the Frontier programme.

Code is for building. Copilot Code turns natural language and organisational context into apps, dashboards and automations, so information workers can create software, not just developers. It complements GitHub Copilot, which stays focused on professional, repository-based development.

The platform underneath

The three tabs are the visible part. The platform changes underneath is what will decide whether organisations can use them at scale.

Work IQ: the intelligence layer that helps Copilot understand people, roles, projects and priorities. It now extends beyond Microsoft 365 to include Dynamics 365 and Power Platform data and workflows. Copilot and agents can therefore draw on the systems where business processes actually run, not just email and documents. The result should be richer, more contextual responses. Work IQ's expanded data sources are in public preview.

Copilot Managed Runtime: gives AI-built apps from Cowork, Code and Copilot Studio, Microsoft-managed hosting, identity, sharing, governance and lifecycle controls. This addresses a problem every organisation experimenting with AI-generated apps will recognise - a useful prototype has nowhere safe to live. Managed Runtime is also in public preview.

Plugin Registry: gives organisations one place to discover and govern the plugins that extend Copilot. This matters more as the number of agents and integrations grows.

A different commercial model

Microsoft is also changing how Copilot is paid for and controlled. Copilot Code, Autopilot and the Managed Runtime all use usage-based billing. This continues a direction set earlier this year, when usage-based Copilot Credits billing became mandatory across all workflows on 1 July 2026 for Cowork.

To support this, FinOps for AI (in public preview) gives administrators more visibility, governance and cost control across Code, Autopilot and Managed Runtime hosting, including model access controls. For finance and IT teams, this means AI spend can be managed like cloud spend, with budgets, reports and guardrails rather than surprises at the end of the month.

What this means for organisations

The biggest change is the unit of value. Until now, most organisations have measured Copilot by seat: who has a licence, and how often they use it. The new Copilot invites a different question - which business processes can AI run, and how do we govern them?

This change helps organisations in four ways:

1. Less sprawl: one app with one entry point replaces a growing collection of assistants, agents and tools, which makes adoption, training and support simpler.
2. Faster route from idea to working solution: someone in finance, HR or operations can describe a need in Code or Cowork, and IT can host and govern the result through the Managed Runtime.
3. Work that continues in the background: Autopilots handle follow-through, coordination and routine process steps continuously, within permissions administrators set.
4. Control built in: Agent identities, lifecycle controls, a plugin registry and AI FinOps give IT, security and finance the levers they need before scaling up.

What to do now

Organisations that benefit first will have done some groundwork:

Data: Work IQ can only reason over what it can reach and what users are permitted to see, so permissions hygiene across SharePoint, Teams and increasingly, Dynamics 365 and Power Platform is now a prerequisite.

Identity: Autopilots act under their own identities, so agent governance belongs in your identity strategy, not as an afterthought.

Costs: before usage-based services scale, set budgets, owners and reporting through FinOps for AI.

Pilots: Pick two or three well-understood business processes, one each for Cowork, Autopilot and Code, and measure outcomes rather than activity.

The new Copilot is Microsoft's clearest statement yet of where workplace AI is heading. The question for most organisations is no longer whether to adopt Copilot, but which processes to hand it and how to keep them under control.

Explore what the new Copilot could mean for your business. Speak to your Softcat Account Manager about where to start, what to prioritise, and how to scale AI safely across your organisation.