This repository contains samples and artifacts for Microsoft Copilot Studio.
Older samples and labs, largely focused on Power Virtual Agents, have been moved to the Legacy branch of this repo.
| Description | Link |
|---|---|
| Home page | aka.ms/CopilotStudio |
| Official blog | aka.ms/CopilotStudioBlog |
| Community forum | aka.ms/CopilotStudioCommunity |
| Product documentation | aka.ms/CopilotStudioDocs |
| Guidance documentation | aka.ms/CopilotStudioGuidance |
| Try Copilot Studio | aka.ms/TryCopilotStudio |
| Description | Link |
|---|---|
| M365 Agents SDK | Github Repo for the M365 Agents SDK |
| M365 Agents SDK - C# | Github Repo for the C# M365 Agents SDK |
| M365 Agents SDK - JavaScript | Github Repo for the M365 Agents SDK |
| M365 Agents SDK - Python | Github Repo for the M365 Agents SDK |
| Adaptive Cards | Adaptive Cards docs and builder |
| Web Chat | Web Chat Github Repo |
| Power Platform Snippets | Copilot Studio snippets |
| Sample Name | Description | View |
|---|---|---|
| 3rdPartySSOWithOKTA | Demonstrates how to implement a seamless SSO experience with a 3rd party authentication provider | View |
| Adaptive Card Samples | YAML sample with a dynamics Adaptive Cards (Power Fx) | View |
| ImplementationGuide | The implementation guide document provides a framework to do a 360-degree review of a Copilot Studio project. Through probing questions, it highlights potential risks and gaps, aims at aligning the project with the product roadmap, and shares guidance, best practices and reference architecture examples | View |
| Dataverse Indexer | Index the content of a SharePoint library into a Copilot Studio Agent as knowledge source files, along with citations that point to the source files in SharePoint | View |
| Load Testing | JMeter test plan to use as a starting point for load testing conversational agents built with Copilot Studio | View |
| RelayBotSample | Demonstrates how to connect your bot to existing Azure Bot Service channels | View |
| SharePointSSOComponent | A SharePoint component demonstrating how copilots can be deployed to SharePoint sites with SSO enabled | View |
| Type Ahead Suggestions | Demonstrates typeahead suggestion functionality for your custom copilot that can assist users finding things like frequently asked questions, auto correcting typos and showing a list of menu items like product names or topic names before sending a message to the copilot | View |
| WebChat Customization | Shows the Customization Options from the Azure AI Bot Services as well as some CSS to drastically change the look of your Copilot agent | View |
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Although the underlying features and components used to build these samples are fully supported (such as Copilot Studio bots, Power Platform products and capabilities, etc.), the samples themselves represent example implementations of these features. Our customers, partners, and community can use and customize these features to implement capabilities in their organizations.
If you face issues with:
- Using the samples: Report your issue here: aka.ms/CopilotStudioSamplesIssues. (Microsoft Support won't help you with issues related to the samples, but they will help with related, underlying platform and feature issues.)
- The core Microsoft features: Use your standard channel to contact Microsoft Support: Community help and support for Microsoft Copilot Studio.
This project has adopted the Microsoft Open Source Code of Conduct.
Resources:
- Microsoft Open Source Code of Conduct
- Microsoft Code of Conduct FAQ
- Contact opencode@microsoft.com with questions or concerns
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include Microsoft, Azure, DotNet, AspNet, Xamarin, and our GitHub organizations.
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's Microsoft's definition of a security vulnerability, please report it to us as described below.
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them to the Microsoft Security Response Center (MSRC) at https://msrc.microsoft.com/create-report.
If you prefer to submit without logging in, send email to secure@microsoft.com. If possible, encrypt your message with our PGP key; please download it from the the Microsoft Security Response Center PGP Key page.
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at microsoft.com/msrc.
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.
If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our Microsoft Bug Bounty Program page for more details about our active programs.
We prefer all communications to be in English.
Microsoft follows the principle of Coordinated Vulnerability Disclosure.
Copyright (c) Microsoft Corporation. All rights reserved.