Set a Copilot Runtime Spending Policy Before December

Copilot Managed Runtime is GA and Copilot Code follows in December. Every person who runs a shared app needs Power Apps Premium or a runtime spending policy at 0.1 Copilot Credits per API call; E3 and E5 rights don't qualify.

By Rajesh Beri·November 19, 2026·10 min read
Share:
An office laptop showing a simple internal request-tracking app, with a printed Microsoft invoice line and a small stack of coins beside the keyboard on a desk, and a coworker leaning in to open the same app on a second

Illustration generated using AI

If your employees build apps in Copilot this winter, anyone who opens one needs a Power Apps Premium license or a seat in a runtime spending policy billing 0.1 Copilot Credits per API call. A Microsoft 365 Copilot license doesn't cover running them. Neither do the Power Apps rights bundled into Microsoft 365 E3 or E5. Microsoft's own guidance is a tenant-wide policy capped at 100 credits (US$1) per user per month, and you want it in place before Copilot Code reaches general availability in December.

Microsoft announced at Ignite on November 17 that Copilot Managed Runtime is "generally available today" and that Code "will become generally available in the coming weeks." The Ignite Book of News is more specific: "Copilot Code will be generally available in December." Neither page carries a price. The prices sit in admin documentation Microsoft Learn published the same day.

What Is Copilot Managed Runtime?

Copilot Managed Runtime is the hosting layer for apps built in Copilot. Microsoft's Learn landing page defines it as "an IT-governed, enterprise-grade platform for running code inside your Microsoft 365 tenant, with built-in sharing, live data connections, and easy app access." The Book of News describes it as "Microsoft-managed hosting and execution for applications," kept separate from wherever the app was written.

That separation drives the bill. An app can be written in Copilot Cowork, in Copilot Code, in Copilot Studio, with the runtime's CLI, or by an outside tool. Microsoft documents a path for publishing apps built in Lovable (see our Lovable page) and a quickstart for building with GitHub Copilot or Claude Code. Whichever tool produced the app, running it goes through one meter.

Who Pays to Run an App Someone Else Built?

The person running the app pays, through one of two routes. Microsoft's licensing and Copilot Credits page says running an app, "regardless of where you build it," requires "a Power Apps Premium license or Copilot Credits through a spending policy that includes Copilot Managed Runtime." The same page lists the licenses that don't qualify:

User has Can run apps?
Power Apps Premium Yes, no credits for normal use
A spending policy that includes Copilot Managed Runtime Yes, at 0.1 credits per API call
Power Apps use rights included with Microsoft 365 or Dynamics 365 No, "regardless of connector type"
Microsoft 365 Copilot license only No
Access to an app shared with them "Not by itself"

Sharing an app with a colleague hands them access to it. Who pays for the runtime is a separate setting. Microsoft's troubleshooting table names the symptom your help desk will see first: "Users with Microsoft 365 E3 or E5 can't run apps," because "Power Apps use rights included with Microsoft 365 or Dynamics 365 don't cover Copilot Managed Runtime."

Building is billed separately. Cowork and Code makers need a Microsoft Copilot license plus credits from a spending policy that includes those services, and the page warns that "building is the most credit-intensive part of the lifecycle." The Copilot Code admin page repeats it: Code "is a usage-based billing feature and requires a spending policy to be configured." We covered how that build-side meter began in Microsoft's New Copilot Bills Autopilot Outside the $30 Seat.

One trap for Copilot Studio shops: environment credits allocated in the Power Platform admin center pay for building, and they don't pay for running. Microsoft says "the environment-based billing policy for Copilot Studio doesn't cover credits needed to run the app." A Studio app can sit in a fully funded environment and still be blocked for every user who lacks runtime coverage.


What Counts as an API Call?

An API call is any request the app makes to the platform, and a single launch makes several. Microsoft counts each static asset loaded at launch ("a script, style sheet or image") as one call, plus each connector read or write, each Dataverse call, and each publish. At 0.1 credits per call, one credit covers 10 calls, and Microsoft states that "US$1 buys 100 Copilot Credits." Apps that use Work IQ APIs are "charged separately at their own rates" on top (our Microsoft Work IQ page tracks that service).

In Microsoft's own worked examples, every user stays within a 100-credit (US$1) monthly limit. Using a conservative 10 calls per launch, the licensing page estimates:

Example Users Usage Approx. cost per month
Personal productivity app 1 3 launches a day, 5 data calls each US$0.99
Team tracker 25 2 launches a day, 10 data calls each US$22.00
Department request app 300 1 launch a day, 8 data calls each US$118.80

Compare that with the license route. Power Apps Premium lists at $20.00 per user per month, paid yearly, or $12.00 with a 2,000-seat minimum. Licensing the 300 people in Microsoft's department example at list would cost $6,000 a month against the $118.80 the credit meter estimates. At $0.01 a credit, $20 buys 2,000 credits, or 20,000 API calls a month. A user has to make roughly that many calls before the Premium seat pays for itself on runtime alone.

So credits are the cheaper route for nearly everyone. Premium is the right answer for people who already hold it. Microsoft says you don't need to exclude them from a broad policy: "When a user has both a Premium license and coverage through a spending policy, Premium is used." Premium usage still draws against the daily cap that the Power Platform request limits page sets at 40,000 requests per user per 24 hours, and the page says it covers apps built in Cowork. Microsoft calls hitting that cap "highly unlikely."

The number to watch is the user count. A department app that its maker shares through an org-wide link stops being a 300-user estimate, and the policy limit is the only thing bounding what it costs. Microsoft's guidance is to treat spending policies as limits: "A policy doesn't reserve or allocate credits to anyone, and you pay only for what is actually consumed."

How Do Spending Policies Resolve?

The policy with the highest per-user limit wins, and a user who hits it is blocked rather than moved to another policy. Microsoft's rules for overlapping policies are specific:

  1. Only one policy applies per user per service. The highest per-user monthly limit wins, then the highest policy limit, then the most recently created.
  2. "When a user reaches their limit, they don't fall back to another policy. They can request more credits."
  3. Moving a user to another group mid-month doesn't reset consumption.
  4. Limits reset on the first of the month.

Microsoft recommends one all-users policy at 100 credits, then group policies for heavy cohorts, "for example 1,000 credits (US$10) a month." Billing draws prepaid capacity packs first, then a Pre-Purchase Plan, then pay-as-you-go. A capacity pack holds 25,000 credits a month, and the licensing page tells you to "turn on a pay-as-you-go meter so users aren't blocked when prepaid credits run out." These policies live in the same Cost management screen we walked through in Microsoft Adds Hard Spending Caps for Copilot Studio Agents.


Which Defaults Should IT Review Before December?

Most of the runtime's defaults are restrictive. Sharing and Copilot Code's auto-approve are two that start open. The governance defaults page says every app inherits a Microsoft-managed default environment group that "scopes to Everyone" and can't be deleted.

Connectors. The default allow list holds 19 Microsoft first-party connectors that authenticate only through Entra ID, plus 12 Microsoft MCP servers. Third-party, ISV and custom connectors are "excluded by design." Even on approved connectors, open-ended "Send an HTTP request" actions, Excel's "Run script" and Dataverse's arbitrary unbound actions are blocked. If you select "Edit this policy" to take full control, automatic updates from Microsoft stop.

Sharing. An app is private until its owner shares it, but "Allow organization-wide sharing" defaults to On. With it on, an owner can create a link anyone in the organization can open, and "a recipient can pass the link on to other people in the organization." Guest sharing defaults to Off. Every recipient of an org-wide link is a runtime user who needs coverage.

External artifacts. Deploying artifacts built outside Microsoft's build system is "disabled by default." Microsoft adds that if you turn it on, "your organization is responsible for validating externally built artifacts." The Lovable path needs both this setting and CLI app creation enabled.

Routing. Every maker is routed into a personal environment, and Microsoft says "you can't turn off environment routing for Copilot Managed Runtime." If you already run Power Platform routing rules or advanced connector policies, the page says the runtime layers its rules on top without overriding them.

Copilot Code. The admin page lists the client defaults. The "Auto-approve setting" is On, which "controls whether users can let Copilot auto-approve permissions in Copilot Code instead of confirming each action." Execution runs in the cloud only by default, GitHub connections are Off, and organizational data from Microsoft Graph and Work IQ is "On for cloud; Off for local." Local sessions run in a sandbox that is required unless you configure otherwise, and it "fails closed." The page also warns that "if a user runs an app that Copilot Code built outside of a Copilot Code session, the sandbox doesn't restrict it."

Microsoft's own internal maker program dealt with the same questions at a scale of 20,000 builders; see Microsoft says Risk-O-Meter sorts agent builds green, yellow or red.

What to Do Before Copilot Code Ships

These are the actions with the shortest lead time. Start with billing, because without runtime coverage every shared app fails for the people it was shared with.

This Week:

  1. Turn on usage-based billing under Copilot > Cost management and create one "All users" policy with Copilot Managed Runtime selected, at 100 credits per user per month. Set policy alerts to a named budget owner.
  2. Pull the list of who holds Power Apps Premium today. Leave them in the broad policy, since Premium is applied first.
  3. Tell your help desk the exact error text, "You do not have enough credits to use this app," and the E3/E5 cause, so tickets route to the policy owner.

This Month:

  1. Decide whether "Allow organization-wide sharing" stays on. If it does, set a cohort policy and alert threshold for the departments most likely to share widely.
  2. Decide whether Copilot Code's auto-approve stays on for everyone or only for a pilot group, and confirm the sandbox policy is deployed to managed Windows 11 24H2+ and Mac devices.
  3. Size build-side spending policies for Cowork and Code makers separately from runtime, as Microsoft advises.
  4. If you build in Copilot Studio, check under Manage capacity which environments are still billed in the Power Platform admin center, and add runtime coverage for their users.

Before Renewal:

  1. Review the first full month of runtime consumption by app and user, and raise or lower cohort limits from real data.
  2. Publish the "Request more" approval path: who approves, what justification a maker gives before sharing an app widely, and who reviews consumption afterward.
  3. Keep external artifact deployment off until security has a written validation process for outside builds, and add third-party connectors one at a time with an owner for each.

The Bottom Line

Microsoft 365 licenses include Power Apps use rights, and the request limits page still budgets "Microsoft 365 apps with Power Platform access" at 6,000 requests a day. Copilot Managed Runtime excludes those rights and meters every launch instead. At Microsoft's published rate the meter is cheap per user. Total cost depends on how many people open each app, and with org-wide sharing on by default, makers decide that number unless you set the policy first.

Create the all-users runtime policy and decide on org-wide sharing before Copilot Code reaches general availability in December.

Continue Reading

Share:

Frequently Asked Questions

Does a Microsoft 365 Copilot license cover running Copilot Managed Runtime apps?

No. Microsoft's licensing page says a Copilot license on its own doesn't cover runtime. Each person running an app needs a Power Apps Premium license or inclusion in a spending policy that includes Copilot Managed Runtime.

Can Microsoft 365 E3 or E5 users run Copilot Managed Runtime apps?

Not with their bundled rights. Microsoft says Power Apps use rights included with Microsoft 365 or Dynamics 365 don't cover Copilot Managed Runtime, regardless of connector type. Add those users to a runtime spending policy.

How much does it cost to run a Copilot Managed Runtime app?

Runtime is billed at 0.1 Copilot Credits per API call, and US$1 buys 100 credits, so US$1 covers about 1,000 calls. Microsoft's conservative estimate for a 300-user department app is about US$118.80 a month. Work IQ APIs are billed separately.

When is Copilot Code generally available?

Microsoft's Ignite 2026 Book of News says Copilot Code will be generally available in December. Until then it is in the Frontier program. Copilot Managed Runtime, which hosts the apps, became generally available on November 17, 2026.

Is organization-wide sharing on by default for Copilot Managed Runtime apps?

Yes. Apps are private until shared, but the Allow organization-wide sharing setting defaults to On, and recipients of an org-wide link can pass it on. Guest sharing defaults to Off. Admins change it under Apps > Settings > Environment groups.

Newsletter

More on AI Governance & Risk, every Sunday

The week's enterprise AI news, AI Governance & Risk included, in one Sunday email.

Weekly, free. Unsubscribe any time. Privacy

Latest Articles

View All →