Build API plugins from an existing API for Microsoft 365 Copilot

Important

API plugins are currently only supported as actions within declarative agents. They are not enabled in Microsoft 365 Copilot. See Add a plugin for an example of adding an API plugin to a declarative agent.

API plugins connect your existing REST API to Microsoft 365 Copilot. You can use the Teams Toolkit to generate a plugin from an existing REST API with an OpenAPI specification.

Prerequisites

• Requirements specified in Requirements for plugin development
• An existing REST API with an OpenAPI specification (this walkthrough uses the Budget Tracker sample API)
• Visual Studio Code with Teams Toolkit version 5.9 or later (if using Teams Toolkit to generate the plugin)
• Teams Toolkit
• Optional: Microsoft Kiota Visual Studio Code extension

Tip

For the best results, make sure that your OpenAPI specification follows the guidelines detailed in How to make an OpenAPI document effective in extending Copilot.

To follow along with this guide, download the Budget Tracker sample API and configure it to run on your local development machine. Build and run the sample at least once to generate the openapi.yml file for the API.

Enable plugin development in Teams Toolkit

1. Open Visual Studio Code. If Teams Toolkit isn't already installed, see Install Teams Toolkit for installation instructions.

2. Select File -> Preferences -> Settings. In the Settings window, search for copilot to locate the Fx-extension: Develop Copilot Plugin option. If not already enabled, enable the setting.

3. In the Settings window, search for kiota to locate the Fx-extension: Enable Microsoft Kiota option. If you want to enable Kiota, enable this option. Otherwise, disable it. For details, see Benefits of enabling Microsoft Kiota.

4. If you made any changes to settings, restart Visual Studio Code before proceeding.

Benefits of enabling Microsoft Kiota

Enabling Microsoft Kiota in Teams Toolkit has the following benefits.

• The user interface for selecting operations from the OpenAPI document is replaced with an API explorer that is better suited for large OpenAPI documents.
• The developer is able to search for public OpenAPI descriptions using Kiota's search command.

Create the plugin

API plugins are a ZIP file that contains the following files.

• The OpenAPI specification for the REST API.
• An API plugin manifest that references the included OpenAPI specification and describes the available operations, authentication method, and response formats.
• A Teams app manifest (for example, manifest.json) with a copilotExtensions property that references the API plugin manifest.

1. Open Visual Studio Code. If Teams Toolkit isn't already installed, see Install Teams Toolkit for installation instructions.

2. Select the Teams Toolkit icon in the left-hand Activity Bar.

3. Select Create a New App in the Teams Toolkit task pane.

   

4. Select Copilot Extension, then select API Plugin.

5. Select Start with an OpenAPI Description Document.

The next steps differ depending on if you enabled Microsoft Kiota or not.

Teams Toolkit without Kiota

1. Select Browse and browse to the location of the OpenAPI specification from the Budget Tracker sample, located at ./openapi/openapi.yml.

2. Select all the operations to enable for the plugin.

   

3. Choose a location for the API plugin project.

4. Enter Budget Tracker as a name for the plugin.

Teams Toolkit with Kiota

1. Select Browse path and browse to the location of the OpenAPI specification from the Budget Tracker sample, located at ./openapi/openapi.yml.

2. The side bar view changes to the Kiota API explorer. Use the Add all button to select all the operations to enable for the plugin.

   

3. Select the Generate button in the Kiota API explorer.

   

4. Choose a location for the API plugin project.

5. Enter Budget Tracker as a name for the plugin.

Once you complete these steps, Teams Toolkit generates the required files for the plugin and opens a new Visual Studio Code window with the plugin project loaded.

Note

If your identity server requires Proof Key for Code Exchange (PKCE), uncomment the following line in teamsapp.yml in the API plugin project.

# isPKCEEnabled: true

Package and sideload the plugin

1. Open the plugin project in Visual Studio Code.

2. Select the Teams Toolkit icon in the left-hand Activity Bar.

3. In the Accounts pane, select Sign in to Microsoft 365. (If you're already signed in continue to the next step).

4. Confirm that both Custom App Upload Enabled and Copilot Access Enabled display under your Microsoft 365 account. If they don't, check with your organization admin. See Requirements for plugin development for details.

5. In the Lifecycle pane, select Provision.

6. When asked to Enter client id for OAuth registration..., enter your Plugin client ID.

7. When asked to Enter client secret for OAuth registration..., enter your Plugin client secret.

8. Read the message in the dialog and select Confirm to continue.

9. Wait for the toolkit to report that is finished provisioning.

   

Your plugin is now available to test with your user account in Microsoft 365 Copilot in Microsoft Teams.

Use the plugin

1. Open Teams in your browser and sign in with the Microsoft 365 account you used to upload your plugin.

2. Select Chat in the left-hand Activity Bar.

3. Select Copilot in the Chat pane.

4. In the message compose area, select the Plugins icon, then enable Budget Tracker in the Plugins flyout.