New Sample Types - Support for Copilot Studio Solutions and Source Code

[pkbullock]

Requires some discussion, but id like to allow for samples using Copilot Studio agents.

• There is a structure in place in for sample templates, here is Power Platform sample templates: https://github.com/pnp/powerplatform-samples/tree/main/templates
• Prefix could be cps, e.g. mcs-MyCoolAgent
• Metadata and sample.json setup will be needed

[sebastienlevert]

The discussion to have is whether MCS is considered "pro-dev". I understand the need and I'm open to it. Though, I don't know how much they really are "transportable"?

[pkbullock]

There is another aspect, I am considering is, whether to rename this repo removing pro-dev element. e.g. Copilot-Agents, as an idea. The renaming is an idea atm. Thoughts?

[pkbullock]

MCS solutions can be exported like PowerApps/Power Automate

[garrytrinder]

The discussion to have is whether MCS is considered "pro-dev". I understand the need and I'm open to it. Though, I don't know how much they really are "transportable"?

It's a good question.

We might want to consider how we approach this, for an MCS solution we would not storing source code (unpacked solution files), so it becomes more of a file share for solution files.

[garrytrinder]

There is another aspect, I am considering is, whether to rename this repo removing pro-dev element. e.g. Copilot-Agents, as an idea. The renaming is an idea atm. Thoughts?

If we were to include MCS solutions in this repo then we might want to consider renaming it to something like, Microsoft-365-Copilot-Agent-Samples, this makes it clear that it's for Microsoft 365 Copilot Agents and not Copilot consumer product.

For folks interested in MCS can be exposed to other approaches like VS Code + Microsoft 365 Agents Toolkit, which they may not be aware of. I've had this experience with folks in the past where I've showed them the "pro-code" approach for building declarative agents and they were just not aware that it existed, the view they had was that you could only create Agents for Microsoft 365 Copilot was using MCS. In a few cases, folks started to preferred to use the pro-code approach after comparing approaches and understanding the pros and cons.

[pkbullock]

The discussion to have is whether MCS is considered "pro-dev". I understand the need and I'm open to it. Though, I don't know how much they really are "transportable"?

It's a good question.

We might want to consider how we approach this, for an MCS solution we would not storing source code (unpacked solution files), so it becomes more of a file share for solution files.

If we think of solution packages, then its comparable to EXEs, MSIs, folks may want to know whats in them. I think there is some learning to be gained from the https://github.com/pnp/powerplatform-samples repo how they handle submissions from Power Platform. Ultimately, these packages are a bunch of JSON, XML, Yaml contents for the agent.

[sebastienlevert]

Also to confirm... There is no Copilot Studio samples repo today?

[garrytrinder]

If we think of solution packages, then its comparable to EXEs, MSIs, folks may want to know whats in them. I think there is some learning to be gained from the https://github.com/pnp/powerplatform-samples repo how they handle submissions from Power Platform. Ultimately, these packages are a bunch of JSON, XML, Yaml contents for the agent.

I think the safe approach would be to store the unpacked files as source code and give folks instructions on how to build/pack the solution themselves.

[garrytrinder]

Also to confirm... There is no Copilot Studio samples repo today?

I don't believe there is a community repo, but it is being discussed.

Maybe @Laskewitz knows if there is an official repo for Copilot Studio samples.

[pkbullock]

I found this one: https://github.com/microsoft/CopilotStudioSamples, it doesn't appear to be integrated into the Sample Gallery for extra exposure but does have regular commits. If the advocates are considering their own initiative, then we could differ this, or in some way signpost to other samples on the docs site. I have built a collection of resources that MS have in various pots, which folks might find useful in exploring.

[Wajeed-msft]

Recently there was an VS code extension released to bring solution file in local. I am checking with Sarah if they can allow export of code so that it can be added directly in GitHub as sample rather than a .zip file for solution.

Copilot Studio Extension for Visual Studio Code Is Now Generally Available | Microsoft Copilot Blog

[Laskewitz]

Also to confirm... There is no Copilot Studio samples repo today?

I don't believe there is a community repo, but it is being discussed.

Maybe @Laskewitz knows if there is an official repo for Copilot Studio samples.

We use powerplatform-samples (http://aka.ms/powerplatform-samples) for that. So yes. There is.

[pkbullock]

Recently there was an VS code extension released to bring solution file in local. I am checking with Sarah if they can allow export of code so that it can be added directly in GitHub as sample rather than a .zip file for solution.

Copilot Studio Extension for Visual Studio Code Is Now Generally Available | Microsoft Copilot Blog

I am finding that the CLI can do that, like: "pac solution clone --name multiagentdemo --outputDirectory . --packagetype Unmanaged" - borrowed from Power Platform Samples. will return the code without the zip.

[kaul-vineet]

@garrytrinder CAPE team is now working on cross product solutions = M365 + Copilot Studio. They are really cool demo components. If we use the Copilot Studio Extension for Visual Studio Code Is Now Generally Available | Microsoft Copilot Blog are we open to publish code to this repo?