Power Apps Premium vs Copilot Credits: 8-Step Guide

TL;DR: Every person who runs an app on Copilot Managed Runtime needs Power Apps Premium or Copilot Credits. Each API call costs 0.1 credits, about $0.001 at pay-as-you-go rates, so a $20 Premium seat only pays off above roughly 20,000 calls a month. Meter most users with credits and license the heaviest ones.

The Power Apps Premium vs Copilot Credits decision arrived with Copilot Managed Runtime, which Microsoft began rolling out in public preview in late September 2026. Apps built in Copilot Cowork, Microsoft Copilot Studio or Copilot Code run there, and the Power Apps rights in Microsoft 365 don't cover them. With App Builder apps moving off vibe.powerapps.com by November 30 and Premium rising to $22 on January 1, 2027, every app user is now a budget line.

Copilot Managed Runtime is Microsoft's hosting layer for internal line-of-business apps, with Microsoft Entra sign-in, your data loss prevention policies and admin center inventory built in from the moment an app is created.

Who is this guide for, and what will you have at the end?

This guide is for Microsoft 365 and Power Platform administrators, IT finance owners and CIOs whose teams build apps in Cowork or Copilot Studio, where apps now sit alongside workflows and agents. By the end you will have an app inventory, a capped runtime spending policy, a usage baseline per user and a short list of people who should hold Power Apps Premium.

What do you need before you start?

You need an admin who can create spending policies, a billing method for Copilot Credits and two to four weeks of real app usage.

Power Apps Premium vs Copilot Credits: which should run each user's apps?

Use Copilot Credits for people who open apps occasionally or a few times a day, and Power Apps Premium for people who work in apps all day or already hold Premium. Most organizations need both.

Runtime is measured in API calls: launching an app, reading or writing a record through a connector, or publishing. Each call consumes 0.1 Copilot Credits. Premium holders consume none until they pass 40,000 Power Platform requests per user per 24 hours.

Start with this decision matrix. Call volumes come from a 2toLead illustrative model; replace them with your numbers after step 6.

In education, nonprofit and healthcare, students, volunteers and seasonal staff rarely justify a seat but can still use a governed app on credits.

How much does Copilot Managed Runtime cost per user?

Copilot Managed Runtime cost is about $1 per 1,000 API calls at the $0.01 pay-as-you-go credit rate, and about $0.80 per 1,000 calls with capacity packs. A $20 Power Apps Premium seat covers the same runtime, so the breakeven sits near 20,000 calls per user per month, roughly 950 calls each working day.

Microsoft's current guidance sets a minimum per-user limit of 2,000 credits a month: 20,000 calls, or $20 at pay-as-you-go rates. A runtime-only policy therefore caps a credit-funded user near the price of a Premium seat, but a user who hits the cap loses access until next month. That is the real reason heavy users belong on Premium: continuity, not just cost.

Building is billed separately: Cowork needs a Microsoft Copilot license plus credits, and Copilot Studio charges credits per environment from the first prompt. Our view on who should own the Copilot Credits meter applies to both.

How do you license managed apps in eight steps?

Inventory apps, meter every user on credits for a few weeks, then move only heavy users to Power Apps Premium. Setup takes about two hours, plus the measurement window.

1. List every managed app and its owner. In the Microsoft 365 admin center, go to Apps > All apps. Open each app's Usage and Data & tools tabs. Expected result: Apps listed with owners, connectors and Work IQ dependencies.
2. Find app users who already hold Power Apps Premium. Go to Billing > Licenses, select Power Apps Premium and note the assigned users. Expected result: You won't pay twice for users already covered.
3. Create a security group for credit-funded app users. In the Microsoft Entra admin center, go to Groups > All groups > New group, choose Security and add every app user without Premium. Expected result: One group that scopes your runtime budget.
4. Add a runtime-only spending policy. In the Microsoft 365 admin center, go to Copilot > Cost management > Configuration > + Add spending policy. Select Specific groups and your group. Under Select agents and services, select only Copilot Managed Runtime and turn off Auto-apply new services. Expected result: A policy that covers app runtime and nothing else.
5. Set the per-user cap and alerts, then create the policy. Choose Limited monthly budget, set a 2,000-credit per-user limit and 80% alerts for admins and users, then select Create spending policy. Expected result: The policy appears on the Configuration tab and applies to the group immediately.
6. Read per-user consumption after two to four weeks. Go to Copilot > Cost management > Consumption, open the Users view and export it. Expected result: Real monthly credits per user, ready to compare with the breakeven table.
7. Move heavy users to Power Apps Premium. For anyone trending above 1,600 credits a month, go to Billing > Licenses > Power Apps Premium > Assign licenses, then remove them from the credits group. Expected result: Their runtime stops drawing credits and can't be capped mid-month.
8. Review the meter every month. On the Overview tab, check Top actions for users near their limit and handle requests under View requests. Expected result: A monthly decision record: who moves to Premium, who goes back to credits and why.

If Premium is the answer for some users, a purchase or renewal with a term starting before January 1, 2027 keeps the $20 price until that term ends.

What are the most common licensing mistakes, and how do you fix them?

Most mistakes come from assuming an existing license covers managed apps. It usually doesn't.

• Counting on Microsoft 365 or Dynamics 365 rights. Neither covers Copilot Managed Runtime. Put every runtime user on credits or Premium.
• Buying Microsoft 365 Copilot licenses to run apps. Only Cowork app builders need one, as our December 2026 Copilot licensing guide explains.
• Sharing one cap between Cowork and apps. A busy Cowork month can lock people out of their apps. Keep runtime in its own policy.
• Leaving Auto-apply new services on. Future services will draw on your runtime budget.
• Sharing apps before licensing users. Sharing grants access, not a license. In preview, unlicensed users are blocked after 20 app operations or five minutes.

Apps that reach business data through Work IQ add their own charges. Our plan for Dynamics 365 data in Work IQ covers that side of the bill.

How do you check that the licensing works?

It works when credit-funded users appear under your runtime policy, Premium users don't, and nobody is blocked unexpectedly. Check the next day; consumption refreshes every two hours.

• Have a credit-funded user open an app and save a record, then confirm usage in the Policies view.
• Have a Premium user do the same and confirm no runtime credits appear.
• Confirm the policy covers only Copilot Managed Runtime, with Auto-apply new services off.
• Confirm Top actions shows no users at their limit in the first week.

How do you measure the value of your app licensing?

Measure cost per active app user, cost per completed transaction and hours returned, against a Premium-for-everyone baseline so finance sees the decision, not just the bill.

In a 2toLead illustrative model, a 500-person manufacturer has 400 occasional app users, 90 daily tracker users and 10 all-day operators. Premium for everyone costs $10,000 a month, or $11,000 after a 2027 renewal. Credits for the 490 lighter users come to 269,000 calls, or 26,900 credits, which is $269 at pay-as-you-go rates. Add Premium for the 10 operators at $200 and the total is $469 a month, about $5,600 a year.

If the shift handover tracker saves each daily user 20 minutes a week, that is about 130 hours a month, roughly $6,500 at $50 an hour, against $469 of runtime. Our guide to Copilot adoption metrics that prove value shows how to present hours returned to finance leaders.

Premium is a seat for people who live in your apps. Credits are a meter for everyone who visits them.

What do IT leaders ask about Power Apps Premium vs Copilot Credits?

The short answer: Premium for heavy and existing Premium users, credits for everyone else, and no Microsoft 365 Copilot license needed to run apps.

Do users need a Microsoft 365 Copilot license to run Copilot Managed Runtime apps?

No. Users need Power Apps Premium or Copilot Credits to run an app. Only people who build apps in Copilot Cowork need a Microsoft Copilot license, and building is billed separately.

Do Microsoft 365 E3, E5 or Dynamics 365 licenses cover managed apps?

No. The Power Apps use rights included with Microsoft 365 and Dynamics 365 don't provide access to apps hosted on Copilot Managed Runtime, whatever connectors the app uses. Power Apps per app and pay-as-you-go plans don't either.

How much does one Copilot Managed Runtime API call cost?

Each API call consumes 0.1 Copilot Credits. At the $0.01 pay-as-you-go credit rate, that is $0.001 per call, or $1 per 1,000 calls. Capacity packs and pre-purchase plans lower the effective rate.

When is Power Apps Premium cheaper than Copilot Credits?

Premium is cheaper when a user makes more than about 20,000 API calls a month at today's $20 price, or 22,000 after the January 1, 2027 increase. It also wins when the user already needs Premium for other Power Apps.

How can 2toLead help?

2toLead turns Copilot spend into governed, measurable outcomes for manufacturing, healthcare, education and nonprofit organizations. In a fixed-scope, three-week Managed Apps Licensing Sprint, our Microsoft MVP team will:

• Inventory every managed app, owner and data dependency
• Set up a runtime-only spending policy with caps and alerts
• Build a per-user breakeven model from two weeks of real usage
• Recommend who holds Power Apps Premium and who stays on credits
• Hand you a monthly scorecard for cost per user, cost per transaction and hours returned

For the full licensing rules, read Microsoft's Copilot Managed Runtime licensing FAQ.

To see where your makers will build next, our comparison of Copilot Chat, Cowork, Code and Autopilot is a good next read.

Find more practical guidance on the 2toLead Insights hub, or book a Managed Apps Licensing Sprint.

No hype. Just practical, governed AI that actually gets adopted.