Business Central

Business Central Copilot and agent pricing in Australia: what teams should budget in 2026

A practical Microsoft Dynamics 365 Business Central guide for Australian teams separating what Copilot includes already, what agents bill separately, and how to budget Copilot Credits without guesswork.

The current Microsoft documentation creates one important distinction that many buyers still miss. Standard Copilot capabilities inside Business Central are currently included with the Business Central licence, while selected autonomous agent capabilities such as Sales Order Agent and Payables Agent use separate consumption-based billing through Copilot Credits.

For Australian teams, that changes the budgeting conversation. The key question is not whether Microsoft mentions Copilot on the pricing page. It is which capabilities are already covered by the core subscription, which ones need an Azure-linked billing model, and how quickly usage-based cost can move from trivial to material once real AP or order-volume hits production.

What Microsoft officially says is included

• Microsoft's current Business Central pricing page says Essentials and Premium include Microsoft Copilot, and the Business Central Copilot overview says Copilot is currently included with the Business Central licence at no extra cost.
• Microsoft also says no minimum user count is required to start using Copilot in Business Central.
• Microsoft's Copilot overview makes another useful clarification: the 30 minutes of Azure AI time referenced in the Dynamics 365 licensing guide applies to non-Copilot Azure AI features such as forecasting, and it does not affect Copilot in Business Central.
• Microsoft's release-plan overview for Copilot and agents also says these capabilities are available only to Business Central online customers, which is an immediate filter for any organisation still carrying on-premises assumptions.

What is not included in the same way

• Microsoft's pricing page explicitly marks Sales Order Agent and Payables Agent as requiring Copilot Credits sold separately.
• Microsoft's admin documentation says selected Business Central agent capabilities use consumption-based billing and that these capabilities use Copilot Credits for AI interactions and tasks.
• Microsoft also says an Azure subscription is required to use agents and that Business Central environments must be linked to a Power Platform environment for billing setup.
• The practical takeaway is simple: “Copilot included” is true for the built-in assistant experience, but it is not the same as “all Business Central AI automation is free”.

Why Australian budgeting gets muddled

• Australian buyers often start with the public pricing page and assume that if Copilot is named there, the whole AI roadmap is covered by the normal ERP subscription. Microsoft's own documentation does not support that assumption.
• The public Business Central page shows US list pricing structure, but Australian customers usually buy through a partner or CSP quote. That means local budgeting should focus first on commercial shape and consumption drivers rather than on a rough currency conversion from the website.
• The harder budget variable is not the base user licence. It is whether the business plans to run mailbox-driven agents at meaningful scale, because that introduces usage-based spend that depends on workflow volume and complexity.

Microsoft's own usage examples are a better planning starting point

• In Microsoft's Business Central billing documentation, a typical Sales Order Agent flow uses 2 Copilot Credits to analyse the incoming email, 5 to check item availability, 5 to create or update the quote or order, and 2 to generate the response email.
• Microsoft then gives an example where 100 monthly requests with attachments on half the emails total 1,650 Copilot Credits per month.
• For Payables Agent, Microsoft documents 50 Copilot Credits to process one invoice plus 5 Copilot Credits per invoice line for line-level interpretation and matching.
• Microsoft's worked example for 100 emailed invoices per month with three lines each totals 6,500 Copilot Credits per month.
• Those examples are more useful for buyer planning than generic AI marketing because they connect actual operational volume to a specific billing model.

What finance and operations leaders should budget separately

• Base subscription budget: Essentials, Premium, Team Members, and other conventional user licensing still need their normal role-based review.
• Agent consumption budget: treat Copilot Credits as a distinct operating line item for any planned use of Payables Agent, Sales Order Agent, or other consumption-billed agent capabilities.
• Implementation budget: mailbox design, permission setup, Power Platform environment linking, Azure billing setup, testing, and exception-handling design still require delivery effort even when the feature is standard product.
• Governance budget: someone must monitor usage, capacity allocation, low-credit warnings, and environment-level ownership after go-live.

The billing design decisions to make before pilot approval

• Decide whether to start with prepaid capacity or pay-as-you-go. Microsoft supports both models in Business Central and says prepaid capacity is consumed first when both are available.
• Decide whether credits stay at tenant level or are allocated to specific linked environments. Microsoft notes that Copilot Credit capacity can also be consumed by other Microsoft services on the tenant, so environment allocation matters if you want tighter cost control.
• Decide which workflow gets first priority for AI spend. AP and sales order capture have very different usage patterns, error costs, and owner groups, so they should not be bundled into one vague “AI budget”.
• Decide what usage threshold would trigger review. If credit spend rises faster than invoice volume saved, the business needs an explicit checkpoint rather than assuming automation is automatically economic.

A practical buyer checklist for Australian teams

• Step 1: separate “included Copilot” use cases from “consumption-billed agent” use cases in the business case.
• Step 2: ask your partner to map one realistic month of AP or order volume to Microsoft's documented Copilot Credit model instead of using a generic AI allowance.
• Step 3: confirm whether the organisation is Business Central online only for the target entities and whether the Azure and Power Platform billing prerequisites are already in place.
• Step 4: set a small pilot with one environment, one monitored process, and a named owner for monthly credit usage review.
• Step 5: compare agent usage cost against the operational outcome you actually want, such as faster invoice intake, better quote response time, or lower queue backlog, not against AI enthusiasm alone.

What readers should conclude now

• Business Central AI budgeting now has two practical layers. Built-in Copilot is currently included, but autonomous agent scenarios can add a separate usage-based cost layer.
• For Australian SMB and mid-market teams, the real risk is not that Microsoft's pricing is hidden. It is that organisations collapse licence cost, usage cost, and delivery effort into one “Copilot” assumption.
• The safest approach is to budget Business Central AI in three parts: core licences, Copilot Credit consumption for agents, and the implementation-governance effort required to keep that consumption useful.

Sources used

• Microsoft Dynamics 365 Business Central pricing page for Copilot inclusion and separately billed agent listings.
• Microsoft Learn Copilot in Business Central overview for included Copilot, no minimum users, and the Azure AI time clarification.
• Microsoft Learn manage consumption-based billing page for billable capabilities, setup model, and the Sales Order Agent and Payables Agent Copilot Credit examples.
• Microsoft Learn release-plan overview for the statement that Copilot and agents are available only to Business Central online customers.