The thesaurus and synonyms do not work with the SharePoint People search. They work brilliantly with all the other content.

Unsure how a product with such touted feature sets can have a 5000 document library search limit. Isn't this backed by MS SQL Server & not MS Access? Inexcusable. Had to switch to different vendor product and ditch SharePoint.

As an administrator I want to be able to remove the "sync this library to your computer" option from the library tool bar on the sharepoint library site to prevent users from syncing a library locally.

The customer want sort the search results by drop box ,but there is not this function on SharePoint Online team site search results page.
Because the search results page(osssearchresults.aspx) can not be edited.
The customer is feeling inconvenience for that and hopes add this function to the seach results page(osssearchresults.aspx).

When I make a search for the files in "Search Online Documents" box on Office 365 portal screen, I am unable to check the search results uploaded within Office 365 group although I can view those uploaded in SharePoint Online team site. I hope that the users accessing to Office 365 will be able to check the search results uploaded within Office 365 group.

When you search in the modern UI, it will bring back the contents matching the search from Document Libraries but not the Document Library. It would be great if you could search and it would include documents and document libraries.

When creating custom Managed Properties we're restricted to only Text and Yes/No data types. Even the build in ones for custom use (Date00) have restrictions that make them useless. Full ability to customize is a must have and an unacceptable restriction.

Calculated columns returning 'Single line of text' show up in Search prefixed with "string#;"

For example, if the formula results in "In Progress" then the value returned by Search is

string#;In Progress

rather than just

In Progress.

Content Processor should drop the data type prefix and store only the actual value in the Index.

The first word after a bullet point in a multiline text field is not being indexed. If a space is added before the first word, the word is being indexed. Microsoft support suggested we inform our users to add this space. A better solution would be for the indexer to handle this scenario.

allow search to include mail, multiple mailboxes and respect permissions

Currently, searching within a document library does not sort results so that the most relevant is at the top of the results list. We would like to see the most relevant (i.e. most occurring in document and metadata, or at least most results found in metadata) at the top of the results list.

In SPO, Search Admin, deactivating a Query Rule does not update the Modified Date. Any type of configuration change should be indicated by a revised date.

Clicking on the Feedback links on tenant.sharepoint.com/layouts/15/searchadmin/TASearchAdministration.aspx takes us to a broken page. Please fix that

We'd like to exclude individual files from Search results at Tenant Administration level with a minimum impact and without having to modify the default result source on each and every site collection. Something similar to the existing “Remove Search Results” option at SharePoint Admin Center, but in a more permanent way (instead of only until next crawl, as currently possible). A custom or modified result source could also be a possible solution if could be fully configured and enforced at the tenant level (site collection admins shouldn’t be able to override it).

Now it is not possible, when using de webbrowser email, to add an Sharepoint attachment to the email.

Right now, {Today} token defined in Search result source used "Server time" when it is translated. This causes a problem when site timezone isn't the same as server timezone. (Mostly found on O365.)

For example, query "Created:{Today}" executed on Dec 30, 11AM on +7 timezone site is translated into "Created:2015-12-29" instead of "Created:2015-12-30" because the O365 server time is Dec 29. The only workaround to fix this is adding the same {Today} part again on the search web part query text property which will make the replacement correctly.

I've not found any documents suggesting this and found this workaround myself.

When installing the SharePoint 2016 the search configuration still is an issue. You need to use PowerShell for proper configuration or it just does not work.