MC1519871: Microsoft Copilot Adds AI-Powered Copilot Code for Frontier Users

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
72
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTenant AdminsIT ManagersSecurity TeamsService OwnersPower Platform Admins
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is a new rollout of Copilot Code for Frontier participants beginning in late October 2026. Admins must configure spending policies, enable usage-based billing and optionally local coding, and prepare support processes. User impact is high for those in the Frontier cohort as Code introduces new ways to build solutions with AI, but the rollout is limited. Governance, compliance, and cost control settings add substantial admin effort and urgency for early adopters.
78
🛡️ Admin Impact
62
👥 User Impact
70
⚡ Urgency
72
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Copilot Code is starting to roll out for Frontier users, bringing AI-assisted coding tools that let people build apps and dashboards directly in Copilot. Admins control who can use Code through spending policies and local coding settings.
👥

END USERS

Frontier users with Copilot licences may see a new Code option in Copilot where they can build and publish projects.
🛡️

IT ADMINS

Review spending policies, check which users have access, and decide whether to allow local coding before rollout.
📅

ROLLOUT TIMELINE

Start:
Late October 2026

📢 Official Microsoft Message Center Announcement


Copilot Code is rolling out in Frontier
Message ID: MC1519871

[What and Why:]

Copilot Code is an AI-powered coding experience in Microsoft Copilot that helps people turn ideas into trackers, dashboards, apps, and other solutions using natural language. Work IQ grounds what they build in emails, meetings, documents, chats, and connected data.

People closest to a problem can build the solution they need while your organization maintains control. Published apps run on Copilot Managed Runtime and inherit your organization’s governance, security, and management controls.

22314 1

[Rollout Schedule:]

  • Copilot Code: Begins with the Frontier program in late October 2026.

[Impact on Your Organization:]

Who is affected:

  • Users in the Frontier program who have a Microsoft 365 Copilot license and are enabled for usage-based billing.
  • Microsoft 365 admins who manage the Copilot app, spending policies, and usage-based billing.

Platforms/Services:

  • Microsoft Copilot app on Windows
  • Microsoft Copilot on the web
  • Microsoft 365 admin center
  • Copilot Managed Runtime
  • Work IQ
  • GitHub, when enabled

What users can do with Copilot Code

  • Users access Code from the Copilot app navigation pane and describe what they want to build. Copilot can ask clarifying questions and use their work context to build the solution.
  • Users can refine what they build through conversation or direct edits. On PC, when local coding is enabled, users can also work with local files and tools or use the terminal.
  • Users can publish projects to Copilot Managed Runtime, a Microsoft-managed cloud environment, and share them with others in their organization. Access to underlying data continues to depend on the user’s permissions.
  • Users can connect Code to GitHub when the connection is enabled by an admin.

How admin settings control access

Copilot Code uses usage-based billing. To use Copilot Code, users need:

  • A Microsoft 365 Copilot license.
  • A spending policy.

By default:

  • Cloud coding sessions are enabled on web and PC for eligible users with a Copilot spending policy.
  • Local coding sessions are disabled by default. Admins can allow local coding on PC by setting Code execution location to Cloud and local in the Microsoft 365 admin center.
  • Users covered by a spending policy where the setting “Allow new Agents and services as they become available” is enabled automatically receive access to Code through that spending policy.

For more information about Allow new agents and services setting, see MC1470425.

The following settings determine what users see and can use:

Code spending policyAllow users to discover and use AI experiences enabled by usage-based billingCode execution locationWhat users see
AssignedNo effectCloud (default)Code with cloud coding sessions
AssignedNo effectCloud and localCode with cloud coding sessions and local coding sessions on PC
Not assignedOnNo effectCode entry point and welcome page; Code cannot be used
Not assignedOffNo effectCode entry point is hidden

[Action Required/Recommendations:]

Action is required if you want eligible users to use Copilot Code.

  1. Review the Copilot Code blog.
  2. Deploy the unified Microsoft Copilot app.
  3. For Windows devices participating in Frontier, set the Microsoft Copilot target channel to Beta.
  4. Review your spending policies and confirm that Code is included for the users who should have access. If automatic access to new usage-based services is enabled, review which users will automatically receive Code through their existing spending policy.
  5. Enable Copilot Credit consumption and configure the appropriate spending policies in the Microsoft 365 admin center under Copilot > Cost management.
  6. Decide whether users should have cloud-only coding or cloud and local coding. Local coding is off by default.
  7. Prepare your help desk for the new Code experience, including the in-product experience and your organization’s access-request process.
  8. Review information about Copilot Managed Runtime.
  9. Review the Frontier program requirements and guidance.

Resources

[Compliance considerations:]

Stores new customer dataUsers can create projects/apps and publish them to Copilot Managed Runtime.
Changes how existing customer data is accessed or processedCode can use Work IQ, including emails, meetings, documents, chats, and connected data, to ground what users build.
Introduces new user interaction with organizational dataApps built with Code can use organizational context, and published apps may be shared with others in the organization subject to underlying data permissions.
Introduces external/third-party integrationGitHub can optionally be connected when enabled by an admin.
Introduces admin-controlled usage-based billingCode uses usage-based billing and requires the applicable spending policy for users to use the experience.
Introduces local execution/data interactionAdmins can optionally enable local coding sessions on PC, allowing users to work with local files and tools.

Source: Microsoft Message Center • Analysed by MWPro

Share This Update