Copilot Studio setup: licenses, credits and your first agent
Diesen Beitrag auf Deutsch lesen
A practical guide to Copilot Studio licensing, Copilot Credits, environment setup, billing policies, first-agent creation and external connectors.
TL;DR
Copilot Studio requires maker licensing for builders and Copilot Credits for agent usage. The guide compares trial, Teams and standalone plans, explains pay-as-you-go and capacity options, and outlines five setup steps: licensing, environment provisioning, billing configuration, agent creation and testing. It also shows how agents can invoke Power Automate flows and custom connectors.
Original by Divya Akula, on Divya Akula. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Confirm whether trial, Teams or standalone access supports the channels, generative features and connectors your agent needs.
- Admins/IT: Provision a dedicated environment, assign the required tenant and maker access, and link a billing policy before production use.
- Leadership/Business: Measure real credit consumption with pay-as-you-go before committing to a capacity pack, because agent actions and generative responses consume credits.
Frequently asked questions
Which Copilot Studio licenses are needed for a standalone deployment?
A standalone deployment needs a tenant license for the organisation and a user license for each maker. End users do not need licenses.
How do Copilot Credits work in Copilot Studio?
Copilot Credits measure compute from retrieval, reasoning, actions, tool calls and interactions. They can come from pay-as-you-go, capacity packs or pre-purchase plans.
How do I create and test a first Copilot Studio agent?
Create a Power Platform environment, configure licensing and billing, then choose Create, New agent and describe its purpose. Test it before publishing.