IT Partner switches on Microsoft 365 Copilot pay-as-you-go in your tenant so people without a Microsoft 365 Copilot seat can use agents in Copilot Chat, SharePoint agents and Copilot Studio agents, metered in Copilot Credits instead of licensed per user. In one to two days we check eligibility and admin roles, create the billing policy in the Microsoft 365 admin center against an Azure subscription in your own tenant, scope it to a security group, connect it to the pay-as-you-go services, add a Copilot Studio billing plan where you build your own agents, set the budget and alert recipients, and hand over a one-page guide to reading the spend and switching it off. The setup is free for organizations that buy their Microsoft licensing through IT Partner. The Copilot Credits themselves are Microsoft's metered charge — billed by Microsoft to your linked Azure subscription at Microsoft's published rate, $0.01 per credit at the time of writing — and are not part of this service. Other organizations get the same setup as a quoted engagement, or move their Microsoft billing to us first.
Microsoft 365 Copilot is licensed per user, but a growing share of what people actually ask for — an agent grounded in a SharePoint site, a Copilot Studio agent built for one team, an agent pinned in Copilot Chat — can be used by people who do not hold a Copilot seat, provided the tenant has pay-as-you-go billing switched on. Microsoft meters those interactions in Copilot Credits and bills them to an Azure subscription in your tenant at its published rate: $0.01 per credit at the time of writing, where a classic answer is 1 credit, a generative answer 2, an agent action 5 and each message grounded in your tenant's Microsoft Graph data 10 — so a typical SharePoint-agent exchange meters at about 12 credits. Users who do hold a Microsoft 365 Copilot license are not metered for agent use inside Copilot Chat, Teams and SharePoint; their seat already covers it, along with the built-in Researcher, Analyst and Facilitator agents. Pay-as-you-go is disabled by default in every tenant, which is why the request reaches our helpdesk as "can you set up Copilot pay-as-you-go credits for us?" The switch itself is a billing policy in the Microsoft 365 admin center (Copilot > Billing & usage — newer tenants show it under Copilot > Cost management as the classic billing and usage page): a name, an Azure subscription and resource group in the same tenant, a region, Microsoft's pay-as-you-go terms accepted, and a scope of either all users or one security group. The policy does nothing until it is connected to the pay-as-you-go services — Microsoft 365 Copilot Chat and SharePoint agents, with the Copilot Retrieval API in preview — and an unconnected policy is the single most common reason a tenant "has pay-as-you-go" and the agents still refuse to answer. The other traps are just as mundane: an Azure subscription that lives in a different tenant or carries a spending cap; a Microsoft 365 admin who is not Owner or Contributor on the subscription and resource group; an "all users" policy that blocks a group-scoped one until it is disconnected; and a budget that finance believed was a cap when Microsoft states plainly that it only sends alerts. Copilot Studio agents spend the same Copilot Credits but are enabled separately — a billing plan in the Power Platform admin center linked to the same Azure subscription and to the environments that host the agents — and Copilot Cowork, generally available since June 2026, bills in Copilot Credits through the usage-based billing controls in the Cost management node. We configure whichever of the three your users actually need, and leave the rest alone. We do this at no charge for organizations that buy their Microsoft licensing through IT Partner — the same relationship that already includes unlimited break-fix support during business hours, a policy published in our facts register. Two boundaries, stated plainly: the Copilot Credits are Microsoft's metered charge on your own Azure subscription, and this service does not resell, discount, cap or absorb them; and the setup is not agent building, Copilot deployment or a readiness project — those are separate services, and we tell you which one you need rather than stretching this one. If your Microsoft licensing runs through another partner or directly with Microsoft, we deliver the same two-day setup as a fixed-price engagement quoted in writing before work begins, or you move your CSP billing to us — free, with no tenant migration and no change to Microsoft's list prices — and the setup comes with it.
We confirm your licensing runs through IT Partner (or issue the fixed-price quote), agree which users need agents and why, and look for an Azure subscription in the same tenant — creating one in Microsoft's wizard, or provisioning an Azure plan through our CSP, if there is none. We also confirm who holds Global, Billing or AI Administrator in Microsoft 365 and who is Owner or Contributor on the subscription and resource group, and put anything that blocks the setup in writing before creating a thing.
Under Copilot > Billing & usage (or the classic page inside Cost management) we create the policy: name, subscription, resource group, region, Microsoft's pay-as-you-go terms accepted, scoped to the agreed security group. If an "all users" policy is already connected we disconnect it first — Microsoft will not attach a group-scoped policy alongside it.
On the pay-as-you-go services tab we connect Microsoft 365 Copilot Chat and SharePoint agents. Only if you build your own agents, we create the Copilot Studio billing plan in the Power Platform admin center and link the environments; where Cowork is in use, we enable usage-based billing in the Cost management node and set its spending policy.
We set the budget amount, reset period and alert recipients on the policy, mirror it with an Azure Cost Management budget on the resource group, and show your finance owner the Copilot Credits report in the admin center and the Azure cost analysis filtered to the Copilot Studio meter.
Three test accounts — licensed, unlicensed inside the group, unlicensed outside it — exercise a tenant-grounded agent so you see exactly who is metered and who is blocked. Consumption can take time to appear in Microsoft's reports; we tell you what to expect rather than wait it out on the clock.
A one-page document — alert recipients, how to read spend, how to widen or narrow the group, what a capacity pack or pre-purchase plan would change, and the disconnect steps with Microsoft's up-to-two-hour lag — walked through with your admins and finance owner on a short call. Any temporary access we were granted is removed.
It is free for organizations that buy their Microsoft licensing through IT Partner — that is the whole qualification. Customers kept asking for it, the work is a few engineer hours, and it belongs with the licensing relationship that already includes unlimited break-fix support during business hours. There is no catch on our side; the only money that changes hands is Microsoft's: the Copilot Credits your users consume are billed by Microsoft to your linked Azure subscription at its published rate, and we neither mark them up nor absorb them. If your licensing is elsewhere, the same setup is a fixed-price quote in writing, paid after you approve delivery — or you move your billing to us first and it comes with that.
Users without a Microsoft 365 Copilot license can use agents — an agent built in SharePoint, an agent published from Copilot Studio, an agent available in Copilot Chat — with each interaction metered in Copilot Credits instead of blocked. Copilot Chat itself is already available to your Microsoft 365 users; it is the agent grounded in your tenant's data that needs either a Copilot seat or a meter behind it. Licensed Copilot users are unaffected: their seat already covers agent use in Copilot Chat, Teams and SharePoint, plus the built-in Researcher, Analyst and Facilitator agents.
Microsoft's list rate is $0.01 per Copilot Credit on the pay-as-you-go meter, billed monthly in arrears to your Azure subscription. What an interaction costs depends on what the agent does: a classic answer is 1 credit, a generative answer 2, an agent action 5, and each message grounded in your tenant's Microsoft Graph data 10 — so a typical SharePoint-agent exchange meters at about 12 credits, roughly twelve cents. Those are Microsoft's published figures at the time of writing; we do not set them, mark them up or guarantee them. What we do is set up the spend report so you can read your own number after the first weeks and decide whether a seat, a capacity pack or the meter is the right shape.
Yes — the billing policy must point at an Azure subscription and resource group in the same Microsoft Entra tenant; that subscription is where Microsoft invoices the credits. If you have none, Microsoft's wizard can create one during the policy setup, which also makes you Owner of the subscription and resource group, or we provision an Azure plan through our CSP so the Azure consumption arrives alongside your licensing on an IT Partner invoice. A subscription in another tenant, or one carrying a spending cap or trial credit, cannot be used.
That message is Microsoft's way of saying the tenant's commerce runs through a partner and the subscription you offered was not provisioned through that channel. The fix sits with the partner: an Azure plan subscription provisioned through their CSP, and the policy pointed at it. If that partner is us, it is part of this setup. If it is someone else, they need to provision the Azure plan — or you move your CSP billing to IT Partner, which is free and changes nothing inside the tenant, and we do it.
A security group, unless you have a specific reason not to. Group scoping limits who can generate metered usage, ties the meter to a business decision rather than to anyone who finds an agent, and lets you add a second policy later for another cost centre. It also avoids a Microsoft rule that bites in the other direction: once an "all users" policy is connected, no group-scoped policy can attach until the broad one is disconnected. We create or reuse a group with you and record in the handover who owns its membership.
No — and it is important that finance hears this from us rather than from the invoice. Microsoft states that the budget on a billing policy only triggers alerts: usage continues after the amount is passed, and the alert email can take up to 24 hours. We set the budget and alert recipients anyway, mirror it with an Azure Cost Management budget on the resource group, and note in the handover which limits in your tenant actually stop usage and which only alert. If you need certainty, prepaid capacity changes the enforcement picture, and we explain that trade-off before you buy anything.
Capacity packs are prepaid blocks of 25,000 Copilot Credits per month at Microsoft's pack price; the Copilot Credit Pre-Purchase Plan is an annual commitment bought as an Azure reservation at a volume discount Microsoft publishes. Two things to know before choosing either: Microsoft requires pay-as-you-go to be enabled first for Copilot Chat and SharePoint agents, and when consumption exceeds the prepaid amount it rolls to pay-as-you-go automatically — so this setup is the prerequisite in every case. We can transact packs or a pre-purchase plan through our CSP when the spend justifies them, quoted separately at Microsoft's price, and we generally suggest running on the meter for a month or two first so the purchase is sized on your data rather than a guess.
Same currency, different switch. Copilot Studio agents consume Copilot Credits too, but pay-as-you-go for them is a billing plan in the Power Platform admin center linked to an Azure subscription and to the environments where the agents live, with an optional monthly consumption limit per agent. We set it up in the same visit when you build your own agents, pointing at the same Azure subscription so finance sees one meter. Building the agents is a separate service.
Cowork, generally available since June 2026, bills in Copilot Credits through the usage-based billing controls in the Copilot > Cost management node rather than through the classic billing policy — a billing method, a default spending policy, limits and alerts. Where your tenant offers it and your users are on it, we enable and configure it in the same setup. Microsoft is moving more AI experiences under that node over time; we configure what your tenant shows on the day and say so in the handover.
Disconnect the policy from the service, or disable pay-as-you-go entirely, on the same admin-center page — the steps are in the handover. Microsoft says it can take up to two hours for users to lose access to the agents, and consumption already recorded is still invoiced. Narrowing the security group is the gentler lever and takes effect the same way.
An account holding Global, Billing or AI Administrator in Microsoft 365 that is also Owner or Contributor on the Azure subscription and resource group — Microsoft's requirement, not ours. For licensing customers we usually work through the least-privilege delegated (GDAP) access already in place under our published access policy; otherwise a temporary role you grant and we ask you to revoke once the handover is done. We do not need, and do not ask for, standing global admin.
The listed duration is two days, and most of it is waiting on people rather than on Microsoft: the hands-on work is a few engineer hours once an Azure subscription and the right roles exist. Creating a subscription, provisioning an Azure plan, or chasing a role assignment adds calendar time, never cost.
Yes, two ways. The same two-day setup as a fixed-price engagement — quoted in writing before work begins, paid after you approve delivery — or move your Microsoft 365 CSP billing to IT Partner first: that switch is free, involves no tenant migration or downtime, keeps your subscriptions at Microsoft's published list prices with their existing term dates, and brings this setup and unlimited business-hours break-fix support with it. There is no lock-in either way; you can move your subscriptions to another partner at any time under Microsoft's own transfer workflow.