Insight · Microsoft Fabric · AI Solutions

    Copilot Credits for Microsoft Fabric: What They Pay For and What an App Costs

    Microsoft announced Copilot Credits as a new way to pay for Fabric at Ignite 2026. What they cover today, the 0.005 credits per second rate, and what a Copilot app on Fabric costs a month.

    Nick de Vrye, CTOPublished 18 November 20265 min readMore on Fabric pricing and capacity
    Navy Solv Systems title card reading 'Copilot Credits for Fabric', with the Microsoft Fabric icon at the centre of a hub of Microsoft product icons: Microsoft Copilot, Copilot Studio, Power BI, Azure Cost Management, Azure SQL Database and Power Automate.

    In Short: What Changed?

    At Microsoft Ignite 2026 Microsoft introduced "Copilot Credits as a new usage-based billing option for Microsoft Fabric". The headline sounds broad, but the only mechanism Microsoft has documented is narrow:

    • What it covers: Fabric used as the data backend for apps hosted on Copilot Managed Runtime
    • Status: that integration is in Frontier public preview. Copilot Managed Runtime itself is generally available
    • Rate: 0.005 Copilot Credits per second of Fabric compute, adjusted for region and workload
    • Capacity: no Fabric capacity purchase is required
    • What it does not cover (yet): Spark, warehouses, pipelines, Power BI, or Copilot in Fabric, which still run on Fabric capacity

    What Copilot Managed Runtime Is

    Copilot Managed Runtime hosts apps that people build in Microsoft Copilot (Cowork and Code), in Copilot Studio and in compatible third-party tools. Many of those apps need somewhere to keep records: requests, approvals, stock counts, survey answers. The new Fabric integration gives them a ready-made backend, with a database, data APIs and storage, without anyone setting up a Fabric capacity first.

    That is why billing in Copilot Credits makes sense here. The person building the app may never have heard of an F SKU. Their organisation already pays for Copilot Credits, so the Fabric compute behind the app is charged to the same meter.

    How the Billing Works

    The Copilot Credits Guide (November 2026) says Fabric usage in this integration "is billed in Copilot Credits, based on the Fabric compute consumed by the app's SQL database and data APIs (GraphQL)". The base rate is 0.005 Copilot Credits per second.

    Final billing adjusts the base rate for three things:

    • Regional pricing
    • An on-demand multiplier
    • The consumption rate of each Fabric workload involved

    Turning credits into money

    Copilot Credits bought pay-as-you-go cost $0.01 each, per the same guide. So the base rate works out as:

    • 0.005 credits per second x 3,600 seconds = 18 credits per hour
    • 18 credits x $0.01 = $0.18 per hour of Fabric compute

    That is the same as the US pay-as-you-go price of one Fabric capacity unit for an hour, which is listed in our Fabric pricing guide. The difference is that you only pay while the app is actually using compute, not for a capacity that runs all month.

    Organisations that buy credits in bulk through the Copilot Credit Pre-Purchase Plan (tiers from 300,000 credits) or the new AI Flex Plan may pay less per credit. Microsoft notes that all pricing is in US dollars and subject to change.

    What an App Costs a Month

    Microsoft's guide gives rough planning estimates for three usage levels, excluding regional pricing. At the $0.01 pay-as-you-go price:

    • Light usage: about 250 to 550 credits a month, roughly $2.50 to $5.50
    • Medium usage: about 1,650 to 2,150 credits a month, roughly $16.50 to $21.50
    • Heavy usage: about 4,700 to 5,600 credits a month, roughly $47 to $56

    For comparison, the smallest Fabric capacity, an F2, costs about $263 a month pay-as-you-go or about $156 reserved. For a handful of small departmental apps, paying per second through Copilot Credits is far cheaper than buying a capacity just to host them.

    The comparison changes once you have a Fabric capacity anyway. If you already run an F64 for analytics, small apps can usually share it, and Fabric apps built directly on Fabric draw on that capacity's capacity units (CUs).

    What You Need

    According to the guide, users need one of these licences:

    • Power BI Pro
    • Power BI Premium Per User
    • Fabric (Free)

    The tenant also needs Copilot Credits usage-based billing turned on. Because the integration is a Frontier preview, it is aimed at organisations in Microsoft's early-access programme, so check availability in your tenant first.

    What Has Not Changed

    Copilot in Fabric and Power BI still uses capacity. Microsoft Learn still documents Copilot in Fabric as consuming Fabric CUs, metered per 1,000 tokens. Our guide to what Copilot in Fabric costs still applies.

    Your F SKU is still how you pay for analytics. Nothing Microsoft has published says Copilot Credits can pay for lakehouses, warehouses, Spark, pipelines or Power BI. If that changes, it will be a significant pricing shift, and we will update this page.

    What to Do Now

    1. Find out who builds apps in Copilot. If business teams are building apps in Cowork or Copilot Studio, their data will start landing in Fabric through this route. IT and data teams should know where it lands. 2. Set a Copilot Credits budget and alerts. Usage-based billing is easy to switch on and easy to forget. Our Copilot Credits explainer covers how credits are bought and tracked. 3. Keep capacity planning separate. Do not reduce your capacity plans on the strength of this announcement. Size analytics capacity as before, using our capacity sizing guide.

    Sources and Further Reading

    Frequently asked

    Only in one documented case so far. Microsoft's November 2026 Copilot Credits Guide says Fabric used as the backend for apps on Copilot Managed Runtime is billed in Copilot Credits, with no Fabric capacity purchase required. That integration is in Frontier public preview. Microsoft has not documented Copilot Credits paying for general Fabric workloads such as Spark, warehouses or Power BI.

    The base rate is 0.005 Copilot Credits per second of Fabric compute used by the app's SQL database and GraphQL data APIs. Final billing adjusts that base rate for regional pricing, an on-demand multiplier and each Fabric workload's consumption rate.

    Microsoft's rough planning estimates are about 250 to 550 Copilot Credits a month for light usage, 1,650 to 2,150 for medium and 4,700 to 5,600 for heavy, before regional pricing. At the $0.01 pay-as-you-go credit price that is roughly $2.50 to $56 a month.

    No. Copilot in Fabric and Power BI is still documented as consuming Fabric capacity units, metered per 1,000 tokens. Copilot Credits for Fabric only cover the Copilot Managed Runtime integration so far.

    According to Microsoft's Copilot Credits Guide, users need a Power BI Pro, Power BI Premium Per User or Fabric (Free) licence, and the tenant needs Copilot Credits usage-based billing turned on.