Microsoft has just announced a structural overhaul of Copilot, built around three new capabilities — Home, Code and Autopilot — accompanied by a new billing model and FinOps for AI features. For IT teams, this evolution goes beyond a new interface: it changes how licenses are consumed, how agents run in the tenant, and how AI spending must be managed. This article details what changes concretely, with announced availability dates and governance considerations.
Home: Chat, Cowork and Office united in a single entry point
Home becomes the new home screen of the Copilot application. It brings together Chat — for instant exchanges, quick questions and drafts — and Cowork, designed for delegated work: you define a complex task (RFP response, launch kit, financial close) and the agent executes it end-to-end to produce an actionable result. Microsoft announces that eventually, users won't need to choose a mode: they'll simply describe the objective, and Copilot will automatically route the request to Chat, Cowork or Code based on the nature of the work.

Notable new feature: Office in Copilot integrates Word, Excel and PowerPoint directly into the Home experience. A draft request, budget modeling or deck generation creates a real, editable document, shared with the team — not an isolated copy to recreate elsewhere. Changes remain synchronized between Copilot and Office applications, even when a colleague is @mentioned in the conversation. Microsoft takes the opportunity to highlight recent improvements to Office apps: automatic brand consistency in PowerPoint, change traceability in Excel with visualization recommendations, and Skills — packaged business competencies (finance in Excel, legal in Word) that industrialize reusable workflows by role.
Code: build business solutions without being a developer
Code opens the creation of small applications, dashboards, automations or workflows to any employee, starting from a simple natural language description. Copilot chooses the appropriate approach itself: persistent desktop widget, interactive dashboard, or cloud-hosted application shareable with the team.

Code relies on the same underlying technology as GitHub Copilot, runs in a sandboxed environment and can be hosted directly in the tenant. With Microsoft IQ, every solution created is anchored in the real context of the organization, with automatic plugin synchronization. Development teams continue to use GitHub Copilot for their daily work, with enhanced connectivity to the Copilot platform. Deployment schedule announced by Microsoft: availability in the Frontier program end of September 2026, rollout in the following weeks, then preview for Microsoft 365 Premium and Pro subscribers later in the year.
To host this code securely, Microsoft introduces the Microsoft Copilot Managed Runtime: a governed execution infrastructure controlled by IT but accessible frictionlessly to business users, enabling app sharing, connection to live data and access from anywhere. This foundation serves applications built in Cowork, Code and Copilot Studio, and now opens to third-party and pro-code developers.
Managed Runtime Governance
Copilot Managed Runtime remains under IT control (access policies, app lifecycle), but its goal is to prevent the usual shadow IT administrative bottleneck. Decide now who in your Microsoft 365 administration will be responsible for approving published apps.
Autopilot: the agent that keeps working while you sleep
Autopilot, formerly known as Scout, functions as a persistent digital teammate: you give it a name, role and objective, and it monitors channels, follows up on threads, executes recurring tasks and resumes a project days later without waiting for input. Microsoft cites the example of a complete supplier review process, entirely driven by the agent — scheduling, preparation, meetings, follow-ups with stakeholders.

