Microsoft Copilot Studio Pricing Australia (2026)

The published Australian starting point is AU$299.30 a month excluding GST for 25,000 credits, as at 7 October 2026. But that buys capacity, not a completed AI automation. I'd price the actual enquiry or staff workflow before choosing packs, because different responses and actions consume different amounts (Australian pricing; consumption rules).

What Does Copilot Studio Cost in Australia In 2026?

Microsoft offers three ways to buy Copilot Credits. Monthly packs pool capacity across the tenant; pay-as-you-go charges actual consumption through Azure; the prepurchase plan is a one-year prepaid option (Microsoft licensing guide).

Microsoft's documentation lists the pay-as-you-go meter at $0.01 per credit, with currency not stated; your Azure bill shows the AUD amount. I would not turn that into an Australian quote (meter documentation).

The pack works out to approximately AU$0.012 per credit excluding GST, calculated from the published price. That is an allocation of the pack price, not a pay-as-you-go rate. For staff seat costs, see Microsoft Copilot pricing in Australia.

What Is a Copilot Credit, and How Many Does Each Action Use?

A Copilot Credit is Microsoft's common billing currency across Copilot Studio capabilities. One conversation can consume several chargeable features, so counting conversations alone will miss part of the bill (licensing; billing examples).

Microsoft's example combines tenant graph grounding and a generative answer into 12 credits for one complex prompt. The rates cover models provided by Copilot Studio; bring-your-own-model configurations, including Azure Foundry models, are billed separately (rate scope).

I'd ask the builder to show which features each workflow uses. A short answer followed by a CRM update has a different consumption pattern from an answer alone.

When Is Copilot Studio Included with Microsoft 365 Copilot?

The no-charge rule covers employee-facing agents and the tools and features those agents invoke when the employee has the qualifying Microsoft Copilot user licence and the agent operates under that authenticated user's identity. Fair usage limits apply (Microsoft's conditions).

That is a useful exemption for an internal staff agent. It does not make a public website agent free because the owner has Microsoft 365 Copilot. Agent flows using other triggers consume credits at standard rates, and computer-using agents are outside the exemption (usage rules).

I would have the builder document the users, authentication and triggers before treating any workflow as included.

How Do You Estimate a Website or Internal Agent's Monthly Bill?

Start with the actions inside each interaction, then multiply by expected volume. The following calculations use standard harness rates and the Australian pack price (rates and examples; pack price).

A Hypothetical Small Business Website Enquiry Agent

Assume 50 conversations a day, each using three generative answers and two agent actions:

1. Three generative answers consume 6 credits.
2. Two agent actions consume 10 credits.
3. Each conversation therefore consumes 16 credits.
4. 50 conversations consume 800 credits a day, or 24,000 over an assumed 30-day month.

That hypothetical workload fits just under one AU$299.30 monthly pack excluding GST. It leaves little room for extra activity. Doubling volume reaches 48,000 credits; adding one tenant graph grounding charge to every conversation reaches 39,000. Either design exceeds one pack.

Microsoft's Website Support Example

Microsoft assumes an average of 900 customers a day and publishes this calculation: [(4x1)+(2x2)] x 900 customers = 7200 Copilot Credits per day (worked example).

For an illustrative 30-day month, that becomes 216,000 credits. Nine packs provide sufficient purchased capacity and cost AU$2,693.70 excluding GST at the published pack price. That is arithmetic on Microsoft's example, not a forecast for your website.

Microsoft's Internal Sales Agent Example

Microsoft's sales performance example charges only the 100 unlicensed users; the other 50 have Microsoft 365 Copilot licences. The published calculation is [(4x2)+(4x10)] x 100 users = 4,800 Copilot Credits per day (internal agent example).

Over an assumed 20 working days, that is 96,000 credits. Four packs cost AU$1,197.20 excluding GST at the published pack price. I would check the licence exemption first, because the number of chargeable users changes this estimate.

What Happens If You Run Out of Credits, and How Do You Cap Spending?

Unused monthly credits do not carry over. Microsoft allows some prepaid overage, then triggers enforcement at 125% of purchased capacity. Custom agents are disabled and can display: "This agent is currently unavailable. It has reached its usage limit." Pay-as-you-go avoids that enforcement because overage bills to Azure (monthly capacity; enforcement).

I would not budget around the grace allowance. The useful control is Microsoft's monthly consumption limit for individual agents in the Power Platform admin centre (agent limits).

1. Estimate normal and busy-month consumption separately.
2. Set an agent limit against the credit budget.
3. Assign someone to review consumption and exceptions.
4. Agree what customers or staff should do when the agent is unavailable.

Does the Github Copilot Harness Change the Bill?

Yes. Microsoft's GitHub Copilot harness charges credits from the moment you start building, while the standard harness starts billing after publication. Charges cover LLM tokens, tools including knowledge and MCPs, and the harness itself (billing overview).

The GitHub Copilot harness is a Copilot Studio framework, not the GitHub Copilot service. Microsoft positions it for reasoning-heavy agents and complex business processes (harness overview). I would ask which harness the proposal assumes before accepting a credit estimate.

What Does a Copilot Studio Subscription Not Cover?

A capacity purchase does not scope your build. I would ask for separate one-off design and build costs, ongoing running costs, and software subscriptions. The quote should name the connections, permissions, approval points, failure handling and owner after launch. Compare delivery options in the AI agent builders guide and broader budgets in AI automation costs in Australia.

Microsoft's trial permits agent creation but not publication. Its free maker licence also requires a tenant prepaid credit pack subscription first (licence requirements). So I would separate learning access from the budget for a live system.

For an Australian service business that wants automation designed, built and then run for it, with a person approving anything sensitive, Truespeak is built for exactly that. At Nikon Australia I built an AI chatbot that deflected more than 140 customer service calls a month, so I know the bill depends on what the agent is designed to do.

Truespeak works with the tools a business already uses; a step stays manual where no usable connection exists. After launch, Truespeak monitors the system, fixes failures, reviews exceptions and improves rules. That work is covered by managed AI operations.

Truespeak does not publish prices. A quote follows a discovery call and covers design, build and ongoing running. I'd start with the enquiry or internal task you need handled, then decide which platform and credit budget suit the work.