What happens when Microsoft decides to "reimagine" their different agentic AI authoring toos to be called #CopilotStudio? The usual confusion and chaos, of course.
Yet before MS made this announcement last week, I hadn't really looked at _how_ different the 2 models for adding your own agents to #Microsoft365 #Copilot actually are.
That's the topic of this week's Perspectives on #PowerPlatform newsletter issue: https://www.perspectives.plus/p/lite-side-dark-side-of-copilot-studio
When I started putting together this comparison table of Copilot Studio lite experience vs. Copilot Studio full experience, I realized that these are far more disjointed than I had imagined.
When licensing is the most unified thing of a Microsoft product, that's quite a surprising result.😅
With one built on M365, the other founded on the low-code roots of Power Virtual Agents, these are not gonna get magically unified anytime soon...
The fact that MS has decided to skip the accurate references to lite vs. full experience in #MicrosoftLearn documentation will cause all kinds of fun misinformation to spread via search results and ChatGPT answers. Here's an example related to the #Dataverse knowledge support of #CopilotStudio
Great news! We can soon copy Copilot Studio Lite Experience agents into the Full Experience! This solves... almost nothing about the real complexity of #CopilotStudio agents built on 2 completely different platforms of #Microsoft365 vs. #PowerPlatform.
https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/copy-agent-to-copilot-studio/
Copying doesn't preserve all knowledge of the #Copilot agent, because of technical differences in how those are managed. It's more just an agent JSON manifest copy from one service to another. Useful, but not a big help.
Jukka Niiranen