What AI Agents Actually Cost in Microsoft 365: Copilot Studio Credits and Agent 365 Licensing (2026 Guide)

The cost of an AI agent in Microsoft 365 is not a per-seat price — it is a consumption meter plus a governance seat. Building and running agents in Copilot Studio is billed in Copilot Credits at $0.01 per credit, either pay-as-you-go through Azure or as a prepaid capacity pack of 25,000 credits for $200 per month, and a single agent response can cost anywhere from 1 credit to well over 100 depending on how it is built. Governing those agents is a separate line item: Microsoft Agent 365 became generally available on May 1, 2026 and is licensed per user, listed at $15 per user per month standalone.

That means the honest answer to "what does a Copilot Studio agent cost" is that architecture decides the bill, not headcount. This guide is written for the IT director sizing a budget, the architect choosing an orchestration pattern, and the finance partner who has to defend the forecast — it breaks down the credit rate card, what your existing Microsoft 365 Copilot licenses already cover, how the buying paths compare, and how to model a specific agent before you build it.

Key Takeaways

Copilot Credits are the unit of cost, and they are pooled at the tenant level. Pay-as-you-go through Azure is $0.01 per Copilot Credit, so cost tracks agent design and traffic rather than the number of people using the agent.
The prepaid capacity pack is $200 per month for 25,000 Copilot Credits. That is roughly 25,000 classic answers, 12,500 generative answers, or about 250 premium reasoning responses — the same money, three wildly different volumes.
Internal, employee-facing agent usage is already covered if the user holds a Microsoft 365 Copilot license. Microsoft lists classic answers, generative answers, tenant graph grounding, and agent actions as no charge for those users, subject to fair usage limits.
Governance is priced separately from execution. Microsoft Agent 365 reached general availability on May 1, 2026 for commercial customers on a per-user basis, listed at $15 per user per month standalone and bundled into Microsoft 365 E7.
The two biggest budget surprises are grounding and reasoning. Tenant graph grounding adds 10 credits per message and premium generative AI tools bill 100 credits per 10 responses, so one design choice can move an agent's run rate by an order of magnitude.
Forecast before you build, not after. Microsoft publishes a Copilot Credit estimator that models credit volume from agent type, traffic, orchestration, knowledge, and tools — running it during design is cheaper than discovering the number in production.

How much do AI agents cost in Microsoft 365? The short answer

Microsoft charges for enterprise AI agents on three independent meters, and a realistic budget has to account for all three. Skipping any one of them is how a $200-a-month estimate becomes a five-figure annual line item.

The build and run meter: Copilot Studio consumption, billed in Copilot Credits at $0.01 each pay-as-you-go, or $200 per month for a 25,000-credit prepaid capacity pack.
The user meter: Microsoft 365 Copilot at $30 per user per month paid yearly, which also waives credit consumption for internal, employee-facing agent usage by licensed users.
The governance meter: Microsoft Agent 365, licensed per user, listed at $15 per user per month standalone, covering registry, identity, observability, and security for agents rather than their execution.

A tightly scoped internal FAQ agent used by Microsoft 365 Copilot–licensed employees can run at effectively no incremental credit cost. A customer-facing, reasoning-heavy, graph-grounded agent handling thousands of conversations a month can consume six figures of credits a year. Both are "a Copilot Studio agent."

What are Copilot Credits, and how many does each agent action consume?

Copilot Credits replaced the older per-message currency and now act as a shared unit across Microsoft's agentic surfaces, including Copilot Studio, Dynamics 365 agents, and Power Platform AI capabilities. Microsoft's own definition is that a credit measures the time and effort required for an agent to retrieve information, respond, and act — so complexity, not message count, drives spend.

Microsoft publishes the exact billing rates for agents on the standard harness. These are the numbers that should sit in your cost model.

Copilot Studio credit rate card

Classic answer

Rate: 1 Copilot Credit per answer.
What it is: A predefined, manually authored response that never changes unless a maker edits it.

Generative answer

