Updating SharePoint file metadata with Set-PnPListItem requires the correct UpdateType. Use SystemUpdate for author and retention label changes, and UpdateOverwriteVersion when updating the editor. When to use SystemUpdate SystemUpdate updates list item metadata without creating a new version or changing the modified date. It is ideal for author changes or retention label updates. When to use UpdateOverwriteVersion UpdateOverwriteVersion updates metadata and creates a new version. It is required for editor changes because SystemUpdate does not update the editor field reliably.

I tested SharePoint auto-trimming behavior against files with and without retention labels. The results show that files without a retention label are trimmed as expected, while files with a retention label behave more like retention policy items and keep versions longer. For non-retention-label files, SharePoint trims old versions once the version count grows. Auto-trimming bypasses the recycle bin and removes older minor/major versions. However, files with retention labels appear to retain versions instead of trimming them.

I tested SharePoint auto-trimming behavior against files with and without retention labels. The results show that files without a retention label are trimmed as expected, while files with a retention label behave more like retention policy items and keep versions longer. For non-retention-label files, SharePoint trims old versions once the version count grows. Auto-trimming bypasses the recycle bin and removes older minor/major versions. However, files with retention labels appear to retain versions instead of trimming them.

Updating SharePoint file metadata with Set-PnPListItem requires the correct UpdateType. Use SystemUpdate for author and retention label changes, and UpdateOverwriteVersion when updating the editor. When to use SystemUpdate SystemUpdate updates list item metadata without creating a new version or changing the modified date. It is ideal for author changes or retention label updates. When to use UpdateOverwriteVersion UpdateOverwriteVersion updates metadata and creates a new version. It is required for editor changes because SystemUpdate does not update the editor field reliably.

Summary SharePoint MCP (Model Context Protocol) tools may be missing in Copilot Studio due to Copilot Frontier access settings. Enable SharePoint MCP tools by configuring access in Microsoft 365 Admin Centre under Copilot Control System. Grant “All Users” access to Web Apps in Copilot Frontier settings. Tools typically appear in Copilot Studio within minutes after enabling. Table of Contents The Problem What Are SharePoint MCP Tools Solution: Enable Copilot Frontier Access Step-by-Step Configuration Verification References The Problem When building agents or custom copilots in Copilot Studio, you may find that SharePoint MCP tools are missing from the available connectors or tools list.

Overview Use Power Automate to update a SharePoint library or list title and description by calling the SharePoint REST API. This is useful when you want to automate metadata updates or rename a library from a flow. Prerequisites A Power Automate cloud flow with access to the target SharePoint site A SharePoint library or list title to update The Send an HTTP request to SharePoint action Configure the SharePoint REST action In the Send an HTTP request to SharePoint action:

Triggering a Power Automate HTTP Trigger from External Applications For production environments, manually triggering a Power Automate flow via an HTTP trigger from external applications (.NET, React, or Agents Toolkit) requires Entra ID authentication if only users within the tenant can trigger it. If set to ‘anyone’ the Url of the workflow contains a sig parameter which is required to call the flow. This guide walks through the setup and testing process for only ‘any user in my tenant’.

Overview Use Power Automate to update a SharePoint library or list title and description by calling the SharePoint REST API. This is useful when you want to automate metadata updates or rename a library from a flow. Prerequisites A Power Automate cloud flow with access to the target SharePoint site A SharePoint library or list title to update The Send an HTTP request to SharePoint action Configure the SharePoint REST action In the Send an HTTP request to SharePoint action:

Triggering a Power Automate HTTP Trigger from External Applications For production environments, manually triggering a Power Automate flow via an HTTP trigger from external applications (.NET, React, or Agents Toolkit) requires Entra ID authentication if only users within the tenant can trigger it. If set to ‘anyone’ the Url of the workflow contains a sig parameter which is required to call the flow. This guide walks through the setup and testing process for only ‘any user in my tenant’.

Summary SharePoint MCP (Model Context Protocol) tools may be missing in Copilot Studio due to Copilot Frontier access settings. Enable SharePoint MCP tools by configuring access in Microsoft 365 Admin Centre under Copilot Control System. Grant “All Users” access to Web Apps in Copilot Frontier settings. Tools typically appear in Copilot Studio within minutes after enabling. Table of Contents The Problem What Are SharePoint MCP Tools Solution: Enable Copilot Frontier Access Step-by-Step Configuration Verification References The Problem When building agents or custom copilots in Copilot Studio, you may find that SharePoint MCP tools are missing from the available connectors or tools list.

Summary Build autonomous agents that respond to email queries and generate dynamic Adaptive Cards. Use prompt tools to break down complex instructions into manageable, reusable components. Send personalized, interactive content directly via Outlook email. Learn formatting requirements and best practices for Adaptive Cards in email. Table of Contents Introduction Why Dynamic Adaptive Cards via Email Using Prompt Tools to Manage Instructions Building the Holiday Planning Agent Processing Email Queries Adaptive Card Formatting for Email Demo: Holiday Query in Action Key Takeaways References Introduction Copilot Studio enables makers to create intelligent agents that go beyond the chat interface.

Summary Autonomous agents run in the background without user prompts, so they cannot ask users to sign in during execution. Use maker-provided credentials for tools; user credentials are not appropriate for autonomous scenarios. Apply least privilege and restrict tool actions to reduce data exposure and abuse. Communicate the “runs under author’s identity” warning and govern access like any service account. Table of Contents Why Authentication Matters Autonomous Agents: What Changes Authentication Models Configure Tool Authentication Restrict Tool Actions Publishing, Warnings, and Governance Best Practices Checklist Why Authentication Matters As organizations adopt autonomous agents to perform tasks and make decisions, authentication becomes a core control.

Converting to Modern YAML Pipeline: Application Lifecycle Management in Azure DevOps for Power Platform There are loads of posts explaining Application Lifecycle Management for the Power Platform using Azure DevOps most using the graphical classical pipeline. The latest post I read on this is Application Lifecycle Management for the Power Platform using Azure DevOps by Luise Freese which is brilliant. Please read article covering difference between YAML and Classic UI to explain why you may want the modern YAML pipeline.

Add or Update Image Column in SharePoint with Power Automate: Download and Use Images from the Web The blog post titled Update image in SharePoint/Microsoft Lists Image columns using Power Automate by Ganesh Sanap rovides a guide on how to update an image column in SharePoint or Microsoft Lists using Power Automate. The native “Create Item” and “Update Item” actions in Power Automate do not directly support adding or updating image columns.