Introduction Searching for files using the Document ID field in SharePoint can be challenging, especially when the ID contains hyphens (-). Hyphens are interpreted by SharePoint Search as a “NOT” operator, which can unintentionally exclude results and make it difficult to locate documents by their full ID. Why Is This Happening? The Document ID is a unique identifier for files, but by default, searching for an ID like M3DJHK53YMAX-2114042065-47 using the standard search box (with or without quotes) may not work as expected due to the hyphen’s special meaning in search queries.

Introduction PnP PowerShell authentication for Microsoft 365 has evolved significantly over the years. The multi-tenant app registration approach was decommissioned for security reasons, requiring each tenant to set up its own app registration. Fortunately, the PnP team has simplified this process with automated cmdlets that streamline app registration and authentication setup. This guide covers modern PnP PowerShell authentication methods, including interactive login setup, multi-tenant management, and certificate-based authentication. The Evolution of PnP PowerShell Authentication Before: Multi-Tenant App Registration Single shared app registration across all tenants Simplified initial setup but created security concerns Decommissioned for enhanced security Now: Tenant-Specific App Registrations Each tenant needs to create and maintain its own app registration(s) Enhanced security and control Automated setup through PnP cmdlets Method 1: Interactive Login Setup Step 1: Create App Registration Automatically The Register-PnPEntraIDAppForInteractiveLogin cmdlet automatically creates an app registration with default permissions:

Introduction There are multiple ways to create Microsoft Teams using PnP PowerShell, each offering different levels of control over naming conventions. This post explores 3 distinct methods and compares their capabilities for customizing Site Title, Site URL, and M365 Group names. When a Microsoft Team is created, a SharePoint site and M365 Group are automatically created in the backend. You may want to implement different naming conventions for each component: