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

One of the cornerstones of good information architecture is content types, and therefore we often use the content type as a criterion in our search queries. But why not use the content types as a refiner too? The default mapping provided by Microsoft is not optimal: So if we look at the value in "ContentType" for a site page it looks like this: So, I recommend updating the mapping by: creating a new Managed Property "ContentTypeName and mapping it to ows_ContentType. Mappin

Case: you have a Content Type for your Policies Pages and want to ensure that they are reviewed every 180 days. You have at least 3 options: 1) add a "Next review date" DateTime site column to the Content Type and be depended on the users remembering to update the column. You could also set up a workflow that will set the value in the "Next review date" on updates, but that is a lot of work when there are better alternatives. 2) Add a calculated site column that will set a va