A request I keep hearing lately: give certain users access to Microsoft 365 Copilot agents, but without handing out full Copilot licences to everyone. Copilot pay-as-you-go now makes that possible. Users can work with tenant-grounded Copilot agents in Copilot Chat, and the usage is billed straight to an Azure subscription. That opens the door to targeted pilots and controlled expansion. It also brings new risks, because without clear governance you end up with surprise bills and messy permissions very quickly.

Pay-as-you-go is switched on in the admin center and billed through Azure

The setup itself is simple. The real effort goes into access and cost controls. You enable the feature in the Microsoft 365 admin center under Copilot → Billing & usage → Pay-as-you-go, where you also link an Azure subscription for metered billing. In practice, only subscriptions with Azure Cost Management enabled make sense here, since you'll want budget alerts and reporting to keep things under control. You can allow pay-as-you-go for specific agents and decide exactly which users or groups are eligible. Most organisations should start small, maybe with a pilot group or a few business units, before opening it up more widely.

Precise control over users and agents prevents most problems

In large tenants especially, you need to decide early on who gets Copilot pay-as-you-go and which agents they can reach. This is handled per agent in the admin center, and you can grant permissions to individual users, groups or roles. That level of detail matters, both for security and for keeping costs from running away. What has worked best for me is a dedicated group for pay-as-you-go pilot users, with access restricted to that group. You can then watch how the pilot plays out and adjust step by step instead of enabling everyone by default.

Pro tip: Use clear naming conventions for groups enabled for pay-as-you-go access, and document who can use which agents. Troubleshooting and later audits get a lot easier that way.

Azure Cost Management takes care of budgets and alerts

Because all billing goes through Azure, anyone already using its cost controls has a head start. In the Azure portal, under Cost Management + Billing → Budgets, you can set a monthly budget for the linked subscription and configure alerts at thresholds of your choosing. Azure Action Groups let you send those alerts to IT, finance or both. Microsoft has a walkthrough in How to create and manage Azure budgets.

A setup I've seen work well:

  • Set a monthly budget per pay-as-you-go subscription
  • Alerts at 50%, 80%, and 100% thresholds
  • Notifications to admins and business owners
  • Regular review of usage per user in Azure Cost Analysis
  • Document which agents and groups are enabled for pay-as-you-go

If you need more detailed reporting, export the data to a Log Analytics workspace or Power BI. That gives you fine-grained analysis and a basis for internal chargebacks.

Regular monitoring keeps surprise bills away

The biggest danger with Copilot pay-as-you-go is overspending by accident, particularly when a few users get very active. Budgets and alerts are a must, but you should also check regularly who has access and what is being spent. Technical enforcement of limits is described in the official Copilot pay-as-you-go documentation. In the tenants I work with, I insist on a monthly check-in that looks at usage and spend per agent and per user. Azure Cost Analysis does most of the work here, and for more advanced tracking you can export to Power BI.

The diagram below shows the flow from setup to cost control:

flowchart TD
    Enable["Enable pay-as-you-go"] --> LinkSub["Link Azure subscription"]
    LinkSub --> AgentAllow["Allow specific agents"]
    AgentAllow --> UserAssign["Assign users or groups"]
    UserAssign --> Use["User accesses agent"]
    Use --> Billing["Cost captured in Azure"]
    Billing --> Budget["Budget & alerts in Azure"]
    Budget --> Review["Monthly review & adjustments"]

Figure: Copilot pay-as-you-go from initial setup to ongoing cost control.

A full Copilot licence becomes the cheaper option for heavy users

More than once I've watched enthusiastic users push their pay-as-you-go costs up to the price of a full Copilot licence, sometimes past it. Nothing switches over automatically, so you have to look at the usage data regularly and compare it with the current licence price. My guide on Copilot usage reports and licence reallocation has some practical pointers.

The exact numbers depend on your pricing and usage patterns, so you'll need to run them yourself. As a rule of thumb, though, a user who relies on Copilot every day is almost always better off with a full licence. If you're planning rollouts and pilots, have a look at Pilot experiences: Copilot rollout lessons.

My take is that the flexibility only works if you stay vigilant

Copilot pay-as-you-go finally gives us a way to run focused pilots or equip power users without licensing everyone. For agents, it's a big step forward. Without solid governance and cost monitoring, though, you can lose control fast. My advice is to start with small user groups, set up budgets and alerts in Azure Cost Management and keep checking usage on a regular basis. Once someone crosses the point where a full licence makes sense, move them over instead of letting the costs creep up. With the right controls in place, Copilot pay-as-you-go is a genuinely useful tool for flexible, security-minded IT teams.