A man views a laptop displaying analytics and security tools, with cloud and server graphics in a modern office.
Microsoft's AI at Work roadmap now has an entry for Copilot Code (ID 571887). The pitch is that office workers can type a description and get working software back. Under the hood, the parts that matter to Windows admins are a governed hosting platform, a Windows 11 sandbox with specific build requirements, and a usage-based billing model that needs a spending policy before anyone can use it.

The roadmap lists Copilot Code as In development. It estimates preview in October 2026 and general availability in December 2026, on Android, desktop, iOS, Mac and web, in the Worldwide Standard Multi-Tenant cloud only. Microsoft's usual caveat applies: roadmap dates are estimates, and entries can be removed when a feature ships, slips or is cancelled. The December date is a target, not a promise.

A man views a laptop displaying analytics and security tools, with cloud and server graphics in a modern office. What Copilot Code actually is​

Copilot Code is not autocomplete in a new outfit. Microsoft Learn describes it as a separate Code tab in the Microsoft Copilot app, next to Home. You explain the outcome you want—a dashboard, an internal tool, a static website, a data transform, or a script—and Copilot Code builds it, shows you a live preview, and iterates with you until it works. You don't need to know how to code.

The roadmap says the experience is "grounded in their work by Work IQ." In practice, with your permission, Copilot Code uses your Microsoft 365 documents, emails, meetings, and calendar as context. Microsoft's September announcement said the engine underneath is powered by the same underlying technology as GitHub Copilot, Code runs in a sandboxed environment and can be hosted securely within your tenant.

According to Microsoft's documentation, the workflow looks like this:

  • Start a project from a plain-language prompt, pasted text, uploaded files (CSVs, spreadsheets, images, documents, PDFs, presentations) or, for local projects, an existing folder.
  • Preview it on the canvas. The finished app or site appears next to the conversation. You can switch to the raw code, or click an element in the preview to point Copilot at what you want changed.
  • Iterate and revert. You give feedback in plain English and can roll back to an earlier version.
  • Extend it. Code uses the same plugins as Cowork, plus web search and image generation, subject to your organization's policies.
  • Automate. You can schedule tasks on your device or start them manually. Microsoft's example is refreshing a dashboard every morning.

Code-tab conversations stay in the Code tab and don't appear in Chat or Cowork.

Section summary: Copilot Code is a conversational, project-based build-and-preview tool for people who think in outcomes rather than syntax. Microsoft says it is powered by the same underlying technology as GitHub Copilot.

Local vs. cloud: where the code runs​

Projects can run in two places:

ModeWhere it runsNotes from Microsoft's docs
LocalA project folder on your PC or MacCan read files, install dependencies and run the app for preview. It asks for approval before going outside the folder, connecting to the network or running terminal commands
CloudAn isolated cloud environmentWorks across devices. Mobile and web sessions are cloud-only

On iOS, iPadOS and Android, the Copilot mobile app can start and follow cloud sessions, respond to approval prompts and review results. Local sessions aren't available on mobile.

Admins should check the default: according to Microsoft's admin documentation, the execution location defaults to cloud only. Message Center post MC1519871 confirms that admins can allow local coding on PC by setting Code execution location to Cloud and local in the Microsoft 365 admin center.

The Windows angle: sandbox requirements and build numbers​

When Copilot Code runs on your machine, a sandbox limits its file and network access. Microsoft Learn's requirements page says the sandbox is supported on Windows 11, version 24H2 or later and on Mac. Windows 10 is not supported. If your organization requires the sandbox and a device can't run it, that user can still run projects in the cloud.

Git commands that the agent runs inside the sandbox have their own minimum builds, and they also need the latest Copilot app:

Windows 11 versionMinimum update / OS build
24H2KB5124010, build 26100.9550 or later
25H2KB5124010, build 26200.9550 or later
26H2KB5124010, build 26300.9550 or later
26H1KB5124006, build 28000.3086 or later

The requirements page separately says that Git and Node.js in the sandbox need build 26200.9550 or later on 25H2, or 28000.3086 or later on 26H1. If you're planning a pilot, check these against your update rings first. A fleet stuck a few cumulative updates behind will get a confusing first experience.

Other Windows details:

  • The Copilot desktop app is supported on Windows x64 and Arm, and on Mac (Intel and Apple silicon).
  • On first launch on Windows, the app downloads a one-time set of required assets. Admins can preinstall those components with the Preinstall Copilot Code components policy, which is off by default.
  • Device policies are delivered through the Microsoft Copilot ADMX template (copilotapp.admx), which you can import into Intune. The settings are under Microsoft Copilot > Code Tab. On macOS, the policy domain is com.microsoft.Copilot.
  • For Frontier, MC1519871 says that for Windows devices participating in Frontier, set the Microsoft Copilot target channel to Beta.

Section summary: Local execution on Windows needs Windows 11 24H2 or later, plus specific late-2026 cumulative updates if the agent will run Git. Windows 10 machines can only use cloud mode.

Copilot Managed Runtime: the part that may matter more​

The roadmap says projects "can be published as managed apps on Copilot Managed Runtime with IT in control." Microsoft introduced the runtime in September as hosting infrastructure that lets code run safely right inside your company's Microsoft 365 environment. This same foundation enables apps built in Cowork, Code and Copilot Studio, and we're opening it up to third-party and pro-code developers, too. Copilot Managed Runtime reached general availability at Ignite 2026 on November 17, 2026, and will also be accessible inside Code.

Microsoft's documentation stresses three points:

  • Building and publishing are separate. An app saves automatically while you work, but it goes live only when you ask Code to publish it.
  • Sharing an app doesn't share its data. Recipients see only data they already have permission to access in connected sources, such as a SharePoint list, and may need to approve a connection when they first open the app.
  • Publishing is itself a preview feature and requires the Frontier program.

Several independent commentators think the runtime is the bigger story. The consultancy Actonomy wrote that the runtime is the more important of the two announcements. It also noted that an SDK and CLI let tools such as Lovable, Claude Code, and GitHub Copilot deploy to the same runtime. A DEV Community analysis summed up Microsoft's positioning: GitHub Copilot stays the tool for developers, and Code is aimed at everyone else.

GitHub: optional, and off by default​

GitHub isn't required to build, preview or save projects. Once connected, Copilot Code can clone repositories, answer questions about code, create branches, commits and draft pull requests, create a new repository from a Code project, and show issues and review requests in "My Work."

The tenant policy for GitHub connections is off by default. A separate allow-list setting limits users to GitHub.com, GitHub Enterprise, both, or neither, and admins can restrict connections to GitHub accounts tied to the tenant.

Admin controls and defaults​

Microsoft's admin guide lists these organization-level defaults:

ControlDefault
Preinstall Code componentsOff
Auto-approve setting available to usersOn
Execution locationCloud only
GitHub connectionOff
Organizational data (Work IQ/Graph)On for cloud, off for local
Sandbox required (local)Enabled. Users can't turn it off
Sandbox outbound network modeAllow list only

Some behaviors worth knowing:

  • The sandbox fails closed. If it can't start, Copilot Code won't run the affected command, and nothing runs unprotected.
  • Apps users launch themselves aren't covered. If someone runs an app Copilot Code built outside a Code session, the sandbox doesn't restrict it. Treat that as a real gap in the security boundary.
  • "Always allow" is sticky. Once a user enables it, it applies to existing and new sessions until they turn it off. Microsoft's own documentation tells users to be careful with it. Since the auto-approve control defaults to On, some admins may want to change it.
  • Auditing. Logs record generated code, commands run, and files read or written, so you can trace each action back to the user's request.

Licensing and billing​

Work accounts need a Microsoft Copilot license, the Code tab enabled by the organization, and Entra sign-in. Personal Microsoft accounts need a supported consumer Copilot plan. For organizations, Code uses usage-based billing and needs a configured spending policy. MC1519871 tells admins to enable Copilot Credit consumption and configure the appropriate spending policies in the Microsoft 365 admin center under Copilot > Cost management. Microsoft also said in September that cost management in Agent 365 is expanding beyond Cowork and Work IQ APIs to include Code and Copilot Managed Runtime.

What it will cost is still unclear. One UK consultancy, Five Forward, noted that Microsoft has not published rates for Code. Expect finance teams to ask about that.

A timeline that doesn't quite agree​

Microsoft's dates conflict:

  • The September 25 blog said Code is rolling out to Frontier at the end of the month, with broad availability in the coming weeks.
  • MC1519871 later said the rollout begins with the Frontier program in late October 2026.
  • The roadmap lists an October preview and a December 2026 general availability.

As of November 17, every Microsoft Learn page for Copilot Code still labels it a Frontier preview. Those pages warn that preview features may have limited functionality, may change, and may never reach general availability. Treat December as Microsoft's goal, not a date to build your plans around.

The verdict: low-code returns, with a sandbox​

This isn't the first attempt at "anyone can build an app." Access databases and Power Apps both promised it, and both left IT departments cleaning up unofficial apps nobody owned. Microsoft's answer this time is to make that hidden development visible. Apps are hosted in the tenant, sign-in goes through Entra, execution is sandboxed and every action is logged.

That approach is better than what came before, but it isn't complete. "IT in control" depends on admins actually configuring the controls. The sandbox doesn't cover apps users run outside Code, the sticky "Always allow" setting can weaken approvals, and an AI-generated dashboard can show the wrong numbers just as easily as a hand-built one.

A practical starting checklist for admins:

  • Decide who gets Frontier access, and set the Copilot app channel to Beta on pilot Windows devices.
  • Configure a spending policy with per-user limits before you enable Code.
  • Confirm pilot PCs run Windows 11 24H2 or later with the required cumulative updates, or keep those users on cloud-only execution.
  • Import the Copilot ADMX template into Intune and review the sandbox network allow list.
  • Leave GitHub connections off until you've restricted them to tenant-linked accounts.
  • Decide whether to keep auto-approve available, and tell users how "Always allow" works.
  • Turn on audit log review so you can see which apps appear in your tenant.

If December's general availability arrives on schedule, a lot of internal tools will be built by people who've never opened a terminal. A little configuration now will make that easier to manage.


Correction (November 17, 2026): An earlier version of this article said Copilot Managed Runtime was in preview. Microsoft announced at Ignite 2026 on November 17, 2026, that Copilot Managed Runtime is now generally available. Publishing apps from Code remains a preview feature and requires the Frontier program.

 

References

  1. Microsoft Copilot (Microsoft 365): Copilot Code Microsoft 365 Roadmap 2026-11-17T18:36:41.967573Z
  2. Copilot Code and the Managed Runtime: first thoughts — Actonomy actonomy.ai
  3. Microsoft Copilot Roadmap | Microsoft 365 microsoft.com