Microsoft is turning Copilot into a single work surface for three different jobs: conversational and delegated work in Home, natural-language solution building in Code, and persistent cloud-hosted tasks in Autopilot. The packaging is simpler, but the deployment boundary is not. Microsoft’s September 25 announcement separates availability, hosting, identity and billing across the three modes. For IT and platform teams, the useful question is not whether Copilot is now a “super app.” It is which capability is available to which users, where generated code runs, what permissions a persistent agent receives, and how long-running work is metered.

Home, Code and Autopilot are different control surfaces

Home combines Chat and Cowork, and Microsoft says Word, Excel and PowerPoint files can be created or updated directly from Copilot while remaining editable in Office. Chat handles quick questions and drafting; Cowork is positioned for delegated, end-to-end work. Code accepts natural-language requests for apps, trackers, dashboards, automations and workflows. Microsoft says it runs in a sandbox and can host output inside the tenant through Copilot Managed Runtime. Autopilot, previously called Scout, is the persistent mode. Microsoft describes it as cloud-hosted with its own identity, memory, computer and workspace, able to watch channels, follow up on threads and resume work later.

The rollout is staged, not generally available

The official launch sets different availability points. Home and Code start rolling out through Microsoft’s Frontier program in the coming weeks. Autopilot expands to private preview at the end of September. Code is also planned for preview for Microsoft 365 Premium and Pro subscribers later in 2026. Copilot Managed Runtime is in preview now. Teams should therefore record the exact tenant, program, licence and preview status instead of treating the three tabs as one broad release.

Code shifts the question from generation to operation

Natural-language app generation is only the first boundary. Microsoft says Copilot Managed Runtime supplies hosting inside the Microsoft 365 tenant, with IT governance, sharing and live-data connections. That reduces some provisioning work, but it does not remove application ownership. Operators still need to know what data a generated app reads, which identities it uses, who can share it, how changes are reviewed and what logging or rollback path exists. A sandboxed build step and a governed runtime are related controls, not proof that every generated app is safe to deploy.

Autopilot needs its own identity review

A persistent agent that continues while a user is away changes the permission model. Microsoft says Autopilot has its own identity and workspace and can be mentioned in Teams, Outlook, chats, channels and documents, with permissions, audit and governance behind it. Before enabling a preview, administrators should test how objectives and boundaries are expressed, which actions require human approval, how access follows the agent across apps, and how an owner can stop or revoke ongoing work. “Keeps working” is a product capability, not a reason to grant broader access.

Agentic work moves onto usage-based billing

Microsoft separates everyday Copilot use from long-running agentic work. Its announcement says Chat and Office productivity are covered by a user subscription licence, while Cowork, Code, Autopilot and frontier models use usage-based billing. Admins can manage spending policies, route credit requests into approval workflows and restrict model families. That makes cost policy part of rollout design. A pilot should define per-user or per-team limits, alert thresholds and the owner for exceptions before persistent agents begin recurring work.

A practical verification checklist

  • Confirm tenant and licence eligibility separately for Home, Code, Autopilot and Managed Runtime.
  • Record whether each capability is generally available, Frontier-only, public preview or private preview.
  • Test generated applications with least-privilege data and sharing permissions.
  • Review Autopilot identity, audit trail, stop controls and cross-app access before persistent tasks.
  • Configure spend policies and approval paths for usage-based work.
  • Keep pilot data and workflows reversible until the preview controls are understood.

Microsoft’s new Copilot narrows the front door but expands the control surface behind it. Teams that treat Home, Code and Autopilot as separate deployment tracks will get a clearer view of readiness than teams that enable the combined app as one feature.