Copilot Studio, Unlocked: Licenses, Credits & First Steps

What is Copilot Studio?

Microsoft Copilot Studio is the low-code platform for building AI agents that don’t just respond — they act. Whether you’re extending Microsoft 365 Copilot, wiring up custom APIs, or orchestrating multi-agent workflows, this guide gets you from zero to first agent with a clear-eyed view of what licenses you actually need.

Copilot Studio sits at the intersection of conversational AI and business process automation. Built on the Power Platform, it lets you design agents using a visual canvas, natural language, or code — then deploy them to Teams, websites, Dynamics 365, or any custom channel via API.

As of 2025, Copilot Studio supports two orchestration models:

• Classic orchestration — deterministic topic-based flows
• Generative orchestration — the LLM dynamically decides which topics and actions to invoke

For new builds targeting agentic scenarios, generative orchestration is the default and recommended path.

Understanding the license model

Copilot Studio licensing has two dimensions: who builds (maker licenses) and how much runs (consumption credits).

You need both in production.

Maker licenses (who can build)

Every developer who creates or manages agents needs a maker license. There are three ways to get one.

Copilot Credits (how much runs)

Credits measure the compute effort of each agent interaction — retrieval, reasoning, action execution, tool calls. They’re consumed whenever a user talks to an agent or an agent acts autonomously.

Three ways to supply them:

Feature comparison by plan

Setting up your environment

Copilot Studio runs inside a Power Platform environment. You’ll need at least a default environment to get started, but for any real project you should provision separate environments for development, test, and production.

Connecting external systems

One of Copilot Studio’s main strengths is its connector ecosystem. You can call external APIs, trigger Power Automate flows, and invoke Azure AI services — all from within a topic or an autonomous action.

# Call an external REST API from a topic action
kind: AdaptiveDialog
actions:
  - kind: InvokeFlowAction
    flow: "/providers/Microsoft.Flow/flows/{flowId}"
    inputs:
      query:    "=${System.Activity.Text}"
      userId:   "=${System.User.PrincipalName}"
    outputs:
      result:   FlowResponse

# Or call a custom connector directly
  - kind: InvokeConnectorAction
    connector: "shared_myapi"
    operation: "GetComplianceStatus"
    inputs:
      aerodromeId: "=${Topic.AerodromeId}"

Developer pre-flight checklist

Before going into your first build, confirm these are in place:

• Work or school Microsoft 365 account (no personal email)
• Access to Power Platform Admin Center (System Admin or Environment Maker role)
• Copilot Studio tenant license assigned to your org (or active trial)
• Copilot Studio User License assigned to your account
• Dedicated Power Platform environment (non-default recommended for dev)
• Billing policy created and linked to environment (required to consume credits)
• Azure subscription available if using pay-as-you-go metering
• DLP policies reviewed in PPAC (these can block connector usage silently)
• For M365 extension: M365 Copilot license on the agent-publishing account

Cost planning tips

The most common licensing pitfall is underestimating credit consumption once you add generative features. A few practical strategies:

Last updated May 2026 · Licensing details subject to change