A few days ago, fellow MVP Reshmee Auckloo notified me that the PnP PowerShell command Get-PnPSearchCrawlLog  is about to be removed (see Deprecate Get-PnPSearchCrawlLog cmdlet #5229 ). For me—and for anyone who works seriously with Search in Microsoft 365—this is a significant step backwards . The output of this command has, until now, been the only reliable way  to get Microsoft Support to acknowledge and act on real search issues, instead of falling back on the default res

As I am not attending the MVP summit in Redmond this year I plan to attend a few more conferences in Europe. If you are attending any of these conferences and want to say hi, or ask a question, please do so, I don't bite :-) Right now these are confirmed: Bremen, Germany, Jan 23-24 Role: attendee Copenhagen, Denmark, Feb 24-25 Role: speaker, 2 sessions Köln, Germany, May 05-07 Role: speaker, 1 session Hamburg, Germany, June 27 Role: probably as speak,er, not confirmed yet

Most small and mid-sized organizations do not invest heavily in tailoring their M365 environment and often use the default settings provided by Microsoft. However, it doesn't have to require an expensive consultant to enhance the search experience in your tenant. Just follow these simple steps and the out of the box Search will by default only show current content. The approach is to segregate the content into two categories; current content and deprecated content . You will

In Modern Search we support a multi-language setup in two areas: The user interface for the configuration of the web parts, in this case in Dutch/Nederlands At the moment (late 2025) we have localization support for the following languages: Localization of managed Metadata We also support Managed Metadata localization, based on the translation values defined in the term store: If the RefinableString is mapped the the OWS_TAXID crawled property, like here: then the RefinableSt