Copilot Managed Runtime Pricing

Copilot Managed Runtime pricing is not one platform fee: 10,000 billed API calls use 1,000 Copilot Credits, or $10 at the $0.01 pay-as-you-go rate, and that $10 covers only the API-call component. Budget app creation, launches, hosting, management, AI services, and user licensing on separate lines.

Copilot Managed Runtime Pricing at a Glance

Copilot Managed Runtime splits the bill between what happens while an app is built and what happens after people start using it. It is a Microsoft-operated host for internal apps, with Microsoft Entra identity, governed data access, deployment, monitoring, and lifecycle controls built into the platform.

I verified these figures against Microsoft's live SDK, admin, pricing, and credit documentation on 26 September 2026. The September Copilot Credits Guide supplies the $0.01 credit price and planning ranges; the Managed Runtime SDK documentation supplies the API-call meter and licensing rule.

The blunt verdict: Power Apps Premium can remove the per-operation runtime meter for a licensed user, but it does not erase build, hosting, management, agent, or Work IQ charges. A budget that treats Premium as an all-inclusive runtime license is incomplete.

Copilot Managed Runtime Cost: The Six-Line Worksheet

The safest forecast has six lines, even when several begin as unknown. Combining them into one credits estimate hides the exact charge most likely to surprise you.

1. Creation and iteration. Cowork and Copilot Studio can consume credits while the maker prompts, tests, evaluates, and revises the app. Microsoft's rough build estimates run from 250-450 credits for a light app to 700-1,350+ for a heavy app.
2. App launches. A credit-funded user is charged whenever an app launches. Microsoft confirms the charge but does not publish the number of credits per launch on the current SDK, admin, pricing, or credit-guide pages. Put unknown in the sheet.
3. Runtime API calls. Each billed API call consumes 0.1 credit. At $0.01 per credit, the component costs $0.001 per call, $1 per 1,000 calls, or $10 per 10,000 calls.
4. Hosting and management. Microsoft bills the host, operational monitoring, and management through credits. Its public estimate bundles these with running the app, so a Premium user's residual hosting and management amount cannot be isolated from that estimate.
5. Agents and Work IQ. AI-powered runtime sits outside the Power Apps request entitlement. Work IQ tool actions consume 0.1 credit per call, while Work IQ chat/context work varies with the model, runtime, context, and tools.
6. Licenses. Add any Power Apps Premium seats and any Copilot license needed by the builder. A Cowork creator needs Microsoft Copilot, but a Managed Runtime end user follows the Power Apps Premium-or-credits rule.

The worksheet formula is:

monthly cost = licenses + $0.01 x (build credits + launch credits + API credits + host/management credits + AI credits)

The formula is useful precisely because it keeps unknown values visible. If a line cannot be estimated from tenant telemetry, leave it unknown and set a spending policy. Do not turn missing documentation into a zero.

Copilot Managed Runtime Credits: What Each Meter Covers

Copilot Credits are a common billing currency, not a single unit of work. One credit can be consumed by materially different activities, and several activities publish no fixed credit count.

For build work, Microsoft's guide gives planning bands rather than fixed prices. At the $0.01 pay-as-you-go rate, the light 250-450 credit example is $2.50-$4.50, the medium 400-750 example is $4-$7.50, and the heavy 700-1,350+ example is $7-$13.50+. These are estimates for the authoring work, not permanent app prices.

For the combined host, run, and manage line, the same conversion produces $0.10-$0.50 per app per month for a light app, $3-$5 for a medium app, and $30-$50 for a heavy app. Those numbers look low because they are rough planning examples, not a service commitment. More importantly, the bundled label prevents you from separating Premium-covered app operations from still-billable hosting and management.

The API meter is the only clean unit in the current Managed Runtime SDK page: 0.1 credit per call. Launches also consume credits, but their rate remains unpublished. AI services add their own meters. The cost model therefore has one fixed component surrounded by variable and unknown ones.

That distinction is the named limitation in Microsoft's current documentation: the inputs are current, but the public pages do not expose enough granularity to calculate one deterministic per-user or per-app total.

Power Apps Premium Managed Runtime: When the License Wins

Power Apps Premium coverage is most valuable when the user already has the license. In that case, covered app operations add no Copilot Credit charge until the user exceeds the applicable Power Platform request limit. The current entitlement is 40,000 requests per licensed user per 24 hours, and unused requests do not roll over.

The standard Power Apps Premium price is $20 per user per month, paid yearly. Microsoft also lists $12 per user per month, paid yearly, with a 2,000-seat minimum. That volume offer is a minimum annual commitment of $288,000, so it is not a cheap way for a small team to buy runtime coverage.

For a new buyer, the cleanest break-even uses only the published API rate:

• 20,000 billed API calls cost $20 at pay-as-you-go, equal to one standard Premium seat's monthly equivalent.
• 12,000 billed API calls cost $12, equal to the volume-seat monthly equivalent before accounting for its 2,000-seat minimum.

These are ceilings on the API-call-only crossover, not complete platform break-evens. Pay-as-you-go also charges for app launches, and both paths can still incur hosting, management, agents, and Work IQ costs. Any nonzero launch charge makes the credit-funded path reach $20 before 20,000 calls.

Power Apps requests also do not map neatly to Managed Runtime API-call credits. Microsoft's request-limit documentation counts connector and Dataverse work, including internal operations needed to complete transactions. Use the 40,000 figure as an entitlement boundary, not as a promise that every app interaction equals one request.

Do not confuse this license with the Microsoft 365 Copilot seat. If the buying question is the assistant inside Excel, that is a separate decision covered in the AI for Excel comparison. Managed Runtime app users follow the Power Apps Premium-or-credits rule.

The Public Preview Is Paid, Not a Free Plan

Copilot Managed Runtime entered Paid Public Preview on 25 September 2026. Microsoft's preview terms allow it to change the price, business model, service, functionality, or availability before general availability.

The preview includes a short insufficient-credit grace behavior, not a free tier. A user without enough credits first receives a warning and can continue without charge. Access is then blocked after 20 app operations or five minutes, whichever happens first. The admin documentation states that Power Apps Premium users are outside this credit requirement for their covered app operations.

Nobody should budget a production Managed Runtime app at $0 from the current documents. An existing Premium user may have $0 incremental cost for covered app operations, but the app can still incur build, hosting, management, agent, and Work IQ credits. The free Power Apps Developer Plan is for building and testing in a non-production environment; it is not a free Managed Runtime production plan.

Put Each Policy in the Right Admin Screen

The build bill and the runtime bill live in different administrative scopes. Mixing them in one environment policy is the fastest way to think a cost cap exists when it does not.

1. 1

   Set the creation-path control

   In the Microsoft 365 admin center, go to Apps > Overview > Set up app creation spaces. Cowork creation is governed through Frontier onboarding, CLI creation is off by default, and Copilot Studio app creation is on by default during public preview.

2. 2

   Fund Cowork builders per user

   In Copilot > Cost management in the Microsoft 365 admin center, include each creator in a spending policy that selects Cowork. A Microsoft Copilot license gives access to Cowork, but it does not include Cowork usage. Building and iterating consume Copilot Credits through the creator's policy.

3. 3

   Fund Copilot Studio build work per environment

   Use the Power Platform admin center, or PPAC, for Copilot Studio build billing. Natural-language authoring, testing, evaluation, and preview in the GitHub Copilot-powered authoring mode consume credits through the environment's billing configuration. Manual non-LLM configuration does not.

4. 4

   Fund app runtime per user

   Return to Copilot > Cost management in the Microsoft 365 admin center and create a separate runtime policy for the people who use the app. This per-user runtime policy applies whether the app came from Cowork, Copilot Studio, or the CLI. Copilot Studio's environment-based agent runtime model does not replace it.

The Copilot Cost management dashboard can apply organization and user limits, alerts, billing methods, and request routing. Its Consumption view breaks usage down by policy, user, group, service, agent, and funding source. That is where the unknown launch and variable runtime amounts become measurable tenant data.

Choose Pay-As-You-Go, a Capacity Pack, or P3

Pay-as-you-go is the safest starting point for a new app because it is post-paid at $0.01 per credit with no upfront commitment. It avoids prepaying for a demand curve you have not observed.

Microsoft's live Copilot Studio pricing page also lists a tenant-wide capacity pack with 25,000 Copilot Credits for $200 per month. At full use, that is $0.008 per credit. The same 25,000 credits would cost $250 at pay-as-you-go, so full use saves $50, or 20%. The simple monthly break-even is 20,000 credits: below that, $0.01 pay-as-you-go costs less than a $200 pack; above it, a fully applicable pack can cost less. Confirm in the tenant's billing configuration that the pack is allocable to the Managed Runtime workload before using that saving in a budget.

The Copilot Credit Pre-Purchase Plan, or P3, is for predictable annual demand. It is paid upfront for one year, unused credits expire at the end of the term, and an exhausted balance requires more credits or pay-as-you-go coverage. The published tiers are:

• 300,000 credits at 5% discount
• 1,500,000 at 6%
• 3,000,000 at 7%
• 15,000,000 at 8%
• 30,000,000 at 10%
• 75,000,000 at 12%
• 150,000,000 at 14%
• 225,000,000 at 17%
• 300,000,000 at 20%

The annual-lock risk is unused capacity, not just cash timing. A nominal discount loses value when credits expire. Do not move from pay-as-you-go to P3 until the Consumption view shows enough stable use to clear the chosen tier.

Three hidden costs remain under every funding method:

• Launch pricing is unpublished. Measure it; do not assume it is immaterial.
• The host/run/manage estimate is bundled. Premium coverage does not let you calculate the hosting and management residual from Microsoft's public range.
• AI services remain separate. Agents, Work IQ queries, and other separately billed services can exceed the non-AI app-operation line.

The Runtime Is Available Before Copilot Code

