M365Con 2027 – 無料オンラインカンファレンス · 11–22 Jan 2027 · 120 sessions m365con.net

API plugins for Microsoft 365 Copilot

Product

ランタイムで Copilot が外部の稼働中 API を呼び出す拡張性モデルで、通常はチケットの作成やレコードの更新などのアクションを実行します。データは Microsoft 365 にインデックス化されません。

◆ PRODUCTAPI plugins forMicrosoft 365 CopilotM365.FM
Title graphic: API plugins for Microsoft 365 Copilot (Product)

Description

API plugins for Microsoft 365 Copilot are an extensibility model in which Copilot calls a live external API at runtime, typically to perform an action such as creating a ticket or updating a record. The data behind the API is not indexed into Microsoft 365. Instead, the API stays hosted outside Microsoft 365 and is queried or modified on demand when a user asks for it in natural language.

According to the Microsoft Learn overview, API plugins are custom actions that let declarative agents in Microsoft 365 Copilot work with REST APIs that have an OpenAPI description. They are not standalone installable packages. Only the agent that contains a plugin can use its functions. Users can ask Copilot to read data and, if the API permits it, to create, update or delete data.

The mechanism rests on two descriptive artifacts. The plugin manifest tells Copilot how to discover the API, and the OpenAPI description supplies operations and parameters. Copilot reads the descriptions of the OpenAPI operations and parameters to decide which operation fits a request and how to map the user's input to parameters. Because the selection depends on these descriptions, clear and accurate wording in the OpenAPI definition affects how reliably Copilot invokes the right endpoint. Adaptive Card templates in the manifest control how results are displayed, and citation metadata can be taken from the API response.

Authentication and consent are part of the model. If the API requires authentication, the plugin obtains a token or key from a token store, and the agent asks the user to sign in when needed. Copilot requests consent on first use. After that, read operations run without confirmation, while write operations still ask the user first. Developers can override these defaults.

The documentation also names practical limits that influence design decisions. Up to five plugins in an agent manifest are always added to the prompt; beyond that, a semantic selection based on plugin descriptions applies. Quality can drop from about ten functions, and the token window truncates large inputs and outputs. Plugin authors therefore have reason to keep the set of functions focused and the responses compact. The documentation names no licensing requirements for API plugins.

The M365.FM episode "Build Custom Microsoft 365 Copilot Plugins" (14 August 2025) covers the same idea from a developer angle. The episode says that by providing an OpenAPI definition, developers enable Copilot to invoke API endpoints reliably, map parameters and handle responses, which makes it easier to build Copilot extensions and API plugins for Microsoft 365 Copilot. It also states that Power Automate flows and orchestrator patterns can be invoked by Copilot extensions to automate multi-step processes, so that Copilot can trigger business workflows, update systems and return results conversationally.

In practice, API plugins fit situations where the source of truth lives in another system and the goal is an action or a current lookup rather than a searchable copy of the content. Typical examples are opening a ticket in a service desk system or updating a record in a line-of-business application. Teams weighing this model against approaches that index data into Microsoft 365 should consider that API plugins always depend on the availability and behavior of the external API at the moment of the request.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeProduct
DocumentationAPI plugins for Microsoft 365 Copilot – Microsoft Learn learn.microsoft.com

Articles about API plugins for Microsoft 365 Copilot (2)

API plugins for Microsoft 365 Copilotを扱った記事:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

API プラグインと Microsoft 365 Copilot のインデックス化されたデータの違いは何ですか? (AI)

API プラグインでは、Copilot がランタイムで外部の稼働中 API を呼び出し、データは Microsoft 365 にインデックス化されません。API は Microsoft 365 の外部でホストされ、オンデマンドで照会または変更されます。

API プラグインが動作するには何が必要ですか? (AI)

REST API と OpenAPI の説明、およびプラグインのマニフェストが必要です。Copilot は操作とパラメーターの説明を使って呼び出す操作を選択し、プラグインは宣言型エージェントの一部である必要があります。

Copilot は API プラグインを使用する前に確認を求めますか? (AI)

Copilot は初回使用時に同意を求めます。その後、読み取り操作は確認なしで実行され、書き込み操作では引き続き確認が求められます。開発者はこれらの既定値を変更できます。

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

API plugins for Microsoft 365 Copilotに詳しいコミュニティメンバー:

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: