Microsoft Adds Home and Code to Copilot
The redesigned app brings conversational and delegated work into Home, while Code turns natural-language requests into tenant-hosted tools under a staged Frontier rollout.
Edited by Tyronne Panaino
Microsoft announced a redesigned Copilot on September 25, adding two work surfaces called Home and Code. Home puts quick conversations and longer delegated tasks in one starting place, while Code lets people describe small applications, dashboards, automations and workflows in natural language. Microsoft says both capabilities will begin through its Frontier early-access program before wider availability.
The change matters to Microsoft 365 users because it moves Copilot beyond a chat panel and toward a shared workspace for asking, delegating and building. It also gives administrators a new class of user-created software to govern, even though the announcement does not yet provide independent evidence about reliability, adoption or operating cost.
Home combines conversation, delegation and Office work
Home brings Chat and Cowork into the same Copilot starting point. Chat remains the immediate mode for questions, lookups, summaries and drafts. Cowork is aimed at work a user delegates end to end, such as preparing a briefing or assembling a package that can be reviewed and refined.
Microsoft also says Word, Excel and PowerPoint are built into the Home experience through Office in Copilot. A user can ask for a document, workbook or presentation and continue editing the resulting file with collaborators. That is a product-integration claim, not evidence that the generated work will be accurate or ready for consequential use without review.
The practical delta is continuity. Instead of moving a draft from a chat response into a separate Office file and rebuilding context, Microsoft wants the conversation and the editable work product to stay connected. Teams will still need to test version handling, permissions and the way source context travels into each generated artifact.
Code turns natural-language requests into internal tools
Code is the more structural addition. Microsoft describes it as a way for non-developers to request a tracker, dashboard, desktop widget, automation or cloud-hosted internal application in natural language. The company says the feature uses underlying technology from GitHub Copilot and runs in a sandboxed environment.
The resulting tools can be hosted inside a customer's tenant and connected to business context through Microsoft IQ and plugins. Microsoft also introduced Copilot Managed Runtime as the hosting layer for software produced through Code, Cowork and Copilot Studio. That creates an administrative boundary for distribution and access, but the announcement does not document a universal security guarantee, a complete isolation model or measured failure rates.
For IT teams, the important question is not only whether a user can make a tool quickly. It is whether the organization can identify who created it, which data it reaches, what permissions it inherits, how updates are reviewed and how usage is charged. Microsoft describes central plugin management and spending controls, but organizations will need product documentation and tenant testing before treating those controls as complete.
The rollout is staged rather than generally available
According to the official Microsoft announcement, Home and Code will begin rolling out through the Frontier program in the coming weeks. Microsoft says Code is due in Frontier at the end of September, with broader availability to follow, and a preview for Microsoft 365 Premium and Pro subscribers later in 2026. The fetched page does not give a precise country list, tenant-by-tenant schedule or final feature matrix.
The same announcement says the persistent agent previously called Scout is now named Autopilot and is moving into a private preview. That confirms one part of an earlier preview story, but it is not the reader purpose of this article: the new event here is Microsoft's public product structure for Home and Code and the staged path by which customers can try them.
Microsoft also separates ordinary subscription use from usage-based billing for longer-running agentic work. Cowork, Code and Autopilot are described as usage-based capabilities. Without plan-level rates or real workload measurements in the fetched evidence, customers cannot yet infer the cost of replacing an existing workflow with one of these tools.
What to watch next
The next verifiable checkpoints are Frontier access appearing in real tenants, detailed administrator documentation for Managed Runtime and plugins, and a published matrix covering plans, regions and client support. Independent testing should also examine whether Code-generated tools preserve data boundaries, survive changes to connected systems and remain understandable to the people responsible for maintaining them.
Status
Confirmed. Microsoft has announced Home and Code and described their staged rollout. Internal confidence is medium because the capabilities, timing and governance model come from a single first-party announcement and were not independently tested in this run.
Sources
Update note: Last reviewed 2026-09-26. We will revise this post when Microsoft publishes firm availability, plan, regional or administrator details.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.