Microsoft starts rolling out Copilot Code to turn work requests into apps

Microsoft began rolling out Copilot Code through its Frontier program on October 21, 2026, giving workers a way to build applications by describing what they need. The company’s pitch extends beyond generating code: users can draw on workplace information, refine a working app and share it, with a route into engineering review when projects grow.

Start with the work, not the code

Copilot Code is a coding experience inside Microsoft Copilot, aimed at turning a business need into usable software. Microsoft describes examples such as a tracker, dashboard or calculator—tools for people who understand a recurring problem but may not write software themselves. Digital Trends describes the rollout as a workplace-focused app-building tool, rather than simply another assistant for professional programmers.

The process begins with an outcome described in ordinary language. Microsoft says Copilot asks clarifying questions and uses Work IQ, its work-context technology, to draw from emails, meetings, documents, chats and connected data sources. That information helps it develop requirements, including details the user did not put in the first prompt. The starting point is therefore both the request and the surrounding work.

Microsoft illustrates this with a business leader assessing a revenue gap across global markets. The proposed application would bring together data, assumptions and business context to model investment decisions. It is an example of the intended workflow, not a reported customer result: the company presents a live application with calculations and changing inputs as the alternative to assembling another static file.

A preview is optional; so is cloud publishing

After the initial build, users can ask for changes in conversation or make direct edits. Microsoft says they can add visualizations, business logic and data sources without starting over. Someone who wants to stay away from code can work entirely in the live preview; someone who needs more control can open the code, use local files and tools, or work in a terminal.

Running and sharing are separate choices. A project can remain on a local device for personal use and be refreshed as needed, or be published to a Microsoft-managed cloud environment. For shared applications, Microsoft says Copilot builds on Copilot Managed Runtime, its managed application environment, so publishing requires no separate deployment work.

Sharing does not remove the underlying data-access requirement. Microsoft says people in the organization can use the application if they have permission to its data. It also says applications inherit the governance, security and management controls the organization has already configured. Those are Microsoft’s descriptions of the built-in controls, not an independent security assessment.

The handoff is a draft, not an engineering sign-off

Microsoft explicitly recognizes that a personal tool can become a larger maintenance job. As a project grows, it may need additional integrations, custom logic, security controls, quality reviews and release management. Copilot Code’s answer is to connect the project to a new or existing GitHub repository and open a draft pull request—a proposed change engineers can review and develop further.

That makes the two Copilot products connected rather than interchangeable. Microsoft says they share the same underlying agent technology but support different ways of working. Copilot Code begins with business context and conversation; the GitHub connection provides a starting point for structured collaboration, change review and further development when the application needs more than its original builder can maintain.