Hello
I purchased the Microsoft Copilot for Microsoft 365 for $30.00 monthly. Do i have access to copilot studio based on the items included in the license below?
The license includes the following items:
@HenryJammes.
I too am using Copilot for Microsoft 365 and looking at the licensing guide for this month.
Power Platform Licensing Guide April 2024.pdf
It says under use rights:
- Unlimited messages
- AI enabled conversations
- Create an publish plugins to customise Copilot
- Power Automate Cloud Flows
When creating an AI plugin you get the option of using an AI prompt, (it even says Copilot for Microsoft 365) - image below.
Yet, working in this way seems to be consuming AI builder credits on top of the Copilot for Microsoft 365 licensing.
Are you able to explain what can and can't be done under the Copilot for Microsoft 365 licensing in Copilot Studio, and what type of credits are consumed?
It appears as though a lot has changed in the platform since your post in March, following the release of the new licensing guide in April.
Hi,
I am using trial version of Copilot studio, but I don't get accurate answers about files stored in SharePoint.
Is it related to license? I mean if I will have the paid license, it will be fixed or not?
I asked simple questions about the content of files but I did not get any answer about it.
Also, as I checked, my custom copilot can only observe word and PDF files, and NOT Excel files. why?
Thanks in advance for your help.
Regards,
Farshad
It's also confusing in a way that for the other Power Platform services a premium license is required to be able to use premium and custom connectors whereas in Copilot Studio every Copilot for Microsoft 365 licensed user can create and publish a copilot (to Copilot for Microsoft 365) that includes such connectors. I'm aware Copilot Studio respects the existing DLP policies, but it's far from ideal from a governance perspective.
I agree that the licensing around the Copilot Studio line is confusing. I think the problem lies in the fact that the licensing is focused on the use of Copilot or bots rather than the creation of them. The creation of things is what Copilot Studio is all about. But the licensing really doesn't kick in until you put the artifacts into production.
Thanks @Pstork1 - understood. I just wish the Microsoft article was more specific about this limitation rather than being somewhat general. I believe the problem lies in the fact that there are so many flavours and variations of Copilot Studio, and to say that Copilot for Microsoft 365 includes Copilot Studio is not entirely accurate.
See HenryJames response above.
Extending Copilot for Microsoft 365 with Copilot Studio is covered by the Copilot for Microsoft 365 license. However, this only covers the creation and use of conversational plugins (https://learn.microsoft.com/en-us/microsoft-copilot-studio/copilot-conversational-plugins), not creating custom copilots and deploying them to
other channels.
I was also expecting to have access to Copilot Studio on purchase of Copilot for Microsoft 365. The following article from Microsoft employee, Richard Riley, states "Copilot Studio provides a visual canvas to create plugins, publish and manage them centrally, and secure them with the right access, data controls, and analytics. This is included in your Copilot for Microsoft 365 subscription and available in public preview today."
Is this information incorrect, or just misleading (because it isn't actually Copilot Studio that is included)?
Once the chatbot is built, using it is covered by the tenant license. Individual users don't need a license to use the chatbot.
Good morning,
I hope you are doing well. To my mind, copilot studio is a different offer and you will need a different license (a tenant license for your organizations and a free user license for each of the people building on copilot studio). However, if you want to try copilot studio and how it can expand the capabilities of copilot, there is a free trial of two months or so available.
Have a great day,
Hope it helps.
So just to make sure the distinction is clear: if you want to build a custom copilot (e.g. a copilot that will be embedded in SharePoint), you will need the Copilot Studio standalone license (and not M365 Copilot). That is a message-based license, and yes, messages are pooled at the tenant level. End users conversing with the copilot do not need licenses assigned to them - that is covered by consuming messages.
Copilot makers/builder do need per user licenses, but those do not incur additional costs.
WarrenBelz
146,660
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,999
Most Valuable Professional