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, ..)

Find relevant Office 365 Groups in the search. Now that the SharePoint homepage has been updated it is almost impossible to find some Groups to follow. (Also, the follow feature does not seem to be working.)

Current behaviour lists activity within libraries under the main tenant card. If all libraries are attached to tenant site and not sub-sites, then all activity within all libraries constrained to 3 lines of text.

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

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.

Que un cuadro de búsqueda permita filtrar elementos introducidos en un Calendario porque ayudaría a usar 500 calendarios en sus 500 sitios

Implement all hashing and cryptography functions to support and run on Federal Information Processing Standard (FIPS) 140-2 compliant configured servers (security hardening).

Currently FIPS has to be disabled - otherwise secure store service and search service applications will not properly run.

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.

All search refiners of type text should have a search box as an alternative display template.

There should be easy option to choose default search scope rather than requiring customization.

In SharePoint Online, dynamic content generated from JavaScript in a publishing web page is not crawled. In SP2010 it is possible using Browser Engine component. This really is an essential feature since lot of cx's have publishing sites with dynamic content in it.

There should be an option to do check-in/ out for multiple files and folder at a time. Because if we have to publish more then 2 files then we have to do this multiple times.

*English follows Japanese

検索時に自動作成されるクエリ候補の削除について

検索時に自動的に作成されたクエリの候補から特定の候補のみを削除できるようにしたい

About deleting query suggestions that are automatically generated when searching
I want to delete specific suggestions from query suggestions that are automatically generated when searching.