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.

I was experimenting with Cowork in my tenant just last week, so I was surprised when it suddenly stopped working. After digging a bit deeper, it turns out Microsoft has taken a clear stance: Anthropic AI models are currently restricted by default due to GDPR considerations, particularly around data processing outside the EU. Why Are Anthropic Models Disabled? For EU-based tenants, Microsoft has disabled Anthropic AI models by default to ensure compliance with GDPR and data sovereignty requirements.

Introduction Searching for files using the Document ID field in SharePoint can be challenging, especially when the ID contains hyphens (-). Hyphens are interpreted by SharePoint Search as a “NOT” operator, which can unintentionally exclude results and make it difficult to locate documents by their full ID. Why Is This Happening? The Document ID is a unique identifier for files, but by default, searching for an ID like M3DJHK53YMAX-2114042065-47 using the standard search box (with or without quotes) may not work as expected due to the hyphen’s special meaning in search queries.

Introduction PnP PowerShell authentication for Microsoft 365 has evolved significantly over the years. The multi-tenant app registration approach was decommissioned for security reasons, requiring each tenant to set up its own app registration. Fortunately, the PnP team has simplified this process with automated cmdlets that streamline app registration and authentication setup. This guide covers modern PnP PowerShell authentication methods, including interactive login setup, multi-tenant management, and certificate-based authentication. The Evolution of PnP PowerShell Authentication Before: Multi-Tenant App Registration Single shared app registration across all tenants Simplified initial setup but created security concerns Decommissioned for enhanced security Now: Tenant-Specific App Registrations Each tenant needs to create and maintain its own app registration(s) Enhanced security and control Automated setup through PnP cmdlets Method 1: Interactive Login Setup Step 1: Create App Registration Automatically The Register-PnPEntraIDAppForInteractiveLogin cmdlet automatically creates an app registration with default permissions:

Introduction SharePoint site designs are powerful tools for automating site configuration, but they’re typically applied during site creation. What if you need to apply Microsoft’s out-of-the-box site designs to existing sites using automation? The PnP PowerShell, CLI for M365 and other PowerShell module cover applying custom site designs only. We can leverage a PowerShell hack using REST API calls to achieve this functionality. Thanks to Arash Aghajani who pinpointed on feasibility and requested for it to be natively available within PnP PowerShell.

Introduction One of the most frustrating experiences for SharePoint users is when a document link that worked perfectly yesterday suddenly returns a 404 error today. This scenario is all too common, especially after migrations or when documents are renamed or moved. Understanding how SharePoint links work and their limitations is crucial for effective document management. The Problem: Broken Links After File Changes This raises an important question: Why do SharePoint links break when files are renamed or moved?