Rate: 2 Copilot Credits per answer.
What it is: A model-generated response grounded in connected knowledge sources.

Agent action

Rate: 5 Copilot Credits per action.
What it is: Triggers, deep reasoning steps, and topic transitions — Computer-Using Agent activity bills at this rate too.

Tenant graph grounding

Rate: 10 Copilot Credits per message.
What it is: Retrieval over your tenant-wide Microsoft Graph, including data synced through connectors — optional per agent.

Agent flow actions

Rate: 13 Copilot Credits per 100 actions.
What it is: Deterministic flow sequences that run without reasoning at each step.

Text and generative AI tools

Basic: 1 Copilot Credit per 10 responses.
Standard: 15 Copilot Credits per 10 responses.
Premium: 100 Copilot Credits per 10 responses, covering advanced reasoning.

Content processing and voice

Content processing tools: 8 Copilot Credits per page.
Classic voice: 10 Copilot Credits per minute.
GenAI voice: 35 Copilot Credits per minute, rising to 75 for premium GenAI voice.

These rates compound within a single turn. Microsoft's own worked example: an agent grounded in the tenant graph can spend 12 credits answering one complex prompt — 10 for grounding plus 2 for the generative answer. Bring-your-own-model configurations, including Microsoft Foundry models, are billed separately and sit outside this rate card entirely. Full rates are documented in Microsoft's Copilot Studio billing rates reference.

What is already included with a Microsoft 365 Copilot license?

This is the most valuable and most misread clause in the model. Employee-facing (business-to-employee) usage of Copilot Studio agents is included in the Microsoft 365 Copilot user subscription when the person interacting with the agent is licensed and the agent runs under that authenticated identity. Classic answers, generative answers, tenant graph grounding, and agent actions all show as no charge in that scenario, subject to fair usage limits Microsoft reserves the right to revise.

The exceptions are where budgets leak. Agent flows only qualify for the no-charge inclusion when triggered by "When an agent calls the flow" — every other trigger consumes credits at the standard rate. Computer-Using Agent activity is explicitly not included in the Microsoft 365 Copilot subscription. And any external-facing agent — a website, a customer portal, a messaging channel — consumes credits regardless of who built it.

The cheapest agent your organization will ever run is the internal one your people are already licensed for.

The practical sequencing consequence: if you already hold Microsoft 365 Copilot at $30 per user per month, your first wave of agents should be internal — IT service desk triage, HR policy lookup, onboarding assistance — because the marginal credit cost is close to zero and the operational learning transfers directly to the external agents you build next. BabyBots runs fixed-fee Copilot agent feasibility and cost-modeling assessments for exactly this sequencing question, and you can see how we frame the build order in our AI agent use case prioritization framework before you commit budget to a roadmap.

How do the Copilot Studio buying paths compare?

Microsoft sells agent consumption four ways, and the right one depends on how predictable your usage is — not on how large your organization is.

Copilot Studio buying paths compared

Included with Microsoft 365 Copilot

Price: $30 per user per month, paid yearly.
Best for: Internal, employee-facing agents used by licensed staff.
Watch for: Fair usage limits, non-standard flow triggers, and any external channel — all fall outside the inclusion.

Prepaid capacity pack

Price: $200 per month for 25,000 Copilot Credits.
Best for: Steady, forecastable production workloads with a known monthly floor.
Watch for: Credits are pooled tenant-wide, so allocate them per environment deliberately rather than leaving one team's pilot to drain the pool.

Pre-purchase (Copilot Credit Commit Units)

Price: Custom annual commitment, with savings of up to 20% for buying credits up front.
Best for: Multi-agent programs with a credible annual volume forecast.
Watch for: You need real consumption data before committing — pre-purchasing on a guess trades one budgeting problem for a worse one.

Pay-as-you-go through Azure

Price: $0.01 per Copilot Credit, usage-based.
Best for: Pilots, spiky workloads, and overflow coverage behind prepaid capacity.
Watch for: No ceiling by default — an unthrottled external agent bills every credit it consumes.

Prepaid and pay-as-you-go are not mutually exclusive. Microsoft supports allocating prepaid capacity to specific Power Platform environments and choosing what happens on overage: draw from the remaining tenant pool, or spill to a pay-as-you-go policy so business-critical agents keep running. Configure that deliberately — the default is rarely the one your finance team would have picked.

What does Microsoft Agent 365 cost, and do you need it?

Agent 365 is not an agent-building tool. It is the control plane for agents you have already built — a registry, an identity layer, an observability surface, and a security perimeter that sits across agents from Copilot Studio, Microsoft Foundry, open-source frameworks, and third-party platforms alike.

Microsoft confirms Agent 365 has been generally available for the Commercial segment on a per-user basis since May 1, 2026, works best with Microsoft E5 as a prerequisite, and requires at least one qualifying licensed user to enable. Licensing analysis places the standalone price at $15 per user per month, with Agent 365 also bundled into Microsoft 365 E7 at a list price of $99 per user per month; a single user license is described as covering all agents that person owns, manages, sponsors, or interacts with. Details are documented in this independent Agent 365 licensing breakdown.

What you get for that seat is the part most enterprises are currently missing. Agent 365 gives agents first-class identity through Microsoft Entra Agent ID, a central registry that inventories every agent and lets admins quarantine unsanctioned ones, an agent map showing how agents connect to users and resources, and enforcement through Microsoft Purview for data protection and Microsoft Defender for threat detection — the capabilities Microsoft outlined when it introduced Agent 365 as a control plane, citing an IDC projection of 1.3 billion agents by 2028.

The decision rule we use with clients: if you are running one or two agents in a single environment with a named owner, Agent 365 is premature. If agents are being built in more than one environment, by more than one team, touching regulated data, or arriving from third-party vendors, the $15 seat is cheaper than the first incident review. Existing enterprise controls were designed for users and applications, not for nonhuman actors that call APIs and send mail on someone's behalf — a gap we unpack further in our guide to autonomous agents in real enterprise deployments.

How do you forecast an agent's monthly cost before you build it?

Credit forecasting is arithmetic, not guesswork, once you commit to a design. Work the estimate in this order.

Define the audience. Internal and licensed, internal and unlicensed, or external — this single answer determines whether the credit meter runs at all.
Count turns per conversation. Estimate the average number of agent responses per session, not just the number of sessions.
Price one turn. Add the rates that apply to a typical turn: 2 credits for a generative answer, 10 more if tenant graph grounding is on, 5 per agent action, plus tool rates if a prompt tool fires.
Multiply by monthly volume. Turn cost times turns per conversation times conversations per month gives a monthly credit figure; divide by 25,000 to see how many capacity packs that implies.
Add the non-Copilot Studio layers. Bring-your-own-model tokens, Azure services the agent calls, and any Dataverse or premium connector requirements bill separately.
Validate against Microsoft's estimator. The Copilot Credit estimator models credit volume by agent type, traffic, orchestration, knowledge, and tools, and is useful as a sanity check on your own math.
Instrument before you scale. The Power Platform admin center reports credit consumption per environment and per agent across harnesses, so pilot with real traffic for 30 days before pre-purchasing anything.

Where do agent budgets actually blow up?

The overruns we see in practice are architectural, and every one of them is visible in the rate card if you read it before building rather than after.

Tenant graph grounding left on by default. It is optional per agent and adds 10 credits per message — five times the cost of the generative answer it accompanies. Turn it on where retrieval quality genuinely requires it, not everywhere.
Premium reasoning used for routine turns. At 100 credits per 10 responses, premium generative AI tools cost 100 times basic tools. Route only the turns that need judgment to the expensive model.
Reasoning where a deterministic flow would do. Agent flow actions bill 13 credits per 100 actions. Steps that never vary belong in a flow, not in an orchestration loop.
Unauthenticated external channels. A public agent with no rate limiting bills every credit that anyone on the internet chooses to spend.
Voice scoped casually. Premium GenAI voice at 75 credits per minute means a single 10-minute call costs about $7.50 before any actions fire.
Overage behavior nobody configured. When consumption exceeds allocated capacity, features are progressively blocked unless a pay-as-you-go fallback is in place — which becomes an availability incident rather than a cost one.

