How do we make it easier for documents to be found through Microsoft 365?


Recently a client asked us the question, “How do we make it easier for documents to be found on SharePoint and Microsoft 365?”.

This post is a repost from the iThink 365 site.

The question came about as we started them on the Microsoft 365 Intranet and SharePoint Online migration journey. Of course one of the issues, when you move content to web-based tools like SharePoint, is that people worry that they cannot find their documents anymore.

Finding documents on a network drive is much harder if you do not know what you are looking for. However, with the network drive, if people cannot find the content they will either ask someone, give up and re-create it. With tools like SharePoint and its search engine the users will most likely find the content but it may take more time than it should.

So then how can we help Microsoft 365 understand what our content is and improve the experience for the people we work with to find our content?

This article explains some ways that you can make your content more discoverable, it is focused on Microsoft Word documents but some of the tips will also work with the Microsoft Office suite.

Tip one: Give your documents good file names.

The number one way that Microsoft 365 search establishes a match to a search query is through the file name. So, make sure you give your file a good name that makes it discoverable.

Think about what terms others or you would use to when searching for the document. If you name it well it might save you or your colleagues from having to write the document again!

Tip Two: Populate the Title field of the Office Document

Every document, workbook, and slide deck in the Microsoft Office suite has a Title field. This is one of the key values that Microsoft 365 search engines use to indicate relevance.

Where to find the Title field property in Microsoft Word

To populate the title field property in Microsoft Word, click File -> Info and fill out the Title field with the name of your document.

Admittedly this is not the most discoverable location for this field and will likely get forgotten about.

However, keep reading to find a way to fix that!

Tip three: Make it easy for your users to fill out that important Title field.

Help your users make their documents more discoverable by embedding the Title field in your organisation’s template.

In Microsoft Word, you can embed that Title field that we discussed in tip two into the main part of the document. Now, a user can fill out the Title field whilst they are writing their document in their flow of work.

To do this do the following, in your Microsoft Word document add the Title field into the document by choosing.

From Microsoft Word, click Insert -> Quick Parts -> Document Property -> Title

Menu options to add the Title Field

This will insert the Title field into your Word document.

The Microsoft Word document can now be turned into a Word template and formatted with your company’s branding and shared across the organisation. Now when users create a Word document with the template then they will fill in the Title field as part of the process.


We hope you found some of these ideas and approaches for improving the discoverability of your Word Documents in SharePoint Online and Microsoft 365.

SharePoint Online Search Results and PnP Search Web Parts suddenly stops working


We have been working at iThink 365 with one of the NHS Trust in the UK to move their SharePoint 2010 environment to SharePoint Online.

One of the tools that we have made a lot of use of is the excellent PnP Search Webparts. If you have not checked these out then you must do so, more information here (

Here is an example of something that was built with them.

The strange thing we were seeing is that every once in a while the search results would stop working. No one seem to do anything or at least change anything but they would stop working.

The search results used custom search result sources (site settings -> manage result sources) and Microsoft SharePoint search rather than Microsoft Graph.


After a lot of trying out different queries in the search result sources page the issue was down to one main issue.

Here is the original result source query which looked like this:

The fixed version ended up being this, do you see the subtle difference?

Note: the double quotes around the path.

On a couple of occasions the ” were stripped out of the query when a user went into the search results and we think that an administrator was saving the result query rather than cancelling and this seemed to break the search web part.

Anyway hope that helps someone as it took us a few hours to work out what was going on!