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

API plugins for Microsoft 365 Copilot

Prodotto

Modello di estensibilità in cui Copilot richiama un'API esterna in tempo reale durante l'esecuzione, in genere per eseguire azioni come la creazione di un ticket o l'aggiornamento di un record; i dati non vengono indicizzati in Microsoft 365.

◆ PRODOTTOAPI plugins forMicrosoft 365 CopilotM365.FM
Grafica del titolo: plugin API per Microsoft 365 Copilot (Prodotto)

Descrizione

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.

Panoramica compilata con l'AI dagli episodi di M365.FM e dai dati di questa pagina. Puoi migliorarla con il pulsante di modifica qui sotto.

TipoProdotto
DocumentazioneAPI plugins for Microsoft 365 Copilot – Microsoft Learn learn.microsoft.com

Articoli su API plugins for Microsoft 365 Copilot (2)

Articoli che trattano di API plugins for Microsoft 365 Copilot:

Domande frequenti

Le domande contrassegnate con AI sono state scritte con l'AI a partire dai fatti riportati in questa pagina.

Qual è la differenza tra i plugin API e i dati indicizzati in Microsoft 365 Copilot? (AI)

Con i plugin API, Copilot richiama un'API esterna in tempo reale durante l'esecuzione e i dati non vengono indicizzati in Microsoft 365. L'API è ospitata al di fuori di Microsoft 365 e viene interrogata o modificata su richiesta.

Di cosa ha bisogno un plugin API per funzionare? (AI)

Servono un'API REST con una descrizione OpenAPI e un manifesto del plugin. Copilot utilizza le descrizioni delle operazioni e dei parametri per scegliere quale operazione richiamare, e il plugin deve far parte di un agente dichiarativo.

Copilot chiede conferma prima di utilizzare un plugin API? (AI)

Copilot richiede il consenso al primo utilizzo. Successivamente, le operazioni di lettura vengono eseguite senza conferma, mentre le operazioni di scrittura continuano a chiedere l'autorizzazione, e gli sviluppatori possono modificare questi valori predefiniti.

Glossario

Community wiki

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

Esperti e aziende per questo argomento

Membri della community esperti di API plugins for Microsoft 365 Copilot:

Fonti

Mantenuto da Mirko Peters (Microsoft MVP) · Ultimo aggiornamento: