I would like to be able to narrow my search to a specific document library or folder so that the search returns results only from the doc library or folder and any folders or subfolders below them.

We have several business needs which rely on easily searching and consuming information across our sites. While we appreciate the work so far that's gone into modern hub and site structures, we would like to be able to customize the default hub site search part. Particularly, we want to be able to add additional Refiners. We already have the required refiners in our site's defined search schema, why not allow us to add additional refiners to the search experience?

In SharePoint O365, the search engine 's Performance is not always satisfactory,especially in Chinese. Sometimes, the search result does not match the search criteria. This issue was analyzed by MS SPO Support team and the root cause should be the incompleted word-breaking.

User expected a better search engine in Chinese Search so that the expected result could be find out directly.

As an alternative, user also expected that the customising feature for word-breaking dictionary could be offerred in SPO.

Currently option to change the "mapping to crawled properties" settings is not editable for Refinable Managed Properties provided OOTB in O365.

It would be nice to have the property enabled so that we can include content from first crawled property that is not empty. This would solve the problem of having multiple values issues in Managed properties while consuming them .

give the possibility by default to search result for suffix matching.
For example to receive result for "SharePoint" i could write "Share"
or "Point" and automatically the search will consider the search key as "Share*" or "*Point".

User wants to search list items in the search box on the upper left of the [site page] for modern UI.

When a users search from a Document Library only the current level will be search. This should include documents from the subfolder too, or the ability to search down the tree.

I would like to be able to configure only Trusted Identity provider on a default zone and still be able to crawl it.

i know that right now im able to crawl non-deafult zone and then create server site mappings, but this causing a lot o disadvantages.
There is also possibility to crawl default zone and extend Web application to provide SAML logon, but then there are also problems like Deafult-zone url's in e-mails, problem with showing feeds on mysites etc...

Maybe a different solution would be to have search dedicated zone, that would act exactly as crawling default one?

We have a list with a "Multiple Choices" column called "Location".
Thus there are list entries with location values like "Berlin, Gray Court".
The item gets indexed in the following style: "Berlin;#Gray Court;#
Unfortunately the search does not return those results when querying for "Berlin".
Only the query "Berlin*" does return all desired results.
Would be nice to see the lingusitic features (word braking) working in such cases!

Modern Sharepoint search page to use default Search settings page result URL from site collection so that results can go to enterpise search - search center page /search

Integrate Yammer search results with SharePoint Online search results. Or allow federation of results.

The need to identify pages/files that contain specific hyperlinks is incredibly useful for maintaining content stored across multiple sources. For example, our business users would like to know how many internal sites/files might be linking to content that will moved, retired or changed. SharePoint 2010 provided this feature, but this cannot be configured in 2013.

Our company was able to configure this in SharePoint 2010 search by creating a Managed Property called "link" that was assigned to the "A.HREF" Crawled Properly. Users could then search using the syntax "link:http://ourintranet.com/documents/annualreport.pdf" Please give us this capability back!

Option to open document either by web browser or local application when searching.

Hello. Can you please add a redirect link to the modern team sites, as well as the classic team sites with modern page experience, that the users can also use the classic search center which is customizable to fit the users’ needs?
You have already added a redirect link to the classic search center within the document libraries when you search for something. But this link is not everywhere available in a modern team site.

A filtering flaw was recently discovered within SharePoint when using the ‘filter button’ on the right hand side while working within a specific view. If this filter is engaged and the ‘see all’ link is selected, the view ID disappears from the link. If this link is then sent to or shared with another user, they won’t be directed to the correct view.

Can you release an update to SharePoint Online to resolve this flaw?

We have B2B external users in SharePoint Online that would need to use our people search-based corporate directory. This has been working before but recently external users have been seeing only "nothing found" view.

When you soft-delete an Office Group, the connected team site is not removed from search index. When you click on the search result, an HTTP 403 is presented.
The workaround from MS Support is to manually delete the site from the index.

Also the site is still visible in "Recent Sites" and "Following" on SharePoint Home for every user. Workaround is that every user has to unfollow and wait until the site automatically removes from recent.

Both is not acceptable and looks like a bug for me.
Please remove soft-deleted sites from search index.

When a search result is returned for an image file (png, jpg, gif etc..) stored in a document library, it returns the dispform.aspx page for the item, and not the path to the file.

This is counterintuitive to end users, and should be resolved to better harmonize with the way modern views render images and documents stored on the same location.

We find out that sometimes the contents of files which has been attached to Custom List can be searched and sometimes cannot.
I want to know which one is correct in the specification of SharePoint Online, is the capable of searching correct or the incapable of searching correct.