Microsoft restructured its Copilot AI assistant around three new destinations - Home, Code, and Autopilot - giving the system a larger role in managing ongoing workplace assignments, generating custom applications, and continuing tasks after employees log off. The announcement, made Friday, leaves key pricing details for the new metered services unresolved, forcing enterprise buyers to weigh expanded delegation against uncertain costs.
The overhaul introduces Autopilot, a persistent agent that can monitor projects, coordinate with colleagues, and resume work days later. It also adds Code, which generates applications from written instructions and runs them on Microsoft-managed infrastructure. Home combines quick chat exchanges with the longer collaborative assignments previously handled by Cowork. Together, the changes represent Microsoft's most substantial bet that businesses will hand routine responsibilities to AI - and pay for the compute those tasks consume.
Autopilot takes on continuing assignments
Autopilot - previously called Scout - lets users assign it an objective and a role. The system maintains its own identity, memory, computing environment, and workspace inside the organization's Microsoft 365 environment. It can watch conversations, pursue updates, handle recurring responsibilities, and resume a project after several days. Employees interact with it through Teams, Outlook, and documents, including by mentioning it as they would another participant.
"Every agent has to have an identity. Everything it does needs to be observed," Microsoft CEO Satya Nadella said during a September 23 presentation.
Microsoft demonstrated Autopilot through a retail scenario. An agent named Dot monitored Black Friday preparations, pulling information from email, Teams discussions, Dynamics 365 inventory records, and spreadsheets. It identified a shipment problem affecting 18 stores, brought employees into a discussion, and reported that the group had resolved the issue. The demonstration illustrates the intended workflow; it does not establish how reliably Autopilot handles comparable situations across customer deployments.
Agent 365 supplies the permissions, audit records, and administrative controls around Autopilot. Those capabilities matter when software starts contacting people or acting on business information. The launch documents do not spell out a complete action-by-action approval policy or explain how administrators should handle every category of failed execution.
Home embeds Office collaboration and Code generates custom applications
Home merges quick conversational exchanges with the longer assignments handled by Cowork. Microsoft plans automatic routing so users can describe an outcome and let Copilot select the appropriate capability. Office integration embeds editing and collaboration for Word and PowerPoint alongside Excel, keeping shared files synchronized with the separate Office applications colleagues are using. A feature called Today gathers signals from email, calendars, discussions, and assignments to prepare follow-up drafts or propose calendar adjustments.
Code extends Copilot to employees who need a custom tool for a particular task. They can describe an application, dashboard, automation, or desktop widget, and Copilot generates the implementation. Microsoft says Code shares foundational technology with GitHub Copilot and draws on organizational context and connected services. The new Copilot Managed Runtime hosts applications within the organization's Microsoft 365 boundary, with Entra supplying identity services and Git tracking source code and versions.
"What this means at its core is hosting and sharing an application literally becomes as simple as saving and sharing a Word document," said Jacob Andreou, Microsoft's executive vice president for Copilot.
Administrators receive a consolidated application inventory with information about access, activity, health, and policy. The practical benefit is a common operating environment for the growing number of applications employees can generate - a concern as business users build tools without traditional IT oversight. For teams evaluating how to manage this shift, AI Agent Courses cover the governance and deployment patterns organizations need.
Spending controls expand as metered services grow
More autonomous work means more opportunities to incur usage charges. Microsoft's FinOps additions extend Agent 365's spending-management coverage to Autopilot, Code, and the managed runtime. Existing controls already let administrators allocate budgets, impose limits, and receive alerts. Metered services remain disabled until administrators establish access through spending policies.
New capabilities include group-specific model access, starting with Cowork. An administrator can restrict available model families, which also limits the choices available to automatic model routing. Employees gain visibility into consumed credits, remaining allowance, and previous activity. Organizations can administer spending policies and monitor balances through Microsoft Graph APIs.
Microsoft also introduces Cowork reporting intended to connect resource consumption with useful results. The supplied announcement does not explain the measurement method well enough to treat those dashboards as proof of financial returns.
Pricing leaves key questions unanswered
Everyday use remains covered by the $30 per-user monthly enterprise subscription. Cowork, Code, and Autopilot require that subscription plus charges for Copilot Credits. Microsoft supplied example workloads: its $30 subscription covers roughly 15 everyday tasks, while 20 everyday tasks plus five complex Cowork assignments reaches $73 with Opus 5 or $69 with GPT-5.6 Sol, including $43 or $39 in consumption. These figures describe selected workloads, not new subscription tiers.
Earlier Cowork economics provide context. Microsoft's June credit guide estimated light tasks at $0.70-$2, medium tasks at $4-$6, and heavy tasks above $15 at the pay-as-you-go rate. Those estimates do not establish prices for Code or Autopilot. The new materials supply no detailed usage rates for the expanded services, leaving administrators without the numbers they need to forecast costs.
Availability is staggered. Home and Office integration begin reaching Frontier participants over the coming weeks. Code is scheduled for Frontier at September's end, with wider access to follow. Autopilot's private preview expands at month-end, while the managed runtime and SDK enter public preview. For organizations building internal expertise, Microsoft AI Courses cover the Copilot ecosystem and administrative controls relevant to these rollouts.
Why this matters for IT, finance, and operations leaders
Microsoft is making a broader range of work delegable through Copilot - but the missing usage rates mean buyers cannot yet model total cost of ownership. The product roadmap is substantial. The financial controls are partially defined. The reliability of Autopilot across real customer environments remains unproven. For the executives and administrators who will decide whether to deploy these tools, the immediate task is testing the previews while pressing Microsoft for the pricing clarity that turns a capability announcement into a budgetable plan.
Your membership also unlocks:
