Skip to main content

Copilot Studio Agent Development

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

EPC Group's Copilot Studio Agent Development service designs, builds, and deploys custom Microsoft Copilot Studio agents for HR, IT helpdesk, sales, customer service, and line-of-business use cases. Tiered: Single Agent (4-8 weeks), Multi-Agent Suite (3-6 months), Agent CoE (6-12 months) — each fixed-fee, scoped after discovery. Includes Agent 365 governance integration, custom connectors for proprietary systems (Epic, SAP, ServiceNow), and agent sprawl prevention framework.

Key Facts

  • Custom Microsoft Copilot Studio agents for specific business use cases
  • 1,000+ pre-built connectors + custom connectors for proprietary systems
  • Agent 365 governance integration (Entra ID identity + Conditional Access)
  • Tiered engagements: single agent up to Agent Center of Excellence, scoped after discovery
  • Agent sprawl prevention with registry + quarterly attestation
  • Industry depth: healthcare (Epic/Cerner), finance, government (FedRAMP)
  • Microsoft Press author + AI Cloud Partner all six designations
  • Microsoft conversational AI since Power Virtual Agents (2019)

Engagement Tiers

Single Agent
Fixed fee
4-8 weeks

One production agent. 5-15 topics. 2-3 data source connections. Teams + web deployment.

Multi-Agent Suite
Fixed fee
3-6 months

3-8 agents covering HR + IT + Sales + Service. Agent 365 governance. Prompt audit cadence.

Agent Center of Excellence
Fixed fee
6-12 months

Suite + custom connectors + agent registry + CoE framework + internal academy.

High-Value Agent Use Cases

  • HR Policy Bot — policy library Q&A, benefits, escalation
  • IT Helpdesk Triage — password, software request, unlock
  • Sales Account Research — D365 + LinkedIn + news synthesis
  • Customer Service First-Line — KB lookup, ticket, handoff
  • Procurement Bot — PO status, vendor onboarding, contract Q&A
  • Field Service Diagnostic — manual Q&A, parts, dispatcher escalation

How Copilot Studio is licensed and billed (checked October 21, 2026)

Copilot Credits are the unit that measures agent usage in Copilot Studio; the number an agent consumes depends on its design, how often people interact with it and the features it uses (Microsoft Learn, Billing rates and management, accessed 2026-10-21). On September 1, 2025 the common currency for agents changed from messages to Copilot Credits, with no change in the quantity per prepaid pack or the pay-as-you-go rate (Microsoft Learn, Licensing for agents powered by the standard harness, accessed 2026-10-21). Credits are bought three ways: prepaid Copilot Credit pack subscriptions, a pay-as-you-go meter that bills an Azure subscription through a Power Platform billing policy, and a one-year Copilot Credits prepurchase plan (Microsoft Learn, Licensing for agents powered by the standard harness, accessed 2026-10-21). Purchased capacity is pooled across the tenant (Microsoft Learn, Billing rates and management, accessed 2026-10-21), enforced monthly, and unused Copilot Credits do not carry over to the next month (Microsoft Learn, Licensing for agents powered by the standard harness, accessed 2026-10-21).

Makers need a Copilot Studio user license, which is free of charge once the tenant holds a prepaid Copilot Credit pack subscription, or a Microsoft 365 Copilot license (Microsoft Learn, Licensing for agents powered by the standard harness, accessed 2026-10-21). People who use a published agent need no special license (Microsoft Learn, Assign licenses and manage access to Copilot Studio, accessed 2026-10-21).

Copilot Credits billing rates as Microsoft Learn lists them (Microsoft Learn, Billing rates and management, accessed 2026-10-21). The rates apply to the language models Copilot Studio provides; bring-your-own-model configurations are billed separately.
Agent featureCopilot Credits
Classic answer1
Generative answer2
Agent action (triggers, deep reasoning, topic transitions; computer-using agents bill at this rate)5
Tenant graph grounding for messages10
Agent flow actions, per 100 actions13
Text and generative AI tools, per 10 responses: basic / standard / premium1 / 15 / 100
Content processing tools, per page8

For employee-facing use, Microsoft Learn lists these features as no charge when the person using the agent holds a Microsoft 365 Copilot license and the agent runs under that user’s authenticated identity, within fair usage limits; computer-using agent usage is not included, and agent flows count as no charge only when the “When an agent calls the flow” trigger starts them (Microsoft Learn, Billing rates and management, accessed 2026-10-21). Agents created inside a Teams environment with Copilot Studio for Teams consume no Copilot Credits, while agents built in standalone Copilot Studio and published to the Teams channel do (Microsoft Learn, FAQ for Copilot Studio billing and licensing, accessed 2026-10-21).

Power Virtual Agents is not a separate tier to mix in for cheaper traffic. Microsoft Learn names it V1 of Copilot Studio, the classic chatbots (Microsoft Learn, Microsoft Copilot Studio Agent inventory, accessed 2026-10-21), and a classic chatbot built in Power Virtual Agents can be cloned and converted into an agent on the standard harness; cloning creates a new agent and leaves the classic chatbot unchanged, and classic chatbots that use languages other than English, hand-off to Omnichannel for Customer Service or Knowledge Management extensions are not eligible to be cloned (Microsoft Learn, Upgrade classic chatbots to Copilot Studio, accessed 2026-10-21). Where a tenant still runs classic chatbots, EPC Group inventories them, clones the eligible ones, rebuilds the rest as new agents, and retires each classic chatbot after its replacement passes testing.

Worked example — an illustration on Microsoft Learn’s own rates, not a quote or a forecast

Assumptions (dated October 21, 2026): an IT helpdesk agent built in standalone Copilot Studio on the standard harness with generative orchestration, published to the Teams channel and an internal web page, grounded in one SharePoint knowledge source, with one connector action that opens a ticket in the service desk. The employees using it do not hold Microsoft 365 Copilot licenses, so their usage is billed. Tenant graph grounding is turned off.

One conversation: 2 classic answers (2 × 1 = 2 Copilot Credits), 2 generative answers from the knowledge source (2 × 2 = 4), and 1 connector action, which Microsoft Learn counts as an agent action in generative orchestration mode (1 × 5 = 5): 11 Copilot Credits (Microsoft Learn, Billing rates and management, accessed 2026-10-21).

A month at 1,000 such conversations: 11 × 1,000 = 11,000 Copilot Credits. Turning tenant graph grounding on adds 10 Copilot Credits to each grounded response; the same agent used by Microsoft 365 Copilot licensed employees under their own identity is listed as no charge for these features (Microsoft Learn, Billing rates and management, accessed 2026-10-21).

The conversation mix and volume are assumptions for illustration. Microsoft describes its estimator as informational and recommends a 10–20% buffer above an estimate (Microsoft Learn, Agent usage estimator, accessed 2026-10-21).

Forecast an agent’s volume with the Microsoft Copilot Studio agent usage estimator, which selects agent type, traffic, orchestration, knowledge and tools (Microsoft Learn, Licensing for agents powered by the standard harness, accessed 2026-10-21). The source pages: Copilot Studio licensing on Microsoft Learn and Billing rates and management.

Copilot Studio agent security: data policies, sign-in and agent identities

Copilot Studio consulting for enterprise AI agent development starts with the controls Microsoft enforces, not with prompts. As a Copilot Studio integration partner, EPC Group sets these before the first agent is published:

  • Data policies. Power Platform data policies have been enforced for Copilot Studio agents in every tenant since early 2025, with no exemption for agents. Connectors are classified as Business, Non-business or Blocked; blocking “Chat without Microsoft Entra ID authentication in Copilot Studio” stops agents that need no sign-in, the HTTP connector or specific endpoints can be blocked, and publishing channels can be closed. Blocking a connector also blocks the tools in connected MCP servers.
  • Sign-in. New agents default to Authenticate with Microsoft. Choosing No authentication lets anyone who has the link chat with the agent.
  • Agent identity. Copilot Studio creates a Microsoft Entra Agent ID for each new agent and, at publish, attaches API permissions for each connector it uses, which Conditional Access policies can target by network location, device compliance or risk.
  • Environments. Managed Environments, included with standalone Copilot Studio licenses, add limited sharing, usage insights, pipelines, IP firewall, customer-managed keys and default environment routing. Unmanaged developer environments must be made managed before December 15, 2026.
  • Publishing and audit. An agent published by your organization appears in the Microsoft 365 admin center agent registry once an admin approves it; publishing in Copilot Studio alone might not make it visible there. Microsoft Purview captures agent prompts and responses in the unified audit log and supports DLP, sensitivity labels, eDiscovery and retention for Copilot Studio agents.

