Problem Statement Mass applying sensitivity labels programmatically using Microsoft Information Protection SDK (MIP SDK) or PowerShell, the sensitivity label column appears blank in the document library UI, even though the metadata value is correctly set in the backend. This is a display refresh issue where the applied sensitivity labels has not synced to the SharePoint metadata. Root Cause When sensitivity labels are applied programmatically (via PowerShell, Graph API, or migration tools), the metadata is present in the file but not displayed in the interface.

Problem Statement When using the KQL query ContentClass:STS_List_DocumentLibrary without additional filters, some document libraries (like “Shared Documents”) are not appearing in search results, even though they exist and contain content. Initial Troubleshooting Steps Taken 1. Hidden Site-Level Visibility Setting Action: Visited https://<your-site>/_layouts/srchvis.aspx and enabled “Always index all Web Parts on this site” Status: ✅ Enabled - Monitoring for 24-48 hours to see if this resolves the issue Result: No effect on bringing the shared documents search result

Overview When moving files in SharePoint, understanding how permissions are handled is crucial for maintaining proper access control. The behavior varies significantly based on several factors, including whether you’re moving a single file or multiple files, and whether you’re moving within the same site or across different sites from the User Interface. This post is based on experiments done in October 2025 and things may change in the future. The “Keep Sharing with Same People” Option Important: The option to unselect the move of permissions appears only when a single file is selected to be moved to a different SharePoint site.