Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This content is archived and is not being updated. For the latest documentation, go to the Microsoft Copilot Studio overview. For the latest release plans, go to Dynamics 365, Power Platform, and Cloud for Industry release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | - | 
Sep 16, 2024 |
Business value
Organizations have wrestled with the "many bots" problem in the past, never quite landing on the right mechanism that balances discovery, appropriate routing and permissions, and capability with the individualized scenarios that modern workers need help with. Copilot extensions rectify this problem, by making it quick and easy for anyone in your organization to create useful, tailored Microsoft Copilot experiences that can generate answers, take action, and provide information that is specific to your business, your data, and your employees.
Feature details
Copilot extensions in Microsoft Copilot for Microsoft 365 are created by employees in your organization to retrieve information or perform actions through Copilot.
With this feature, these extensions can be created and shared in one, simple canvas that all Microsoft Copilot users can access. This means employees in your organization can quickly and easily create work-specific extensions in a familiar experience; they don't have to learn a new app or service, and the extensions will be instantly available in Microsoft Teams or at https://microsoft365.com/chat.
Microsoft 365 Copilot is a seat-licensed product that includes the Microsoft Copilot Studio license, meaning anyone can be a maker. These nascent makers can be using Copilot Extensions in Microsoft 365 Copilot, or browsing the Microsoft 365 Copilot Extension store to install one, see the "create a copilot extension" call to action and be taken to the studio.
For example, an employee might want to create an extension for Copilot to handle internal queries and requests for creating, managing, and approving tasks within an expense reporting system.
When the maker has created their copilot extension, they can expand its knowledge with data sources from SharePoint and Microsoft Graph, enabling richer, more informed answers that are contextually scoped. Makers can also create "actions", which allow the maker to connect their extension to enterprise and internet systems to perform tasks—doing everything from getting the weather to resolving a ticket in a customer management portal.
The copilot extension, with its knowledge and its actions defined, can then be published to Microsoft Copilot, where an end user can get information based on the knowledge sources provided and interact with the capabilities offered by the actions, right in Microsoft Copilot.
Admins can trust these copilot extensions as well; all of them leverage the same Microsoft large language model, admins in Power Platform can govern which power platform tools can be used in a copilot action, and Microsoft 365 admins can govern who can use the copilot extension.
Geographic areas
This feature will be released into the following Microsoft Azure geographic areas:
- Germany
- US Sec
- US Nat
- Norway
- Singapore
- South Africa
- Switzerland
- United Arab Emirates
- US GCC
- US GCC High
- United States
- Europe
- Asia Pacific
- United Kingdom
- Australia
- Brazil
- Canada
- India
- Japan
- France
- Korea
- US Gov
- US DoD