Frequently Asked Questions

How much does Microsoft Copilot Studio cost per month?

A Copilot Studio prepaid capacity pack is $200 per month for 25,000 Copilot Credits, and pay-as-you-go billing through Azure is $0.01 per Copilot Credit with no upfront commitment. There is no per-user price for agent usage — credits are pooled at the tenant level and consumed based on how agents are built and how often they run. A pre-purchase option for Copilot Credit Commit Units offers savings of up to 20% for buying credits annually in advance.

Do Microsoft 365 Copilot licenses include Copilot Studio agents?

Yes, for internal use. Microsoft includes employee-facing Copilot Studio agent usage — classic answers, generative answers, tenant graph grounding, and agent actions — in the Microsoft 365 Copilot user subscription when the interacting user is licensed and the agent runs under that authenticated identity, subject to fair usage limits. External-facing agents, Computer-Using Agent activity, and agent flows triggered by anything other than "When an agent calls the flow" consume credits at the standard rate.

How many Copilot Credits does one agent conversation use?

It depends entirely on the design. A scripted classic answer costs 1 credit, a generative answer costs 2, an agent action costs 5, and tenant graph grounding adds 10 credits per message — so Microsoft's own example of a grounded complex prompt lands at 12 credits for a single response. Add a premium reasoning tool and one turn can exceed 100 credits.

How much does Microsoft Agent 365 cost?

Microsoft Agent 365 is licensed per user and reached general availability for commercial customers on May 1, 2026. Independent licensing analysis lists the standalone price at $15 per user per month, with the capability also included in Microsoft 365 E7 at a $99 per user per month list price. Microsoft notes that Agent 365 works best with Microsoft E5 as a prerequisite and requires at least one qualifying licensed user to enable.

Is Agent 365 licensed per agent or per user?

Per user. Microsoft documents Agent 365 as licensed on a per-user basis rather than per agent, and licensing analysts describe a single user license as covering all the agents that person owns, manages, sponsors, or interacts with. That structure means governance cost scales with the number of people accountable for agents, not with the size of your agent fleet — which usually favors organizations running many agents under a small number of owners.

What happens when Copilot Studio credits run out?

When consumption exceeds the capacity allocated to an environment, features are progressively blocked, with a grace allowance intended to avoid halting business processes outright; for agent flows specifically, enforcement blocks new runs rather than disabling the agent. Administrators can allocate prepaid credits per environment in the Power Platform admin center and choose whether overage draws from the remaining tenant pool or falls through to a pay-as-you-go policy. Configuring that fallback is what keeps a budget event from becoming an outage.

Where this is heading

Two directions are already visible. Copilot Credits are consolidating into a single currency across Microsoft's AI surfaces — Copilot Studio, Dynamics 365 agents, Power Platform AI, and Work IQ APIs — which makes tenant-level credit governance a finance discipline rather than a Power Platform admin chore. Expect FinOps practices that were built for Azure consumption to be pointed at agent credits within the next budget cycle.

The second direction is that governance is being priced and sold as its own layer. Agent 365 formalizes what many enterprises were improvising: agents as identities with lifecycles, owners, policies, and audit trails. The organizations that will spend the least per unit of value are the ones that decide their agent architecture — internal versus external, grounded versus scoped, reasoning versus deterministic — before the meter starts, and instrument consumption from the first pilot rather than the first invoice.

Model your agent costs before you build

If you are sizing a Copilot Studio program and need a defensible number rather than a range, book a BabyBots agent cost and feasibility assessment — we model credit consumption per use case, map which agents your existing Microsoft 365 Copilot licenses already cover, and hand back a fixed-fee build plan with the governance layer scoped in. One working session, real arithmetic, no platform sales pitch.