Copilot Studio vs Azure AI Foundry: Which Agent Platform, What It Costs, and When to Bring Us In

Both platforms reach the same frontier models: Copilot Studio uses Microsoft's hosted models and can call models you deploy in Foundry through its bring-your-own-model option for prompts, while Foundry exposes the Azure OpenAI catalog and other model families directly. The real questions are who builds it, where its data lives, which channel the users are in, who governs it, and how the meter runs.

A Copilot Studio agent is built by a power user or Power Platform developer inside the tenant's existing environments, data policies and Microsoft 365 permissions. A Foundry agent is built by a developer with an Azure subscription, a landing zone and a pipeline. The first reaches a useful version in days; the second takes weeks and carries operations for life.

Copilot Studio is a maker tool. An agent is instructions, knowledge (SharePoint, files, websites, Dataverse, Microsoft Graph), topics for guided conversations, and tools: connectors, prompts, agent flows, MCP servers and other agents. It publishes to Teams, Microsoft 365 Copilot, the web and custom channels.

Licensing has three parts. The maker license, the Microsoft Copilot Studio User License, is $0.00. Capacity is a tenant subscription, Microsoft Copilot Studio, at $2,400.00 per tenant per year on an annual term, a $200.00 per month equivalent ($2,400.00 ÷ 12), or $240.00 per month on a monthly term (Microsoft list price, October 2026 price list); Microsoft's licensing guidance describes it as one capacity pack of 25,000 Copilot Credits per month. The third is the pay-as-you-go meter, a per-credit rate billed through an Azure subscription linked to the environment, alone or as overflow above the packs. That is Microsoft's metered charge and it is always yours.

Microsoft's billing page, which our estimator was checked against in September 2026, rates a classic authored answer at 1 credit, a generative answer at 2, an agent action or flow call at 5, and tenant Graph grounding at 10. A help desk agent answering 2,000 questions a month with a generative answer and one connector action each uses about 14,000 credits, inside one pack; add Graph grounding to every answer and it is 34,000. Run your numbers in the Copilot Studio estimator before buying a pack.

One exemption matters. Microsoft's guidance states that for users licensed for Microsoft 365 Copilot, $30.00 per user per month on an annual term ($360.00 ÷ 12, Microsoft list price, October 2026 price list), usage of agents published to Microsoft 365 Copilot is included, subject to fair-use limits. If most users hold that license, an employee-facing agent may need no capacity pack; the Copilot licensing guide covers the seat side.

Foundry is a developer platform, and Foundry Agent Service is its managed runtime for agents. Microsoft's documentation describes it this way: pick the model from the catalog, attach knowledge tools (Azure AI Search, Fabric, SharePoint, Bing grounding) and action tools (Azure Functions, OpenAPI, Logic Apps, MCP servers), give the agent a managed identity, and run it inside your own virtual network when needed. An agent can be published to Microsoft 365 Copilot and Teams from the Foundry portal, which provisions an Azure Bot Service resource and an Entra application, or through the Microsoft 365 Agents Toolkit.

There is no license to quote. Microsoft's Foundry Agent Service pricing page states that there is no additional charge for creating or running Foundry-native agents; you pay for model token consumption through Foundry Models, for the tools and knowledge connections the agent uses, and for hosted agent compute if you bring your own framework. All of it is Azure consumption on your subscription, metered by Microsoft, and always the customer's charge. Our Foundry work is priced for the build; the Azure bill is separate and sized with you before the first deployment.

That is the real difference: a Copilot Studio pack is a fixed monthly number, while a Foundry agent's cost moves with tokens per request, requests per day and the model you chose. Budget it like any Azure workload, with a secure AI landing zone (from $9,500 per project, 4 weeks) for keys, networking and logging.

Copilot Studio wins when the agent is for your own employees, the knowledge already sits in SharePoint, Dataverse or Microsoft Graph, the channel is Teams or Microsoft 365 Copilot, the actions are existing or custom connectors, and the people who will maintain it also maintain your Power Automate flows. Help desk, HR policy, sales enablement and phishing triage agents are Copilot Studio builds in our projects.

Foundry wins when you need a specific or fine-tuned model, when the agent is part of your product or a customer-facing site, when it must run inside a private network or a regulated Azure environment, when you need code-level control over tool calls and evaluation, or when volume is high enough that a per-token bill on a smaller model costs less than Copilot Credits.

The two platforms are designed to stack. Copilot Studio's bring-your-own-model option lets a prompt inside a Copilot Studio agent call a model you deployed or fine-tuned in Foundry, so a maker-built agent in Teams uses your domain model for one step while the rest stays low-code. In the other direction, a Foundry agent exposed through MCP becomes a tool or connected agent that a Copilot Studio agent hands work to. Identity, channel and data policies stay in Copilot Studio; the hard reasoning and the code live in Foundry.

This is our default when a Microsoft 365 Copilot tenant has one problem low-code cannot solve alone, such as contract analysis or a pricing engine. Both meters run, credits on one side and tokens on the other, so estimate them separately.

Whichever platform you choose, three controls come first.

Microsoft Purview: sensitivity labels and oversharing cleanup before any agent reads SharePoint, so retrieval cannot surface a document the user could not open themselves; our Purview before Copilot article gives the order.

Power Platform data policies: Microsoft's documentation (April 2026) describes how data policies cascade to every environment in the tenant, classify connectors, and set a violating connection to a disabled state; it also notes that the Copilot Studio controls are evolving into their own governance rules. Give agents their own environment with a policy listing only the connectors they may use.

Microsoft Entra Agent ID: Microsoft's documentation (April 2026) describes it as the identity framework that gives agents their own directory identities, with Conditional Access, Identity Protection, lifecycle management and audit logs applied to them, on Microsoft and non-Microsoft platforms. Our agent governance article explains the inventory problem; the AI Agent Inventory and Lifecycle Governance Implementation ($4,950 per project, 3 weeks) builds it, and the Copilot Studio Agent Security Review ($2,950, 2 weeks) tests one agent the way an attacker would.

Is Copilot Studio included with Microsoft 365 Copilot?

Building an agent needs the Copilot Studio user license, listed at $0.00. Running it needs capacity, except that Microsoft's guidance states agents published to Microsoft 365 Copilot are included for users who hold that license, subject to fair use. Unlicensed users and other channels consume credits.

Do we need Azure for Copilot Studio?

Only for pay-as-you-go billing, which links an Azure subscription to the environment. Prepaid packs alone need no Azure subscription. The pay-as-you-go credits setup is included with IT Partner licensing.

Which one is cheaper?

For an employee-facing agent on Microsoft 365 data, usually Copilot Studio, and it may be covered by Microsoft 365 Copilot seats. For high-volume or customer-facing agents, a Foundry agent on a smaller model can cost less per interaction. Estimate both.

• Microsoft, Copilot Studio licensing guidance (microsoft.com/licensing/guidance/Microsoft-Copilot-Studio), opened October 2026; the page shows no date
• Microsoft Learn source files on GitHub, opened: MicrosoftDocs/entra-docs "What is Microsoft Entra Agent ID?", ms.date 04/14/2026; MicrosoftDocs/power-platform "Data policies" (wp-data-loss-prevention), ms.date 04/07/2026
• Microsoft Learn pages that could not be retrieved when this article was written, cited without a date: "Copilot Studio billing and licensing" and "Copilot Credits and capacity management" (consumption rates); "Foundry Agent Service overview" and "Tools overview"; "Bring your own model for your prompts"; "Publish an agent to Microsoft 365 Copilot and Teams"; Azure pricing page "Foundry Agent Service pricing"
• IT Partner: src/lib/calc/copilot-studio.ts (credit rates verified 2026-09-13 against Microsoft's billing page); content/blog/new/microsoft-365-copilot-licensing-and-pricing-2026.json; what-is-agent-governance-and-why-your-business-needs-it-in-2026.json; why-you-must-deploy-microsoft-purview-before-copilot.json
• IT Partner pages: content/services/ITPWW0790DEVOT, PRP-CPLT-004, ITPWW0770DEVOT, ITPWW880DEVOT, ITPWW460SECOT, ITPWW1010IMPOT, ITPWW1030IMPOT and ITPWW910IMPOT; Microsoft Copilot Studio CFQ7TTC0LH1F (SKUs 0001 and 000P) and Microsoft 365 Copilot CFQ7TTC0MM8R (SKU 0002), October 2026 price list
• IT Partner engineering notes from Copilot Studio and Foundry agent builds, September 2026