New Microsoft 365 Copilot Business reseller orders will default to pay-as-you-go

Microsoft is taking some of the friction out of buying its metered AI tools. The business paying the bill will need to put some thought into the limits.

From 2 November 2026, new Microsoft 365 Copilot Business purchases through the Cloud Solution Provider (CSP) channel will include usage-based billing by default. That covers standalone licences and bundles bought through participating IT providers and resellers, with the necessary Azure subscription setup included.

Microsoft’s 16 September partner announcement explains the appeal to sellers plainly: less billing setup, followed by opportunities for “expanded consumption” and “upsell conversations”. For the office manager approving the order, those words have a simpler meaning. The number of people with a licence won’t, on its own, tell you what Copilot will cost.

This is a change to new CSP purchases. The announcement doesn’t say all existing subscriptions will switch on that date, or set a date for purchases made directly from Microsoft. An order adding seats to an existing agreement needs clarification from the provider.

Copilot’s Australian price is only part of the bill

On 30 September, Microsoft’s Australian website advertised the Copilot Business add-on from A$26.91 per user per month, paid yearly, excluding GST. That price comes with conditions: it’s a first-year promotion running from 1 July to 31 December 2026, for existing customers with an eligible Microsoft 365 Business plan. It requires an annual commitment and auto-renews. The underlying Microsoft 365 plan costs extra.

Even with those conditions understood, that figure leaves out an important part of the buying decision. It’s Microsoft’s advertised subscription price, rather than a reseller quote covering service charges and metered use.

Microsoft splits Copilot into two kinds of spending: the user subscription for everyday AI work, and usage-based billing for more demanding work, including Cowork. The latter consumes Copilot Credits. Administrators must set up a billing policy before people can use experiences that require usage-based billing.

Nor is a credit simply another name for a prompt. Microsoft’s billing documentation says consumption depends on the model, information retrieved, running time and tools used. A request that sends an agent through several steps can carry a different cost from a short exchange. A headcount is easy to price; the work those people hand over is less predictable.

That makes the Australian-dollar usage rate worth getting in writing, with GST clearly stated. Microsoft refers to a preset monthly limit in the partner announcement but doesn’t give its amount. There’s no sound budget to build from that omission.

Defaults are buying decisions

The most revealing details are in Microsoft’s setup instructions. The default policy covers all users. Auto-apply new services is also on, so future supported services and agents can join the policy automatically. And each additional spending policy has an independent limit: it doesn’t inherit the default policy’s limit.

Those are consequential choices for a small business trying Copilot with a few staff. A company-wide configuration is a poor fit for a small trial, and the limit on one policy doesn’t settle what another can spend.

Our recommendation is to begin with a named group and one task whose result you can check. In Copilot > Cost Management, the administrator can narrow access, choose services, set monthly policy and per-user credit limits, and nominate alert recipients. Turn off automatic additions if you want to approve new services first.

Limits have an operational cost too. Microsoft says reaching a policy limit cuts off the covered agents and services until credits reset the following month, unless the limit is changed. Whoever receives the alerts needs authority to decide whether more spending is justified.

The bookkeeper then faces a second translation: credits into dollars. Copilot > Cost Management reports credits rather than dollars; Azure billing shows the charges. Microsoft’s billing documentation says usage can take up to 24 hours to appear in Azure Cost Management, and Cowork charges can appear under Microsoft Copilot Studio. The usage dashboard can also include non-billable activity, so it isn’t the final record for reconciling an invoice.

Have the provider walk through that path before the order is approved, from a staff member’s access to the policy limit to the charge on the bill. During the trial, record the checking and rework alongside the credits consumed. The credit bill won’t capture that staff time.

Microsoft is making the route from buying a licence to consuming more AI easier. A small business still needs someone who can explain what it’s paying for, and decide when the extra work is worth the extra charge.

Checklist

• Confirm the order with your IT provider. Establish whether it is a new CSP Copilot Business purchase covered by the 2 November 2026 change.
• Get both prices in writing before approving the order. Ask the provider for the licence charge and Australian-dollar usage rate, including GST treatment.
• Review the spending policies with your administrator before metered use starts. Check the staff, services, monthly policy and per-user limits, alert recipients, and whether future services will be added automatically.
• Trace the usage charges with your bookkeeper and provider. Identify the credit report, the corresponding invoice charges and the final billing record used for reconciliation.