Microsoft unveiled a rebuilt Copilot on Sept. 25 with three headline modes: Home, Code, and Autopilot, Chief Marketing Officer Jared Spataro wrote on the company blog. Home merges Chat and Cowork and brings Word, Excel, and PowerPoint into the Copilot app. Code lets non-developers describe apps, dashboards, and workflows in natural language, running on the same underlying stack as GitHub Copilot inside a sandboxed tenant. Autopilot — formerly Scout — is a persistent cloud-hosted agent with its own identity that can watch channels, follow up, and keep projects moving without a fresh prompt.

Home and Code were set to start in the Frontier program in the weeks after the post; Autopilot was expanding to private preview at the end of September. Microsoft also introduced Copilot Managed Runtime for governed hosting inside Microsoft 365 and layered FinOps tools so admins can set spend policies as agentic work shifts onto usage-based billing.

The Sunday carry lands beside OpenAI’s ASIC push and Google’s orbital prototype: enterprises are being sold agents that run while people sleep, on someone else’s silicon. The household and desk stake is whether delegated agents cut real work hours — or just create new approval queues and surprise credit bills. Backstory: Copilot has been Microsoft’s Microsoft 365 AI brand since 2023; this rebuild is the clearest split yet between chat, build, and always-on agent modes. Engage: Microsoft’s Sept. 25 blog for rollout stages and billing notes.

What we know:
Home, Code, and Autopilot were announced Sept. 25; Frontier and private-preview stages were named; Managed Runtime and FinOps controls accompany the agent push.

What we don’t:
Broad availability dates for every mode; typical Autopilot credit burn for midsize tenants; how often Cowork tasks finish without human rework.

Agree (full): Microsoft’s blog describes Copilot expanding into Home, Code, and Autopilot enterprise agents with Managed Runtime governance.
Differ (full): Microsoft emphasizes agent productivity; customers still weigh usage-based cost risk and admin overhead before wide enablement.