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?

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.