Copilot Managed Runtime's public preview is already available, subject to tenant eligibility and creation-path controls. Microsoft's 25 September launch post gave different timing for the surrounding experiences: Copilot Code would begin rolling out through Frontier in the coming weeks, while Autopilot was expanding to private preview at the end of the month.

Do not use the Code rollout date as the Runtime start date. The host and SDK can be evaluated now, while a specific Copilot creation interface may still require Frontier access or a later rollout.

Your Monday Budget Move

Start with one small internal app and make every meter visible before broad distribution. The Monday move is a worksheet and three policies, not a platform-wide launch.

1. List the builders and end users, then mark who already has Power Apps Premium and Microsoft Copilot.
2. Create separate worksheet rows for build, launch, API calls, hosting/management, AI services, and licenses. Enter unknown for the launch rate and any host/management residual you cannot isolate.
3. Start variable demand on $0.01 pay-as-you-go. Consider a $200 capacity pack only after monthly eligible use consistently exceeds 20,000 credits. Consider P3 only after annual demand is stable enough to consume the full tier.
4. Put Cowork builders in a per-user build policy, Copilot Studio build work in its PPAC environment, and app users in a separate per-user runtime policy.
5. Review consumption after the pilot. Replace unknowns with observed tenant usage, then decide whether Premium seats, credits, or a mix is cheaper for each user group.

The final choice is straightforward. Existing Power Apps Premium users should use their covered app operations and fund the uncovered lines. Low or uncertain usage should stay on pay-as-you-go. Predictable usage can move to a pack or P3 only when utilization, not the headline discount, supports it.

Copilot Managed Runtime Pricing FAQ

How much does Copilot cost to run?

Copilot Managed Runtime has no single run price. Pay-as-you-go costs $0.01 per credit; 10,000 billed API calls cost $10 for the API component, while launches, hosting, management, and AI services add separate amounts.

How to check Copilot usage cost?

Open Copilot > Cost management in the Microsoft 365 admin center, then use Overview and Consumption to inspect credits by policy, user, group, service, agent, and funding source. Copilot Studio build billing is managed separately by environment in PPAC.

How much does Copilot Studio cost per agent?

There is no universal per-agent price. Microsoft meters credit consumption by what the agent does and lists pay-as-you-go at $0.01 per credit plus a $200 monthly capacity pack containing 25,000 credits.

Do you have to pay extra for copilot agents?

Often, yes. Some agent runtime in Microsoft channels is included under specific licenses and execution modes with fair-use limits, but agent use inside Managed Runtime and Work IQ API access are separately billed through Copilot Credits.

What is the difference between a copilot agent and a copilot studio agent?

"Copilot agent" is the broad category. A Copilot Studio agent is created and managed through Microsoft's dedicated agent-building product, with its own execution model, environment, publishing, and credit rules. Managed Runtime apps can call agents, but that agent activity remains a separate cost line.

Do I need Copilot Studio to build an agent?

No. Microsoft also provides agent creation through Microsoft Copilot experiences. Copilot Studio is the choice when you need its dedicated build environment, execution options, governance, and environment-based billing.

Is Copilot as good as Chatgpt?

That comparison does not answer the Runtime buying question. Copilot Managed Runtime is governed hosting for internal apps, while ChatGPT is an assistant product; choose the runtime for deployment, identity, data access, and administration rather than chat-model preference.

Do you need a Copilot license to use a Copilot agent?

It depends on the experience. A Cowork builder needs Microsoft Copilot plus separately funded credits. A Managed Runtime app user needs Power Apps Premium or Managed Application Copilot Credits; a Microsoft Copilot seat is not the universal runtime entitlement.

Will the price of Azure increase in 2026?

The Managed Runtime launch does not announce an Azure-wide price increase. Copilot Credit purchases can connect to Azure billing and qualifying commitments, but the published Managed Runtime calculation uses Copilot Credits, not a general Azure price change.

Is Copilot Managed Runtime free?

No production free plan is published. The preview warning allows only 20 app operations or five minutes without sufficient credits before access is blocked; an existing Power Apps Premium license covers eligible app operations, not hosting, management, or separately billed AI.

Does Copilot Managed Runtime offer a student discount?

Microsoft does not publish a dedicated student rate for this enterprise runtime in the pricing and licensing pages verified on 26 September 2026. Education agreements may have separate terms, so an institution should check its Microsoft agreement rather than assume a consumer discount applies.

Can I get a refund for unused Copilot Credits?

Microsoft's current guide does not promise a refund. It says unused P3 credits expire at the end of the one-year term, so treat the committed amount as use-it-or-lose-it unless your contract states otherwise.

Did Copilot Managed Runtime pricing change?

This is launch pricing. Microsoft introduced the runtime on 25 September 2026 and published it as a Paid Public Preview, with an explicit warning that pricing and the business model can change before general availability.

Get the AI Business Workflow Audit Checklist

A practical checklist for finding costly steps, choosing the right automation model, and budgeting the workflow before it scales.