Sources: Microsoft Learn, data policies, end-user authentication, Entra agent identities, security and governance, Managed Environments, agent registry and Purview for Copilot Studio (accessed 2026-11-07).

AI Agent Development Services by Need

Which agents are worth building

Agents earn their cost on high-volume questions that existing content or systems can already answer. Each candidate is weighed on volume, the data it needs and the harm a wrong answer would do before any build starts.

Build: Copilot Studio, Azure AI Foundry, custom

Copilot Studio for agents that live in Microsoft 365 and Teams; Azure AI Foundry when an agent needs its own models, code or orchestration; custom connectors for systems with no pre-built connector.

Testing and acceptance before production

Each agent passes a written acceptance test covering expected answers, refusals, escalations and the actions it may take. See the Copilot Studio agent acceptance test pack.

Governance, identity and cost control

Who may build and publish, the data policies and identities agents run under, and Copilot Credits capacity. See Copilot Studio agent governance, Microsoft Agent 365 and agentic AI governance.

Running agents: monitoring and change

Usage and answer quality are reviewed after launch, prompts and topics change through a release process, and agents nobody uses are retired. For how other firms compare, see AI agent development companies in 2026.

What we need from your team: a named business owner for each agent, read access to the content and systems it must use, and the people who will test it before launch.

Next step: Schedule Discovery Call. The call covers the agents you are considering, the data and systems they need, and how they will be governed.

FAQ

How do you secure Copilot Studio agents?

With the controls Microsoft enforces: Power Platform data policies (enforced for agents in every tenant since early 2025, no exemption), Authenticate with Microsoft as the sign-in default, a Microsoft Entra Agent ID for each new agent that Conditional Access can target, Managed Environments, admin approval before an agent appears in the Microsoft 365 admin center registry, and Microsoft Purview audit, DLP and sensitivity labels for agent prompts and responses (Microsoft Learn, accessed 2026-11-07).

What is Microsoft Copilot Studio?

Microsoft Copilot Studio is the low-code platform for building custom AI agents that work alongside Microsoft 365 Copilot. Use cases: HR helpdesk, IT support, sales assistant, customer service triage, document processing. Agents can access Microsoft Graph content (SharePoint, Teams, Outlook), call external APIs, query line-of-business systems, and orchestrate multi-step workflows. Agents run inside Microsoft Teams, embedded web, Outlook, or as standalone chat experiences.

What is the difference between Microsoft 365 Copilot and a Copilot Studio agent?

M365 Copilot is the org-wide AI assistant grounded in your Microsoft Graph (Word, Excel, PowerPoint, Outlook, Teams chat). Copilot Studio agents are custom AI assistants you BUILD for specific use cases: HR policy Q&A, IT password reset, sales account research, claim status lookup. Agents have specific topics, connections to data sources, and personality. Agents can be triggered FROM M365 Copilot (agent extensibility) or run standalone.

What does the engagement deliver?

Three tiers. Single Agent (4-8 weeks): one production agent, 5-15 topics, 2-3 data source connections, deployed in Teams + embedded web. Multi-Agent Suite (3-6 months): 3-8 agents covering HR + IT + Sales + Service workflows, Agent 365 governance integration, prompt audit cadence. Agent Center of Excellence (6-12 months): suite + custom Copilot Studio connectors + agent registry + governance framework + adoption playbook + internal agent academy training.

What use cases work best for Copilot Studio agents?

High-volume + structured + answerable from existing content. Examples we have built: (1) HR Policy Bot (grounded in policy library, surfaces relevant section + escalates), (2) IT Helpdesk Triage (password reset, software request, account unlock), (3) Sales Account Research (Dynamics 365 + LinkedIn + recent news synthesis), (4) Customer Service First-Line (knowledge base lookup, ticket creation, handoff to human), (5) Procurement Bot (PO status, vendor onboarding, contract Q&A), (6) Field Service Diagnostic (equipment manual Q&A, parts lookup, dispatcher escalation).

How is Copilot Studio licensed and billed?

