Use Plugin Actions in Microsoft Copilot Studio (Preview)

Microsoft Copilot Studio empowers users to enhance their Copilot's capabilities by integrating plugin actions. These actions enable Copilot to respond automatically to user queries or be explicitly called within a topic. Let's delve into the core plugin action types, how to add and call them, and testing their functionality.

Core Plugin Action Types:

Plugin actions are categorized into four core action types:

1. Prebuilt Connector Action:

These actions leverage prebuilt connectors within the environment to execute specific tasks.

2. Custom Connector Action:

Custom connector actions allow users to define custom processes tailored to their unique requirements.

3. Power Automate Cloud Flow:

Users can incorporate Power Automate flows to automate tasks seamlessly.

4. Bot Framework Skill:

Bot Framework skills enable the integration of external bot capabilities into Copilot workflows.

Adding a Plugin Action:

To add a plugin action in Copilot Studio, follow these steps:

1. Open Copilot Studio and navigate to "Topics & Plugins."

2. Select "+ Add" and choose "Plugin action (preview)."

3. Search for the desired plugin action and select it.

4. Configure the connection for the action as prompted.

5. Review and finalize the plugin action configuration.

Calling a Plugin Action:

Plugin actions can be called automatically in response to relevant user queries or explicitly within a topic. To call a plugin action explicitly:

1. Create a new topic or select an existing one.

2. Add trigger phrases to initiate the action.

3. Add a node and select "Call an action" from the plugin actions tab.

4. Choose the desired plugin action and save the topic.

Testing Your Plugin Action:

To ensure the functionality of your plugin action, test it by engaging with Copilot in a relevant chat scenario. Toggle the chat pane to interact with Copilot and observe its response to your queries. During testing, Copilot dynamically selects and executes plugin actions based on the context and user input.

Overriding Inputs and Authentication:

Users have the flexibility to override inputs for plugin actions, providing explicit values instead of prompting users. Additionally, some plugin actions, particularly those based on AI Plugins, require authentication. This ensures secure execution within the Copilot runtime environment. Authentication methods include integrated authentication for Teams and Power Apps or manual authentication for third-party bots.

In conclusion, leveraging plugin actions in Microsoft Copilot Studio enables users to extend Copilot's capabilities, automating tasks and enhancing user experiences. By understanding core action types, adding, calling, and testing plugin actions, users can optimize Copilot's functionality to suit their specific needs and workflows.