Usage-based billing goes default for Copilot Business

What partners need to do

If you're trying to keep up with the firehose of Copilot news from Microsoft, here's the latest one worth your attention: starting 2 November 2026, usage-based billing becomes the default setting for new Microsoft 365 Copilot Business licenses bought through CSP – standalone or bundled. No more manual setup required to open the door to Copilot Cowork, Work IQ APIs, and the GitHub Copilot Harness.  This blog post looks at some considerations for your customers deploying Copilot.

What mature data governance looks like

Worth being precise about what this does and doesn't mean, though: it doesn't hand your customer's users automatic access to Copilot Cowork – that still needs to be deployed and made discoverable. What it does mean is that the Azure subscription and billing plumbing needed to pay for Cowork, Work IQ API calls, and GitHub Copilot Harness usage will already be sitting there the moment a new licence is provisioned.

Making onboarding smoother for new Copilot Business customers is unquestionably a good thing. But with great PAYG comes (possibly) great bills – so this is one of those "great power, great responsibility" moments for partners.

As a CSP reseller and Copilot implementation partner, here's what you need on your radar:

• A new Azure subscription lands on the tenant automatically – make sure only the right people have admin access to it.
• The subscription will start showing up on your customer's SoftwareOne invoice – how are you going to explain that line item before they ask you first?
• Spending policies don't configure themselves. Set caps, alerts and access scoping before usage starts, not after the first invoice lands – default cost-management settings can quietly auto-enable new pay-as-you-go services.
• PAYG Copilot Credits are exactly that: pay-as-you-go, so make sure your customer's credit standing in your systems reflects real, uncapped-by-default spend.
• Inform your customers about the upside and the pitfalls so they can make an informed call on whether to switch on Cowork and other usage-based agents.
• Add this to your implementation runbook so usage-based consumption settings get checked on every new deployment, not just remembered on the good days.

Lastly, as Redmond keeps placing its chips on Copilot, are you as a partner using it yourselves? As with most tech, having hands-on experience to draw from helps a lot – so consider this your nudge to become Customer Zero if you aren't already.

How Cloud-iQ helps you stay ahead of this

Getting transparency on a new Azure subscription – and spotting whether a customer's burning through Copilot Credits – is refreshingly easy with Cloud-iQ. It automatically detects new subscriptions on a customer's tenant, assigns them to the right customer, and follows the invoicing settings you've already set up. Nothing extra for you to do.

Want to check if a customer's already dipping into Copilot Credits? The quickest route is the "Microsoft CSP Azure Plan Cost & Usage Estimates report – download it, filter on "Pay As You Go Copilot Credit," and you'll see usage across all your customers by meter.