Introduction When working with Copilot Studio autonomous agents, you may encounter a situation where actions remain incomplete with the message “Waiting for user,” and there’s no clear way to proceed. I faced this issue while building an agent to create an incident in ServiceNow when an email is received, and then reply to the sender with the incident number. Although the scenario seems straightforward, the flow would stall and neither create the incident nor send the reply email.

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 blog post, I demonstrate how to create an OpenAPI specification for interacting with a SharePoint list using Microsoft Graph for integration with Microsoft 365 Copilot Declarative Agents. The list in question was created using the tracker template. This approach allows you to define and document API interactions, making it easier to integrate with tools like Microsoft 365 Agents Toolkit (previously known as Teams Toolkit) or Copilot for automation and extensibility.

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.

Embed GitHub Gist in Hugo posts I was approached by Divya Akula with a suggestion to use a link to GitHub for my script and I really bought in the idea because I used to do it on Wordpress. I started googling and trying out solutions which did not work and messed up my blog repo. Fortunately being MVP I have access to GitHub Copilot and asked Copilot with a simple prompt which gave me a simple straight forward looking solution.

Exploring some Limitations of Copilot in Power Automate I was thrilled when Copilot became available in the UK region within Power Automate around mid-November 2023. To understand its functionalities and limitations, I started exploring. Please refer to Understanding the Cloud Flows Designer, which outlines some limitations and described the Flows Designer experience. Creating New Flows While creating a new flow using the prompt “Start an approval process and update the item in a SharePoint list when a new item is created,” I noticed a functional flow generated.

MS Build AI Day Keynote by Scott Hanselman On October 19, 2023, the inaugural MS Build AI Day at Excel London in Custom House marked a pivotal moment for the world of AI. As an attendee, I had the privilege of witnessing a groundbreaking keynote session led by none other than Scott Hanselman. Titled “Navigating the AI Landscape,” the keynote, introduced by Michael Wignall, the lead for MS Build, set the stage for an eventful day filled with insights, connections, and hands-on experiences.