Microsoft has started rolling out Copilot Code, a new Code tab in Microsoft Copilot that turns a plain-language request into working software: a dashboard, an internal tool, a static website, a data transform or a script. The rollout to the company's Frontier early-access program was announced to administrators on October 21, 2026, and begins in late October. This guide explains who can get it, how to build a first project, and what admins should decide before switching it on.
Who Can Use Copilot Code Right Now
Copilot Code is a preview feature, and for business customers it sits behind several gates. According to Microsoft's Message Center notice (MC1519871), eligible users must:
- Be enrolled in the Frontier program, Microsoft's early-access track for new Copilot features.
- Hold a Microsoft 365 Copilot license.
- Be covered by a spending policy, because Copilot Code runs on usage-based billing that consumes Copilot Credits.
Admins enable Copilot Credit consumption and configure spending policies under Copilot, then Cost management, in the Microsoft 365 admin center. One detail is easy to miss: if a spending policy already has "Allow new Agents and services as they become available" turned on, people covered by that policy receive Code automatically.
On Windows, Microsoft's documentation also asks admins to deploy the unified Microsoft Copilot app and set its update target channel to Beta on Frontier devices. Copilot Code runs in the Copilot desktop app for Windows and Mac, and on the web at copilot.cloud.microsoft for cloud projects.
How to Build Your First App, Step by Step
The workflow in Microsoft's get-started guide looks like this:
- Open the Code tab. Launch the Copilot app or the web version and select Code in the tab switcher.
- Describe the outcome. Type what you want in the task box, and be specific about what it should do and who will use it. Microsoft's own example is a dashboard that tracks weekly signups by channel.
- Add context. Use the + button or drag and drop files such as CSVs, spreadsheets, PDFs, documents, images or presentations. You can also paste raw data straight into the prompt.
- Pick where it runs. Choose cloud to keep the project online, work across devices and share it, or local to work inside a project folder on your PC.
- Choose a model. The model picker includes Anthropic's Claude Opus 5 and Sonnet 5 families, OpenAI's GPT 5.6 and GPT 5.5, and Microsoft's MAI-Code-1-Flash, or you can leave it on Auto for cloud projects.
After you send the request, Copilot Code may ask a few clarifying questions about layout or purpose, then shows its progress step by step. A live preview appears on a canvas beside the conversation, and you can switch to a code view to inspect or edit the generated files.
Iterating, Reverting and Sharing
Building is meant to be a conversation. Ask for a change in plain language, or click an element directly on the canvas to point Copilot at it before describing the fix. If a direction goes wrong, ask it to revert to an earlier version.
When something is ready, there are two ways to share it:
- Static apps can be shared as links scoped to your organization (cloud only).
- Interactive apps can be published to Copilot Managed Runtime, a Microsoft-managed cloud environment where published apps inherit the organization's governance, security and management controls.
Copilot Code can also draw on Work IQ context, meaning your emails, meetings, documents, calendar and chats, when you allow it. Microsoft stresses that access to data inside a published app still follows each viewer's own permissions, so a shared dashboard should not expose files a colleague could not already open. Users can additionally connect a GitHub account to clone repositories, open branches, commit and raise draft pull requests, but only if an admin has enabled that connection.
Admin Checklist Before You Turn It On
The defaults are fairly conservative. Cloud coding sessions are on by default for eligible users with a spending policy. Local coding, which lets Copilot Code work with files on the PC and use the terminal, is off until an admin sets the code execution location to cloud and local. If no spending policy is assigned but AI discovery is allowed, users see the Code entry point and welcome page but cannot actually build anything.
Microsoft's notice flags several compliance points worth reviewing: new storage of customer data in projects and apps, new routes to existing data through Work IQ, the optional third-party GitHub integration, and optional local execution. A sensible rollout sequence is to brief the help desk, confirm which spending policies grant access, decide between cloud-only and cloud-plus-local, and only then widen the pilot.
Why It Matters
Copilot Code puts a full AI app builder inside the productivity suite many offices already use, rather than in a separate developer tool. That lowers the barrier for staff who need a quick tracker but would never open an IDE. The trade-off is governance: every user who can build is now a potential publisher of internal software, and usage-based billing means costs follow adoption. Organizations that set spending policies, sharing scopes and data rules early will get the productivity gain without a sprawl of unmanaged apps. Because this is still a Frontier preview, Microsoft warns that features and timing may change before general availability.
