[Microsoft Copilot Studio]Copilot 连接器、操作和扩展概述（预览）

[This article is prerelease documentation and is subject to change.]

Not every action type is available for every copilot:

You create and configure actions in Copilot Studio. You can also create and edit some types of actions in Power Apps. Learn more in Create a prompt (preview) in Power Automate or Power Apps.

In order to use the content sources, you have to define authentication for the source. Sources require specific types of authentication. When you select your content, the source provides the needed prompts for authentication.

Here are some examples:

• Non-authenticated: MSN Weather connector. This connector action only retrieves public weather data and has no secure content. As a result, the weather connector is open to be used without providing credentials.
• Flow actions: Cloud flows use the connection and connection settings configured at time of creation.
• Connector actions: If you use a Connector to access your data source, it has its authentication method built in to the connector. You will not configure it at setup but will be asked to supply credentials before testing or using the connection.
• Prompt action: Uses your Teams or Power Apps identity. Make sure to share the prompt to the appropriate users or groups after is created.
• Conversational actions: Conversational actions don’t need any authentication of their own. However a Conversational action can be used to call a connector action, in which case the connector’s authentication mechanism is invoked.

Each source has actions already defined, but when configuring, you can select which of the actions you wish to use. You can select from any number of actions to use with the source. For example, with multiple actions, you could perform the following:

• Retrieve a list of users
• Add a new user
• Update a user's details
• Delete a user

As long as the actions are present in the source, the handler can carry out any of the actions.

Inputs and outputs are specific to an action and provide all of the data input options possible for an action and define the results to return. These parameters are provided by the content source (connectors, and so on) and can't be added to or removed. However, descriptions can be updated to provide a better understanding of the inputs and outputs. They're displayed as part of the setup to provide visibility into what needs to be included in a query and what is returned.

Enhanced features are available when setting up extensions for some Copilot types.

Enhanced features include:

• Solutions
• User consent
• Conversation starters
• Adaptive Cards
• Testing

Not all enhanced features are available in every copilot type.

Solutions are essential for application lifecycle management. If saved in a solution an action can be easily moved across environments. By default, the system selects the most suitable solution for you, based on the preferred solution, or a solution where connector components are present. You can also change solution. If you don't specify a solution for your action, the system automatically creates a solution at runtime.

Learn more about solutions in Application lifecycle management (ALM) basics with Microsoft Power Platform.

User consent is a toggle provided on each action. It determines if the copilot will prompt users to continue when executing an action. Turning on this option means that the copilot will ask users if they're sure they want to take the action. This helps prevent unintentional actions that could affect data.

Best practices:

• For data retrieve-only actions (get, retrieve, list, and so on), turn off user consent. Such actions only retrieve a set of data and display it. They don't put the data at risk.
• For other actions (create, update, delete, add, remove, and so on), turn on user consent. Such actions can add or change data in the system, so it's a good idea to prompt users to confirm before taking action. You can always change user-consent settings for the plugin by editing it.

Conversation starter lets you create commonly used questions that display as clickable buttons. Conversation starters execute the query immediately. They also show types of queries that can be used. These examples can help users come up with more queries on their own using successful natural language framing. Conversation starters are set at the plugin level rather and are optional. You can edit them at any time.

Adaptive cards are an optional component configured at the action level. You can add or modify them at any time by editing the plugin. Adaptive cards provide an alternative way of displaying results from a copilot query.

Adaptive cards come in two types:

• Default: A basic adaptive card that can have a title, a subtitle, a body, and a button that takes the user to a URL location. It provides a more stylized view and a call to action.
• Custom: Custom adaptive cards are created outside of the wizard and can be uploaded for inclusion in a plugin. These cards are more customizable and can have multiple fields, multiple buttons, and other options. You can create a custom card in Adaptive Card Designer and export it as a file for upload.

When configuring the default adaptive card, you must select a root path. The root path is a segment of the data source's configuration file and it includes all the fields that can be selected to define the title or body. There can be multiple root paths in a source file, and all available paths are available for selection. After you select a root path, you can choose the desired title and body from lists.

Every adaptive card shows the returned values and then lists the references used when compiling the result. Adaptive cards also allow a user to specify the reference view layout. This is how the references used in the query are displayed for more information. It allows for inclusion of a title, URL, and subtitle. These are also dropdowns that can be populated based on the root path selection.

For connector actions, a maker can test the new plugin inside of Microsoft 365 by sideloading the plugin created. This is an option on the review screen when the action has been authored. It will prompt the user to select or create a connection, and then create a side loaded test version of the plugin that is available in the M365 environment. This is not visible externally and is not published for admin approval. It is only available for the author so that it can be used only to validate that the plugin is working as expected.

End users in your tenant can use conversational and AI actions in their chats with Microsoft Copilot if:

• Your Microsoft 365 tenant admin deploys the Copilot Studio app in the Microsoft 365 admin center.
• The end user enables the connection from within their chat with Microsoft Copilot. Available plugins can be enabled through the plugins menu or through the Power Platform plugins configuration portal.

1. Sign in to the Microsoft 365 admin center with your admin account.
2. Expand Settings on the side navigation pane and select Integrated apps.
3. Go to the Available apps tab and select the entry Microsoft Copilot Studio. The app's details pane opens.
4. Select Deploy to enable the app in chats with Microsoft Copilot.

Tenant admins can enable or disable:

• Showing Conversational AI/topic actions and Prompt actions in the M365 Chat app using the "Copilot Studio" app.
• Showing Flow actions in the M365 Chat app using the "Power Automate" app.
• Connector actions and API actions in the M365 Chat app using the associated apps (the app name will be the connector or action name). Additionally, custom connector actions are available in the Teams store for users to install.

Microsoft Copilot end users need to enable plugins before they use them in chat. Available plugins can be enabled through the plugins menu or through the Power Platform plugins configuration portal.

They can get to the portal by asking about plugins in their chat with Microsoft Copilot. They receive a short summary about plugins and a link to the portal:

Users can also ask directed questions about data connections or how to perform cross-organizational tasks, for example they could ask:

• How can I use a plugin?
• Tell me about Power platform Copilot plugins
• How can I get data from an external system?
• How can I get data from Salesforce?

By default, actions are only visible and usable in Microsoft Copilot by the person who authored them.

However, the action author can share their plugins in the portal where they created them. For example, you can share an AI Builder prompt from the AI prompts page by selecting Share for the prompt. The same applies for Power Automate flows (from the Flows page in Power Automate) or for custom connectors from the Custom connectors page.