When publishing an agent via Copilot Studio to Teams & Microsoft 365 Copilot (especially asking for Copilot) the agent becomes available in the Agent section of Copilot for all those with Viewer rights (managed via the Share Settings in Copilot Studio), right?
Do those end-users need a "Pro"-License (Copilot with Add-On License) or is the standard Copilot Chat License sufficient to use the agent via Copilot Chat?
And how is it billed when using the agent inside an organization?
you could share two way the agents from copilot studio : by share from the agent or by ask an admin to publish the zip of the agent.
Share by agent is limited to 98 people.
Zip is limited to people, group or all org.
So for "normal user" who don't have copilot 365 premium licences.
If it's an agent coming from copilot studio you need to have copilot credit or pay as you go credit assign to the environnement wich store the agent.
If you it's an agent made with agent builder by a copilot 365 user and you share it inside copilot chat to all company (you could download it as zip and ask an admin to publish to all company), if it only containt feature that exist in copilot studio : you need to have configure the "pay as you go" on the copilot chat menu in admin (and then you can remove it and only use copilot credit). If an agent from agent builder use copilot 365 feature not avaiable in copilot studio : the agent will show an error message "user need copilot 365"
So end user don't need mandatory copilot 365, only credit (if it use copilot studio feature).
User with copilot 365 will not alway consume credit, in the link there is a table showing that for most conversationnal use case , copilot 365 premium user will not consume credit. Carefull : AI Builder prompt tool consume credit in all case (even inside a power automate or agent flow)
I hope it help you to understand :) if yes please use the checkbox to mark the answer as answered, it's important for the community and search engine :)
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.