The Challenge SharePoint Online’s automatic version deletion feature is designed to help organizations manage storage by automatically removing old file versions. When you enable automatic version trimming at the tenant level, SharePoint sets expiration dates on file versions before they’re permanently deleted. However, there are scenarios where you might want to preserve specific versions indefinitely—perhaps they contain critical information, represent important milestones, or are required for compliance purposes. This is

Introduction Refer to blog post Triggering a Power Automate HTTP Trigger from External Applications - testing with Postman for the initial Power Automate flow set up and testing with Postman. In this post, I’ll show you how to build a Microsoft 365 Copilot declarative agent that invokes a Power Automate flow with an HTTP trigger using Microsoft 365 Agents Toolkit. This approach enables you to extend Copilot’s capabilities by orchestrating complex workflows without writing custom code.

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’.