M365Con 2027 – conferencia online gratuita · 11–22 Jan 2027 · 120 sessions m365con.net

API plugins for Microsoft 365 Copilot

Producto

Modelo de extensibilidad en el que Copilot llama a una API externa en tiempo de ejecución, normalmente para realizar acciones como crear un ticket o actualizar un registro; los datos no se indexan en Microsoft 365.

◆ PRODUCTOAPI plugins forMicrosoft 365 CopilotM365.FM
Gráfico del título: Complementos de API para Microsoft 365 Copilot (Producto)

Descripción

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.

Resumen generado con IA a partir de los episodios de M365.FM y los datos de esta página. Puedes mejorarlo con el botón de edición de abajo.

TipoProducto
DocumentaciónAPI plugins for Microsoft 365 Copilot – Microsoft Learn learn.microsoft.com

Artículos sobre API plugins for Microsoft 365 Copilot (2)

Artículos que tratan sobre API plugins for Microsoft 365 Copilot:

Preguntas frecuentes

Las preguntas marcadas con IA se escribieron con IA a partir de los datos de esta página.

¿Cuál es la diferencia entre los complementos de API y los datos indexados en Microsoft 365 Copilot? (IA)

Con los complementos de API, Copilot llama a una API externa en tiempo de ejecución y los datos no se indexan en Microsoft 365. La API está alojada fuera de Microsoft 365 y se consulta o modifica bajo demanda.

¿Qué necesita un complemento de API para funcionar? (IA)

Necesita una API REST con una descripción de OpenAPI y un manifiesto de complemento. Copilot usa las descripciones de las operaciones y los parámetros para elegir qué operación llamar, y el complemento debe formar parte de un agente declarativo.

¿Pide Copilot confirmación antes de usar un complemento de API? (IA)

Copilot solicita consentimiento en el primer uso. Después, las operaciones de lectura se ejecutan sin confirmación mientras que las de escritura siguen pidiéndola, y los desarrolladores pueden modificar estos valores predeterminados.

Glosario

Community wiki

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

Expertos y empresas para este tema

Miembros de la comunidad expertos en API plugins for Microsoft 365 Copilot:

Fuentes

Mantenido por Mirko Peters (Microsoft MVP) · Última actualización: