Employ user authentication and parameters in plugins

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	Jul 22, 2024	-

Business value

When building a plugin to Microsoft Copilot, a key value is to be able to specifically access the data specific to a user or scenario. Parameters and Entra ID authentication make it possible to narrow the request to exactly what the user is looking for.

Feature details

With Copilot Studio plugin extensibility for Microsoft 365, the user's authentication token is used to invoke the plugin, which means that capabilities such as generative answers are immediately more useful as they can use corporate resources in the plugin on the user's behalf, such as Microsoft SharePoint.

With parameters, a plugin maker can define a set of parameters to be collected by Microsoft Copilot before calling the plugin. Internal to the plugin, these parameters can be used to call external functions, exercise business logic, or otherwise as the maker sees fit.

Copilot Studio makes it easy to define parameters and provide descriptions to Microsoft Copilot so it can automatically determine how to prompt the user to provide the needed information.

Geographic areas

This feature will be released into the following Microsoft Azure geographic areas:

• Switzerland
• United States
• Europe
• Asia Pacific
• United Kingdom
• Australia
• Brazil
• Canada
• India
• Japan
• France

See also

Add an action to a copilot extension (docs)