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.

Introduction When building agents in Microsoft Copilot Studio, you’re faced with a fundamental choice: Classic Orchestration or Generative AI Orchestration. Understanding the differences between these approaches is crucial for making the right architectural decision for your chatbot project. Enabling Generative AI unlocks dynamic capabilities where responses are intelligently crafted using available tools and knowledge sources as needed. In contrast, Classic Orchestration restricts responses to only the predefined content and behaviors explicitly configured in your agent’s topics.

Introduction During a recent community discussion, Suhail Sayed presented an interesting challenge that many organizations face during SharePoint tenant migrations. The problem? Converting sharing links to their canonical URLs when documents are migrated between tenants. The Challenge When migrating SharePoint documents from one tenant to another, organizations often encounter a specific issue with document references: The Problem Scenario: Source tenant: Documents contain reference links to other documents Migration requirement: Update these links to reflect the new tenant Complication: Links were created using the Share option, not the Copy Link option Why This Matters: When you generate a link using SharePoint’s Share function, it creates a unique link with a randomly generated ID that redirects to the correct canonical URL.