Copilot Credits Without an IT Team: Three Numbers to Check Before Your First Agent Goes Live

Our Copilot Credits reference explains what every Microsoft workload costs. This is the field version, for the person at a 10 to 60 person firm who became the Microsoft 365 admin by default: the office manager, the practice manager, the partner who likes technology. You are about to publish an agent, or you have one running that nobody budgeted for, and you do not need to understand the whole of Microsoft’s guide. You need three numbers before go-live, and a fourth check that is not a number. All of them live in your admin centres or in Microsoft’s free estimator, and none takes longer than an afternoon.

Microsoft prices below are US dollar list at September 2026, with an approximate sterling figure. Check Microsoft’s UK pricing page before anything reaches a budget.

Number one: how many of the agent’s users hold a Copilot licence

Why it matters. On the standard and Copilot Chat harnesses in Copilot Studio, an internal user with a Microsoft Copilot licence draws no credits when they use the agent, within fair use. Everyone else draws credits per response. So the same agent can cost nothing a month or £50 a month depending on who is talking to it, and the licence count is the first thing that decides which.

Where to find it. The licences view in the Microsoft 365 admin centre. Count the people who will actually use the agent, not the whole firm. Five licensed partners asking it questions is a different bill from twenty unlicensed staff doing the same. If the count points to licensing a few more people, Copilot Business is $21 per user per month on an annual plan, about £16, with no minimum seat count, and our Copilot Basic vs Premium post sets out who should hold one.

The trap. This applies only to the classic harnesses. Copilot Studio’s new default is the GitHub Copilot harness, and the licence covers none of it: credits are consumed while the agent is built and every time it runs, whoever is using it. To check which harness an agent is on, open it in Copilot Studio. An agent on the new harness has build, preview, evaluate and monitor tabs and is written in skills. A classic agent sits under other ways to build and is written in topics. If yours is on the new harness, number two changes shape, and our guide to which harness an agent belongs on explains whether it should be there at all.

Number two: the credits per conversation for this agent’s design

Why it matters. Two agents that look identical to the person using them can differ six-fold in cost. On the standard harness, an answer grounded on SharePoint or other Microsoft 365 content is 12 credits. An answer from uploaded files or a website is 2. Every tool the agent calls, a flow, a connector, a prompt, adds 5. The design decides the meter.

Where to find it. Microsoft’s Copilot Credit Estimator for agents. Put in the number of unlicensed users, conversations a month, the share that use knowledge and how many tools fire, and it gives a monthly credit figure. Multiply by $0.01 for pay as you go, roughly three quarters of a penny a credit. Microsoft’s own wording is that the estimator makes no guarantee of final costs, so treat it as the scale of the bill, not the bill.

Here is the sum at this audience’s size. Fifteen unlicensed users at 20 conversations a month is 300 conversations. Half use knowledge. Of those, 75 pull from SharePoint at 12 credits and the other 75 answer from files at 2. The remaining 150 each call one tool at 5 credits. That is 1,800 credits a month, $18, about £13.50. Allow three exchanges per conversation and it is still only about 5,400 credits, $54, about £40. Low thousands of credits, tens of dollars.

The trap. If the agent is on the GitHub Copilot harness, the per-response maths does not apply. Microsoft’s September 2026 guide gives per-run planning ranges instead: 100 to 300 credits for a light run, 300 to 500 for a medium one, more than 500 for heavy. That is $1 to $5 or more each time it runs, and building it in natural language draws credits too, 1 to 60 or more per authoring session. A daily medium-weight automation on the new harness is roughly $90 to $150 a month, £70 to £110, before anyone has used it interactively. The harness decision is a cost decision. For a first agent the classic harness is usually the right one, and our post on what the new engine changes explains why the meter runs faster there.

One rule for either harness: below 20,000 credits a month, stay on pay as you go. Do not buy the $200 capacity pack for a first agent. It resets monthly and unused credits vanish.

Number three: the monthly spend cap set before you publish

Why it matters. Pay as you go is billed in arrears and has no ceiling unless you set one. For a firm with no IT team, the cap is the safety net. It turns “what might this cost” into a number you chose.

Where to find it. Two admin centres, in a sequence small firms have most often not completed. Pay as you go is switched on in the Power Platform admin centre and needs an Azure subscription linked to it. If the firm has never used Azure, that subscription is the step that is missing. Once the meter is on, spend policies and usage thresholds live in the Microsoft 365 admin centre, next to the consumption report that shows credits by workload and by agent. So the order is: link an Azure subscription, enable the meter, set the threshold, then publish.

The trap. Setting the cap after go-live. Set a first-month threshold that is deliberately low, £50 or so, which is about 6,500 credits and more than the worked example above needs. Put a calendar reminder in for two weeks after publish to open the consumption report and see what the agent actually drew. Then raise the threshold to something with headroom. A cap you never hit is doing its job.

The fourth check, which is not a number

The connector tier. We have seen a build get underway, the team discover that the connector to the system they needed was premium, and the whole thing pause while someone found out what a Power Automate Premium licence was and got the spend approved. Nothing was wrong with the design. Nobody had checked.

Standard connectors, SharePoint, Outlook, Teams, OneDrive, Forms and Planner among them, cost nothing extra. Premium connectors, SQL, HTTP, Dataverse, custom connectors and most non-Microsoft systems, need Power Automate Premium at $15 per user per month on an annual plan, about £11, for every user who runs a flow that touches one, or $0.60 a run, about 45p, on pay as you go. The check takes two minutes on Microsoft’s connector reference, where every connector is marked standard or premium. Do it before the build starts, not during it. Our Copilot Studio vs Power Automate post covers where flows sit in an agent build.

One date to add. On 1 November 2026 the AI Builder credits that came seeded with Power Automate Premium and Process licences are being removed. A document-processing step that relies on AI Builder will draw Copilot Credits or need a paid add-on from then, so from November it belongs in number two.

Who owns these numbers afterwards

The three numbers do not stay still. People join and leave, and the licence count moves. The agent gains a knowledge source, and the credits per conversation move. Word gets round and usage grows past the cap. Somebody has to re-check all three every quarter, and the first time an agent stops working because a threshold was hit is usually the moment a firm realises nobody was. What happens after the agent is built is about that role, and the Embed retainer exists for firms that would rather the re-checking was ours. For a whole year of these numbers added up for one firm, see what a first agent costs a 30-person firm in year one.

The next step

If you would like to be able to run these checks yourself, that is what the Enable agent workshop is for: three hours, hands-on in your own tenant, from £850. If you would rather someone checked them with you before you press publish, book a free consultation and bring the agent.

Sources checked

Last checked: 12 September 2026. Microsoft prices are US dollar list at September 2026 and subject to change. Sterling figures are approximate.

• Microsoft, Copilot Credits Guide, September 2026
• Microsoft, Copilot Credit Estimator
• Microsoft Learn, standard harness licensing in Copilot Studio
• Microsoft Learn, connector reference
• Anders Jensen, Copilot Studio pricing 2026, including per-feature rates
• Citizen Development Academy, Power Automate pay as you go rates, June 2026
• PlugJunction, the November 2026 AI Builder change