API plugins for Microsoft 365 Copilot
Product
Modelo de extensibilidade em que o Copilot chama uma API externa em tempo real, normalmente para executar ações como criar um chamado ou atualizar um registro; os dados não são indexados no Microsoft 365.
Descrição
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.
| Tipo | Product |
|---|---|
| Documentação | API plugins for Microsoft 365 Copilot – Microsoft Learn learn.microsoft.com |
Articles about API plugins for Microsoft 365 Copilot (2)
Artigos que tratam de API plugins for Microsoft 365 Copilot:
- Plugins do Copilot, grounding no Microsoft Graph e conectores do Copilot Studio explicados
· Mirko Peters
O que são plugins, plugins de API, grounding por meio do Microsoft Graph, conectores do Copilot e conectores do Copilot Studio no Microsoft 365 Copilot, em que diferem e qual usar
Vale a pena ouvir istoGrounding Microsoft Copilot for Trusted Enterprise AI - Copilot Plugins, Graph Grounding and Copilot Studio Connectors Explained
· Mirko Peters
What plugins, API plugins, grounding through Microsoft Graph, Copilot connectors and Copilot Studio connectors each mean in Microsoft 365 Copilot, how they differ, and which one to
Perguntas frequentes
Questions marked with AI were written with AI from the facts on this page.
Qual é a diferença entre plug-ins de API e dados indexados no Microsoft 365 Copilot? (AI)
Com os plug-ins de API, o Copilot chama uma API externa em tempo real e os dados não são indexados no Microsoft 365. A API é hospedada fora do Microsoft 365 e é consultada ou alterada sob demanda.
O que um plug-in de API precisa para funcionar? (AI)
É necessária uma API REST com uma descrição OpenAPI e um manifesto de plug-in. O Copilot usa as descrições das operações e dos parâmetros para escolher qual operação chamar, e o plug-in deve fazer parte de um agente declarativo.
O Copilot pede confirmação antes de usar um plug-in de API? (AI)
O Copilot solicita consentimento no primeiro uso. Depois, as operações de leitura são executadas sem confirmação, enquanto as operações de gravação ainda pedem confirmação, e os desenvolvedores podem substituir esses padrões.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Especialistas e empresas para este tópico
Membros da comunidade especialistas em API plugins for Microsoft 365 Copilot:
- Mirko Peters · Microsoft MVP
Sources
- API plugins for Microsoft 365 Copilot – Microsoft Learn learn.microsoft.com
- Feed RSS: API plugins for Microsoft 365 Copilot
- Articles on this topic: 2
Maintained by Mirko Peters (Microsoft MVP) · Last updated: