Stores affected by the shipment issue Autopilot surfaced in Microsoft's demo: 18 (Source: Microsoft demonstration, reported by VentureBeat (Sept. 25, 2026))
A background employee with its own identity
Microsoft's Friday redesign combines Office collaboration, software creation and autonomous agents inside Copilot. The overhaul names two new destinations for enterprise work: Code, which generates applications from written instructions, and Autopilot, a persistent agent that can monitor projects and coordinate with employees for days without one present. Microsoft also introduces managed application hosting for the applications employees build and expands the controls businesses use to track AI spending. For organizations already running Copilot, the change moves the assistant from a chat window into something closer to a background employee with its own identity, memory and workspace inside the company's Microsoft 365 tenant.
What the demo showed
Autopilot is the renamed successor to Scout, Microsoft's earlier personal-agent project, which the company said in June was built on the open-source technology OpenClaw with added enterprise identity and access controls. Assigned an objective and role, Autopilot can watch conversations, chase updates, handle recurring responsibilities and pick a project back up after several days, interacting with staff through Teams, Outlook and shared documents. Microsoft demonstrated the concept with an Autopilot named Dot that tracked Black Friday preparations across email, Teams discussions, Dynamics 365 inventory records and spreadsheets.
Whether Autopilot performs as reliably in a live deployment as it did in a scripted demo is not something the announcement addresses, and Microsoft's own materials leave the underlying architecture change from Scout largely unexplained.
The bill scales with autonomy
For budget-holders, the more immediate question is cost. Base Copilot subscriptions hold steady at $30 a month, but Microsoft's own workload modeling shows how quickly that changes once agents start working unsupervised. The company also extended its FinOps spending controls, first built for Agent 365, to cover Autopilot, Code and the new managed runtime, with Copilot Studio agents scheduled to join in October. Metered usage stays switched off for a tenant until an administrator creates a spending policy, and administrators can cap credits, set alerts and restrict which model families are available to automatic routing.
Governance is still catching up
Agent 365 supplies identity, permissions and audit records for Autopilot, and Microsoft CEO Satya Nadella told a September 23 presentation that "every agent has to have an identity" and that "everything it does needs to be observed." But the launch materials stop short of a complete action-by-action approval policy, and they do not explain how administrators should handle every category of failed execution once an agent is acting on its own.
Enterprise licensing adds another layer. A Microsoft 365 E7 plan, billed annually, bundles E5, Copilot, Agent 365 and Entra Suite for $99 per user a month; Agent 365 alone lists separately at $15 on the same terms. None of those figures establish unlimited Autopilot or Code usage — they cover access, not consumption.
What to ask your team
Before expanding beyond a pilot group, a budget-holder's team should be able to answer a few specific questions: what would the credit-consumption forecast look like for the department's actual Autopilot and Code use cases, not Microsoft's modeled workload; which categories of agent failure trigger a human review rather than an autonomous retry; whether the GitHub Copilot Business or Enterprise license that Scout's preview required still applies once Autopilot leaves private preview; and which model tiers, metered or included, are assigned to each team before automatic model routing is turned on.
