Copilot Studio’s new agentic workflow is evolving fast, and it now makes it easy to combine automated flow orchestration with M365 Copilot agent execution. If you have used Microsoft Foundry Workflow, the interface will feel familiar: a visual designer with triggers, actions, inline testing, flow notes, and governance hooks. What’s new in Copilot Studio agentic workflows Version control with built-in version comparison Action-level testing without running the full flow One action to initialize multiple variables Create and invoke agents directly from the workflow designer Flow-level sticky notes for context and documentation Built-in classification, human review, prompt orchestration, and M365 Copilot integration Flexible layout switching between horizontal and vertical A Tidy button to reorganize the designer automatically Easier disconnect/reconnect support for actions and connections Invoking an M365 Copilot Declarative Agent In this post I demonstrate how to invoke an M365 Copilot agent (a DeclarativeAgent) from a Copilot Studio workflow.

When automating SharePoint site configurations with PnP PowerShell, it’s essential to check whether a feature is already active before attempting to enable it. This prevents unnecessary errors, improves script performance, and ensures idempotent operations. This guide demonstrates best practices for checking feature status and conditionally enabling features in SharePoint Online. Table of Contents Why Check Feature Status First? Understanding SharePoint Features Prerequisites Basic Feature Check Pattern References Why Check Feature Status First?

Introduction Document Sets in SharePoint are a powerful way to manage groups of related documents as a single entity. They enable you to apply metadata, workflows, and permissions to a collection of documents, making them ideal for project folders, case files, or any scenario where you need to keep related content together. This post shows how to automate the configuration of Document Sets across multiple libraries using PnP PowerShell. Why Use Document Sets?

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.

PnP PowerShell: Enabling and Configuring Document ID in SharePoint The Document ID feature in SharePoint is a powerful tool that assigns a unique ID to files, making it easier to reference and track documents. The script within the post activates and configures the Document ID feature using PnP PowerShell. Additionally, it covers the Set-PnPSiteDocumentIdPrefix cmdlet, which simplifies the process of setting a custom prefix for Document IDs. Why Use Document IDs?

Using OpenAI in Excel and Google Sheets Integrating OpenAI’s GPT models into Excel or Google Sheets can unlock powerful automation and language processing capabilities. This blog post demonstrates how to use OpenAI’s API to translate text in a spreadsheet cell into French using a script. Google Spreadsheet Apps Script Example The following script uses OpenAI’s GPT-3.5-turbo model to translate the content of a selected cell into French and outputs the result in the adjacent cell.