Should we turn on pay-as-you-go for SharePoint agents?

You’re right to treat “just switch on pay-as-you-go” as a FinOps decision, not a favour to makers. Metered access without seats can be the right tool — or a quiet way to turn every chatty site agent into a line on the Azure invoice.

Here’s what’s happening. Microsoft’s pay-as-you-go path for Microsoft Copilot Chat and SharePoint agents bills consumption (Copilot Credits / messages) through an Azure subscription you link in the Microsoft 365 admin centre. Users without a Copilot add-on can still reach work-grounded agents when they’re covered by a billing policy; for SharePoint agents, access for non-licensed users is gated by the security group on that policy. Creating a policy isn’t enough — you must connect it to the Copilot Chat or SharePoint agents service. You can set a budget and email alerts, but Learn is blunt: reaching 100% of the budget does not stop the service or billing. The reliable off-switch is disconnecting the payment method / billing connection.

This is First Law thinking for money: don’t put spend into a meter unless you can see how it comes back out — owner, cohort, alert path, and a reclaim rule. 12 Panes puts Cost & Value in the Steady base before maker freedom becomes tenant-wide.

Practical options:

1. Pilot PAYGO with a tight security group. One billing policy, named makers and pilot users only, Azure Cost Management alerts plus admin-centre budget emails, weekly message-consumption review. Best balance for most organisations.
2. Prepaid Copilot capacity packs (where available for Copilot Chat) with optional PAYGO overage. Predictable floor; still needs ownership of the credit pool. SharePoint agents may still lean on PAYGO — check the capacity-pack guidance for your service.
3. “All users” PAYGO so nobody waits for a licence. Politically easy. Economically, one viral site agent becomes everyone’s problem. I’d avoid this until Steady Cost holds.
4. Refuse PAYGO and buy seats only. Cleaner procurement story; slower for Chat-only cohorts. Fine if Wave 0 already decided seats are the only path.

The caution: Product names, credit rates, and which services accept prepaid packs move. Budget alerts are warnings, not circuit breakers. Re-check Set up Microsoft Copilot pay-as-you-go services, Manage access to agents in SharePoint, and Copilot Studio billing-rates guidance before you connect anything.

I’d suggest telling Finance and makers the same sentence: we’ll enable PAYGO for a named pilot group with a budget alert and a Friday kill-switch rehearsal (disconnect the policy). Broad “all users” metering waits until Cost & Value has a register of agents, owners, and expected credit burn.

You’re asking the right question — a calmer invoice beats a surprised board pack.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer