Introduction After encountering issues with creating a To-Do task action in my previous attempt Building a Copilot Agent with Microsoft 365 Agents Toolkit and Microsoft Graph Plugin to list my ToDo Tasks, I explored various methods to generate an OpenAPI specification for M365 Copilot Declarative Agents using the Ms Graph OpenAPI spec. This post outlines the different approaches I tried, the challenges I faced, and the lessons learned. Methods for Generating OpenAPI Specs 1.

Introduction In a previous post, I detailed the steps for Building a Copilot Agent with Microsoft 365 Agents Toolkit and Microsoft Graph Plugin to list my ToDo Tasks. However, I encountered issues with the CreateTask function when using an OpenAPI spec generated with Kiota. Upon investigation, I identified the problem as being related to the handling of complex objects, particularly those involving dates. Even after simplifying the object structure, the CreateTask function continued to fail.

Introduction In this post, I’ll walk you through how to call Azure AI Search APIs from a M365 Copilot declarative agent without writing any code by using Microsoft 365 Agents Toolkit. Leveraging OpenAPI specifications, Microsoft 365 Agents Toolkit (previously known as Teams Toolkit) enables seamless integration with Azure AI Search, streamlining the development process for Copilot extensibility. Waldek Mastykarz wrote an insightful post on when Azure AI Search can be used, highlighting its ability to provide a more controlled approach to indexing and relevance without the complexity of building a custom engine agent.

Introduction In this post, I’ll walk you through how to call Azure OpenAI APIs from a Copilot declarative agent—without writing any code—by using Microsoft 365 Agents Toolkit. Leveraging OpenAPI specifications, Microsoft 365 Agents Toolkit enables seamless integration with Azure OpenAI, streamlining the development process for Copilot extensibility. Step 1: Create and Import an OpenAPI Specification Microsoft provides a pre-built OpenAPI specification for Azure OpenAI, but it’s often broader than needed. To simplify, I generated a targeted OpenAPI spec with Copilot by using the endpoint URL and a sample request body as a prompt.

Introduction This guide walks you through creating a Copilot agent using Microsoft 365 Agents Toolkit (previously known as Teams Toolkit) and Microsoft Graph API. By leveraging OpenAPI specifications, Kiota, and Microsoft 365 Agents Toolkit, you can build a plugin to interact with Microsoft Graph endpoints. I used the blog post Copilot Graph API QnA Plugin by Franck Cornu as inspiration with some variation to apply it to get my ToDo tasks.

Introduction When building a Copilot agent using Microsoft 365 Agents Toolkit (previously known as Teams Toolkit), you may encounter certain errors that can hinder your progress. This blog post highlights common issues and provides solutions to help you resolve them effectively. Common Issues and Fixes 1. name_for_human Exceeds 20 Characters Issue: You may encounter the following error when the name_for_human field in the ai-plugin.json file exceeds 20 characters: name_for_human in PluginManifestDocument has characters beyond the length 20 that MAY be ignored.

Introduction Balancing AI safety measures and practical functionality for SharePoint Agents is key for some use cases due to the lack of customisation of the inbuilt content safety against the four categories: harm, self-harm, sex, and hate. A particular use case we wanted to explore was its use for mental health support agents in the form of virtual mental health first aiders. My partner in crime Lee Ford and I explored what we could do without tripping the Responsible AI principles and flagging Content Safety categories.

Introduction SharePoint Agent is the easiest way to get started with building your own grounded Agents from your SharePoint data. The possibilities are vast, from HR agents to legal agents. If more configuration and features are required, the Copilot Studio or Azure AI Foundry could help. Each SharePoint site comes with its own default Agent scoped to data within the site. As of today (i.e. March 2025), the default SharePoint agent can’t be modified.