Declarative Agent Development Using Agent Toolkit | Part 2 - Generate Open API Spec

How does your Copilot agent actually know which API to call? The answer lies in the OpenAPI Specification - the brain behind every Declarative Agent. In this video, we break down OpenAPI Specification for Declarative Agents and show how it powers Microsoft Copilot API Plugins using Microsoft Graph. Reference Articles : What Is OpenAPI?: https://swagger.io/docs/specification/v3_0/about/ Set up DevProxy: https://learn.microsoft.com/en-us/microsoft-cloud/dev/dev-proxy/get-started/set-up?tabs=automated&pivots=client-operating-system-windows OpenAPI spec plugin for DevProxy: https://learn.microsoft.com/en-us/microsoft-cloud/dev/dev-proxy/how-to/generate-openapi-spec ✔️ What OpenAPI Specification really is (and what it is NOT) ✔️ Why Declarative Agents require an OpenAPI file ✔️ Understanding endpoints, parameters, request body & responses ✔️ OAuth 2.0 & Copilot API Plugin Authentication ✔️ Security schema & Sites.ReadWrite.All permission ✔️ YAML vs JSON OpenAPI Spec formats ✔️ How Microsoft Graph API OpenAPI Spec connects to SharePoint ✔️ Generate OpenAPI Spec using Dev Proxy CLI ✔️ Configure Dev Proxy to watch Graph API endpoints ✔️ Preparing your OpenAPI file for Agent Toolkit (M365) If you're building a Microsoft Copilot API Plugin, working on Declarative Agent Development, or exploring Copilot Extensibility with OpenAPI, this step-by-step breakdown will clarify how natural language gets translated into structured API calls. This is essential knowledge for: Microsoft Copilot developers Teams Toolkit Agent Development Agent Toolkit Extension (M365) SharePoint Graph API Integration Natural Language to API Copilot scenarios 👉 If this helps you understand Copilot architecture better: ✔️ Like this video ✔️ Subscribe for the full Declarative Agent series ✔️ Share it with your M365 developer network ✔️ Comment your questions below 💖 Sharing Is Caring