Deploy Copilot Studio Agents to Microsoft 365 Copilot Without Per User Licenses
Diesen Beitrag auf Deutsch lesen
Copilot Chat users can access Copilot Studio agents through Copilot Credits, while admins govern deployment, capacity allocation and channel behavior.
TL;DR
Copilot Studio agents can be published to Microsoft 365 Copilot through the Make agent available in Microsoft 365 Copilot toggle. Copilot Chat users do not need a Microsoft 365 Copilot license, because usage can use Copilot Credits. From April 20, 2026, standalone prepaid capacity packs no longer require an Azure subscription.
Original by Henry Jammes, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Enable the Microsoft 365 Copilot channel and replace Conversation Start logic with an Activity Event trigger, because Conversation Start is unsupported there.
- Admins/CoE: Use Copilot Credit Policies for Entra ID groups and pin agents for target users, so capacity and rollout can be managed centrally.
- Security/Compliance: Test agents in both Teams and Microsoft 365 Copilot, because features such as embedded URLs, Adaptive Cards, hand-off and feedback behave differently.
Frequently asked questions
How do I make a Copilot Studio agent available in Microsoft 365 Copilot?
Connect the Teams and Microsoft 365 Copilot channel, then enable Make agent available in Microsoft 365 Copilot. Users can select it with @.
Do Copilot Chat users need a Microsoft 365 Copilot license for Copilot Studio agents?
No. Copilot Chat is sufficient, and agent consumption can be covered through Copilot Credits rather than per user Copilot licensing.
Why does Conversation Start not work for a Copilot Studio agent in Microsoft 365 Copilot?
Microsoft 365 Copilot does not support the Conversation Start system topic. Use an Activity Event triggered topic when context values are unknown.