One-Line Summary

Microsoft unifies chat, documents, no-code apps, and persistent agents in a redesigned Copilot to centralize everyday work inside Microsoft 365.

Big Tech

Microsoft brings Home, Code, and Autopilot to Copilot

Microsoft is rolling out a redesigned Copilot app that adds three capabilities: Home, Code, and Autopilot. Home combines Chat and Cowork in one starting page and embeds Office in Copilot so Word, Excel, and PowerPoint files can be created and edited directly inside the app. Microsoft says Home and Code roll out to the Frontier program over the weeks following Sep 25, 2026, and Autopilot expands to private preview by the end of Sep 2026. ¹

Code lets non-developers describe an app, tracker, dashboard, or automation in natural language; Copilot chooses an approach and builds it, running in a sandbox within the customer’s tenant. Microsoft also previews Copilot Managed Runtime to host these solutions safely inside Microsoft 365, and introduces FinOps for AI features to monitor and manage spend on Copilot and agents. ²

Autopilot, previously called Scout, acts as a persistent agent with its own identity that watches channels, follows up on threads, schedules, and resumes work without a new prompt. It lives inside a customer’s tenant with permissions, audit, and governance, and appears where people already work (Teams, Outlook, chats, channels, documents). ²

Microsoft positions Copilot as a central place to ask questions, complete or delegate tasks, develop solutions, and automate processes, and it plans previews like Today in Home and @Copilot in Teams to deepen the experience. The company also highlights enhanced grounding via Microsoft IQ to connect organizational data, processes, and applications for more context-aware results. ¹

What This Means for You

If your team works in Microsoft 365, putting Office directly inside Copilot and merging Chat with Cowork means fewer context switches and a clearer path to delegate end-to-end work. That can speed up briefs, budgets, and decks while keeping a single live file your team edits together. ²

Code lowers the bar for building small internal tools, but the value depends on guardrails: run inside your tenant, attach only necessary data sources, and use Managed Runtime so IT can govern hosting. Start by defining one low‑risk workflow in plain language, then map inputs, outputs, stakeholders, and approval steps. ²

Autopilot changes handoffs: instead of chasing updates across chats and email, you set objectives and boundaries and let the agent run daily follow‑ups, with audit and permissions in place. Begin with recurring processes like supplier reviews or weekly reporting once your org has access. ²

Finance and ops teams can prepare to quantify value and costs using Microsoft’s FinOps for AI capabilities: pair usage telemetry with budgets so you can justify licenses and retire agents that don’t pay off. ²

Action Items

1. Revisit Copilot in Office apps: Open one real Word, Excel, or PowerPoint file and use Copilot to draft, visualize, or apply brand templates; note minutes saved versus your normal workflow.
2. Scope one Autopilot‑ready process: Write a one‑page brief for a recurring task (objective, inputs/outputs, boundaries, success metric) and share it with IT to evaluate when private preview access is available.
3. Draft a “Code” mini‑app spec: In plain language, outline a small internal tracker or dashboard (fields, data source, who edits, who approves) so you can build quickly when Code reaches your tenant.
4. Set up a two‑week usage log: Track when and where your team uses Copilot, what artifacts it produces, and estimated time saved to prepare for FinOps for AI reporting.
5. Create a governance checklist: Define five checks for any Copilot app/agent (data scope, least privilege, audit logging, escalation path, human review) and circulate to your team.