Autopilot has its own identity, memory, workspace and work account in the tenant, all anchored in Microsoft IQ to understand the real processes of the organization. It appears in Teams, Outlook, chats and documents, and can be @mentioned like a colleague, with associated permissions, audit logging and governance. Microsoft announces Autopilot entering private preview end of September 2026.
An agent with its own identity = a full governance object
Autopilot has its own identity and memory in the tenant. Before any deployment beyond a limited pilot, verify associated Agent 365 policies (permissions, audit, lifecycle) rather than relying solely on the scope defined at agent creation.
Microsoft IQ extends business context available to Copilot
Microsoft IQ is the unified intelligence platform that connects how the enterprise operates to its data, to feed Copilot and agents in real-time, with integrated governance and security.
Two context extensions are announced:
- Fabric IQ brings context from over 20 million Power BI semantic models into Copilot. It already powers Chat and Cowork, available in general availability (GA) starting today, with integration to Code announced "soon" via the Frontier program.
- Copilot is now anchored in the data and workflows of Dynamics 365 and Power Platform, rolling out progressively in public preview over the coming month. A sales representative drafting a proposal can thus see deal history or support tickets integrated directly into the document, without switching applications.
Finally, a new plugin registry brings together Microsoft, partner and internally-developed plugins in a unified catalog. IT can approve and manage plugins centrally, while developers and partners publish once to reach all supported Copilot experiences. This registry is currently rolling out, with general availability announced in the coming weeks.
User license vs. usage-based billing: the new economic model
Microsoft now distinguishes two cost logics depending on the type of work performed. The User Subscription License (USL) covers daily usage: Chat, Copilot in Word/Excel/PowerPoint/Outlook/Teams, model selection, and new capabilities as they roll out. At the heart of the USL, the Auto engine arbitrates at each request between accuracy, speed and cost to route to the most appropriate model.
Agent work — more resource-intensive and requiring advanced models — follows a different logic: Usage-Based Billing (UBB), which gives complete control over model selection and cost/value alignment. Cowork, Code, Autopilot, new long-running agentic capabilities, as well as cutting-edge Astra and Fable models, all operate on this basis.
| Model | Covered capabilities | Cost logic | Typical use case |
|---|---|---|---|
| USL (user license) | Chat, Word, Excel, PowerPoint, Outlook, Teams, model selection via Auto | Fixed cost per user | Quick answers, drafts, summaries, spot analyses |
| UBB (usage-based billing) | Cowork, Code, Autopilot, long-running agentic capabilities, Astra and Fable models | Measured consumption, fine control over model selection | Complex task delegation, persistent agents, code execution |
Microsoft clarifies that this pricing model will continue to evolve with usage; details are published in the documentation for Copilot billing model evolution.
FinOps for AI: maintain control of spending
FinOps for AI refers to the shared discipline of managing and optimizing AI spending. Microsoft extends this approach across Agent 365, Insights and Copilot:
- Cost management in Agent 365 extends beyond Cowork and Work IQ APIs to now cover Code and the Copilot Managed Runtime, with support for Copilot Studio agents announced in October.
- Administrators can manage spending policies at scale via API, route credit requests to existing approval workflows, and restrict available model families by user group — a configuration that also conditions the pool of models available to the Auto engine.
- Business owners have indicators to identify which Cowork tasks generate the most value, to decide where to maintain, extend or optimize usage.
- End users visualize directly in Copilot their credit consumption, remaining balance and usage history, respecting guardrails set by the organization.
Microsoft details these commitments in its documentation on FinOps for AI optimization.
Tenant-wide impact of model policies
Restricting available model families by group affects all concerned users, including automatically made choices by Auto. Test any spending or model policy on a restricted pilot group before applying it to the entire tenant — an overly strict policy can silently degrade Chat and Cowork response quality.
What comes next: Today and @Copilot in Teams
Two additional capabilities are announced in preview. Today, coming to Home, acts as a proactive command center crossing emails, calendar, Teams threads, meetings and tasks: it doesn't just flag what was missed, it already prepares draft responses or suggests schedule changes. Today enters private preview in October in Copilot, before arriving in Outlook and Teams.
Furthermore, invoking @Copilot in Teams will provide access to the shared context and permissions of the channel, group chat or meeting — enabling tracing of decision history without re-explanation, and automatically triggering preparation of a cross-functional review (dependencies, owners, open questions). This capability enters private preview end of September 2026.
Microsoft promises to say more at Microsoft Ignite, November 17-20 in San Francisco and online.
Implementation: preparing Copilot adoption and cost tracking
Before the new USL/UBB model and FinOps for AI dashboards become mainstream, it's useful to establish a baseline: how many users already have a Copilot license, and what is their current usage level. The script below relies on the Microsoft Graph PowerShell SDK.
Prerequisites:
- Module:
Install-Module Microsoft.Graph -Scope CurrentUser - Minimum Graph permission:
Reports.Read.AllandUser.Read.All(delegated) - Recommended minimum Microsoft Entra ID role: Reports Reader, rather than a global administrator role
- Output produced: a
copilot-usage-D7.csvfile listing Copilot usage over the past 7 days, to cross-reference with future FinOps for AI indicators
1# Connect with least privilege principle2Connect-MgGraph -Scopes "Reports.Read.All", "User.Read.All"3 4# 1. Identify the Copilot SKU(s) present in the tenant5$copilotSku = Get-MgSubscribedSku | Where-Object { $_.SkuPartNumber -like "*COPILOT*" }6 7if (-not $copilotSku) {8 Write-Warning "No Copilot SKU detected. Verify exact label via: Get-MgSubscribedSku | Select SkuPartNumber"9 return10}11 12# 2. List of Copilot-licensed users13$copilotUsers = Get-MgUser -All -Property "DisplayName,UserPrincipalName,AssignedLicenses" |14 Where-Object { $_.AssignedLicenses.SkuId -in $copilotSku.SkuId } |15 Select-Object DisplayName, UserPrincipalName16 17Write-Host "Copilot-licensed users detected: $($copilotUsers.Count)"18 19# 3. Copilot usage report for 7 days, retrieved as JSON via $format parameter20$reportUri = "https://graph.microsoft.com/beta/reports/getMicrosoft365CopilotUsageUserDetail(period='D7')?\$format=application/json"21$usageReport = Invoke-MgGraphRequest -Method GET -Uri $reportUri22 23# 4. Export for later cross-reference with FinOps for AI dashboards24$usageReport.value | Export-Csv -Path ".\copilot-usage-D7.csv" -NoTypeInformation -Encoding UTF825 26Write-Host "Export complete: copilot-usage-D7.csv"This script is read-only: it modifies no licenses or policies, so it can be run in production without simulation mode.
Common troubleshooting
- Error 403
Authorization_RequestDenied: theReports.Read.Allscope was not consented, or the account used doesn't have the Reports Reader role (or higher). - Pseudonymized names in the report (e.g. "User 1234"): the report privacy setting is active in the Microsoft 365 admin center, under Organization settings > Reports. Disable anonymization to get concrete identities, if your internal privacy policy allows.
- Empty or incomplete report: Copilot usage reports experience propagation delay; a
D7period doesn't necessarily reflect the very last 24 to 48 hours. - SKU not found: the exact name of the Copilot SKU varies by contract (Microsoft 365 Copilot, Copilot Chat, etc.) — always verify the actual value via
Get-MgSubscribedSkubefore writing a filter.
Key takeaways
This new Copilot shifts the center of gravity of the productivity tool toward an environment of delegation, creation and persistent automation. Concretely, starting today:
- Check if your organization is enrolled in the Frontier program to access Home and Code in the coming weeks.
- Anticipate the shift in cost model: identify who in your organization will use usage-based billing capabilities (Cowork, Code, Autopilot) rather than just the user license.
- Assign the Reports Reader role to a dedicated service account to track Copilot adoption before FinOps for AI dashboards become the official reporting channel.
- If your organization plans to pilot Autopilot in private preview, frame governance first (permissions, audit, objective scope) rather than relying solely on initial agent configuration.
See you at Microsoft Ignite, November 17-20 in San Francisco and online, for more announcements on this Copilot roadmap.


