TL;DR: These scripts in the post use PnP.PowerShell to enumerate document libraries and compare file URLs against Search result to determine whether files are searchable. The plan was to show whether those files were indexable successfully, however the Get-PnPSearchCrawlLog is deprecated, see Deprecate Get-PnPSearchCrawlLog cmdlet for more details. This is because the underlying CSOM endpoint GetCrawledUrls has been deprecated. Use the first script when you want a quick list of files that are present in a library but do not appear in Search results.

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.