https://richardstk.com/2014/08/06/enable-searching-for-sharepoint-2013-asset-library-items-using-keywords/

Local SharePoint can make keywords fields searchable, why can't 365 SharePoint?

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.

need to be able to use the search function within windows explorer with mapped drives. This would improve the functionality and would ease the transition of on premise file servers to office 365 and SharePoint online

I wanted to display people item when SipAddress contains some value. If I use "Contains" keyword, it is behaving as "Equals" keyword. This is occurring for SipAddress property.
Please check.

When PDF files appear in search results, the link to the file in the Display Template includes the #search=myTerm parameter, while the OPEN link in the Hovercard does not. Therefore when the file opens in a PDF viewer, one will display inline search results while the other does not. This results in an inconsistent user experience being reported as an issue by users.

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.

Especially when having content of a certain type spread over multiple webs and sites, search provides a good way to aggregate this information, e.g. get all risks tracked in all project sites. It would be great if these results could be exposed as Odata stream to be directly integrated in the reporting tool of your choice.

I would like either ability to have automatic contextual scoping till library/list level in sharepoint main search or search within list/library should sort results based on search relevance not sorted based on name. By sorting search results based on name within library search it doesnt make sense because relevant document is displayed at the very bottom if its name dies start from initial alphabet letters (a,b,c, ..)

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

Naming of Content Types and Site Columns should not be Unique.
As both content types and site columns are identified uniquely by CT Id and internal field name, it should be possible to give a display name for content type or site column, even if the display name is already in use.
This way we can avoid al sorts of strangely named content types or fields, because of the current limitation, and still be able to use the different columns in the search schema

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

If I am creating a list from custom template and the name of template is "Project", but while searching for template I type "Project ", it says "Not Found". I think that, those extra spaces in search string for custom templates, at the end, should be trimmed, resulting into robust search.

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.

Provide API to allow crawling of SharePoint online using a standalone (3PP) search engine. Today we do this for SP 2013.

We have been told in SP online that we must use a web crawler.

That option would be complex for some of our websites and would limit the meta-data and security information available to us and make the search experience so much worse.