Client secrets have traditionally been the go-to method for deploying Power Platform solutions from Azure DevOps, utilizing app registrations from the Azure platform. However, my personal experience has shown that this approach can be problematic, especially when you are not an application admin. It often involves wasting time figuring out why deployments have failed due to expired or missing client secrets. Even when reaching out to someone with application admin rights, they might generate a new client secret but forget to update the service connections for each service connection within Azure DevOps or the application admin does not have access requiring to reach out to someone else who have access, causing further disruptions.

Introduction Adding a SharePoint document library as a tab in Microsoft Teams is a common requirement for collaboration scenarios. While Teams provides an out-of-the-box (OOTB) experience for this, automating the process via PowerShell or Microsoft Graph can be tricky due to limitations. Thanks to Tiago Duarte through the discussion within the bug he raised , he found out a solution for it using Ms Graph PowerShell and I attempted to achieve same using PnP PowerShell.

Introduction In SharePoint on premises, administrators could log directly onto servers to inspect the crawl log and monitor search indexing. In SharePoint Online, this is no longer possible, making it tricky to track crawl activity and diagnose indexing issues. Fortunately, PnP PowerShell provides the Get-PnPSearchCrawlLog cmdlet, which allows you to inspect crawl activity programmatically. Certain activities can significantly increase the load on SharePoint’s crawl and indexing processes, such as: Migrating large volumes of content into the tenant Enabling OneDrive for Business Enabling or disabling Restricted Content Discoverability (RCD) to control content visibility for Copilot (see Microsoft docs) Forcing reindexing of libraries or sites, for example after changes to the search schema or to resolve search issues To avoid overloading your tenant and causing delays (such as intranet news not appearing promptly), it’s essential to plan these activities carefully—ideally performing them in phases or batches.