Copilot Studio bills agent usage in Copilot Credits, the common currency across Copilot Studio capabilities; on September 1, 2025 the unit changed from messages to Copilot Credits, with no change in the quantity per prepaid pack or the pay-as-you-go rate (Microsoft Learn, Licensing for agents powered by the standard harness, accessed 2026-10-21). Credits are bought as prepaid Copilot Credit pack subscriptions, through a pay-as-you-go meter billed to an Azure subscription, or as a one-year Copilot Credits prepurchase plan (Microsoft Learn, Licensing for agents powered by the standard harness, accessed 2026-10-21). Makers need a Copilot Studio user license, which is free of charge once the tenant holds a prepaid Copilot Credit pack subscription, or a Microsoft 365 Copilot license (Microsoft Learn, Licensing for agents powered by the standard harness, accessed 2026-10-21); people who use a published agent need no special license (Microsoft Learn, Assign licenses and manage access to Copilot Studio, accessed 2026-10-21). Each agent feature consumes credits at its own rate: a classic answer 1 Copilot Credit, a generative answer 2, an agent action 5, tenant graph grounding 10, and agent flow actions 13 per 100 actions (Microsoft Learn, Billing rates and management, accessed 2026-10-21). Power Virtual Agents is not a cheaper tier beside Copilot Studio: Microsoft Learn names it V1 of Copilot Studio, the classic chatbots (Microsoft Learn, Microsoft Copilot Studio Agent inventory, accessed 2026-10-21). EPC Group sizes each agent in Copilot Credits with the Microsoft agent usage estimator before capacity is bought, and quotes Microsoft licensing at Microsoft list price.

How do you integrate with line-of-business systems?

Copilot Studio connectors: 1,000+ pre-built (Salesforce, ServiceNow, Workday, SAP, Oracle, Dynamics 365, Power Platform). Custom connectors via OpenAPI spec for proprietary systems. Authentication: Entra ID (preferred), API key (acceptable), OAuth 2.0. Data residency: agents can scope queries to specific tenants, regions, or compliance boundaries. EPC Group has built custom connectors for healthcare EHR (Epic, Cerner), financial trading platforms, and government FedRAMP-bound systems.

How does Microsoft Agent 365 (May 1 2026) affect Copilot Studio agents?

Agent 365 gives Copilot Studio agents (a) Entra ID identity (new principal type), (b) cross-tenant collaboration with vendor + partner agents, (c) agent-to-agent messaging and delegation, (d) Conditional Access policies for agents. Net effect: Copilot Studio agents are now first-class enterprise citizens with identity, audit, governance. EPC Group includes Agent 365 governance integration in all multi-agent engagements from May 2026 forward.

What about governance + agent sprawl?

Critical issue. Copilot Studio is low-code: any employee can build an agent. Without governance: agent sprawl (hundreds of unmanaged agents), data exposure (agents grounding on oversharing exposure), security drift (agents calling APIs without approval). EPC Group governance framework: (1) Agent provisioning policy (who can build), (2) Agent registry (catalog of approved agents), (3) Agent permission tier (sandbox / dev / production), (4) Agent action audit trail, (5) Quarterly agent attestation, (6) Decommission policy. Included in Multi-Agent Suite + Agent CoE tiers.

How long until a single agent is in production?

Single Agent engagement: 4-8 weeks. Week 1: Discovery + use case scoping + data source mapping. Week 2-3: Agent topic + content authoring + connector configuration. Week 4-5: User testing + prompt tuning + escalation flow design. Week 6: Production deployment in Teams + governance integration. Week 7-8: Adoption coaching + analytics dashboard + hypercare. Agent quality requires iterative prompt tuning — first version is rarely production-ready without 2-3 prompt revisions.

Why EPC Group for Copilot Studio agent development?

EPC Group has been building Microsoft conversational AI since Power Virtual Agents (2019), now Copilot Studio. We bring: (a) Industry depth (healthcare, finance, government, manufacturing), (b) Integration expertise (custom connectors to proprietary systems), (c) Governance framework (agent sprawl prevention, Agent 365 integration), (d) Microsoft Solutions Partner with all six designations under the Microsoft AI Cloud Partner Program.

Related

Schedule Your Agent Development Discovery

Industry depth, governance and custom connectors.

Documented and anonymized engagements

Named engagements come first; anonymized summaries follow under the anonymized-engagement rule — the client is not named and every statement is EPC-reported. Documents behind named engagements are in the Evidence Center.

All case studies →

AI assistant — not a human