Preface: Just to be clear because there's a lot of copilot language going on, I am NOT referring to creating agents directly in the full Copilot Studio application, I am referring to the ability for anyone with a Copilot for M365 license to be able to go into the Copilot application in O365 and create custom agents from there.
According to the documentation found here -
https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/copilot-studio-agent-builder#data-storage - agents created using Copilot Studio Agent Builder are stored in our tenant's Cosmos DB storage and are not created in Dataverse, unlike the agents built in the full Copilot Studio application. Currently, there is a greyed-out option in the top right corner labeled 'Open in Full version'; this upcoming feature will allow you to transfer your custom agent to Copilot Studio. My question is, what are the implications of choosing this option? Will it create Dataverse components? Do users need a 'Copilot Studio User' license to extend their custom agents built in Copilot Studio Agent Builder to the full Copilot Studio app? When choosing this option will it always go to the default power platform environment or can you configure it to take the user to a separate environment? My primary concern is the sprawl of agents and how we can manage or restrict agent creation.
Side Note: Ideally in Copilot Studio Agent Builder it would be fantastic if you can extend your custom agents capabilities in the full Copilot Studio application without it ever creating dataverse components. Just keep everything in Cosmos.
TLDR: I don't want a bunch of agent components created in my default dataverse environment