SharePoint
Feedback by UserVoice

SharePoint Search

Welcome! This is your place to suggest ideas or vote for ideas for improving the SharePoint Search experience.

How to submit a new idea

  1. Check if it's already been suggested. If it has, vote for it.
  2. If it's new, submit it in 50 words or less.
  3. Gather support!
  4. If your idea receives over 100 votes in 90 days, we will respond.
    If not, we will close it.

Want to engage further? Please visit the SharePoint Community

Note: we have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

  1. Content Type and Site Column Naming

    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

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Sort search results by most relevantat library level

    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.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Fix the Feedback link on the Search Administration page

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

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Fix the Manage Query Rules Page

    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.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Fix eDiscovery for MicroFeed data

    When doing eDiscovery the result for MicroFeed data suffers a few flaws:
    - when a query returns a post, the preview for a post is useless for the human reader (the Display-Form of the MicroFeed-list is not equipped for that use)
    - when someone puts a hold on a post, he can't preserver the rest of the thread (formulating the extended query needed not possible, as the data model for the MicroFeed-List is not documented)
    - when exporting, the export is returned as CSV like for any other list; but as data model of teh Microfeed list is not documented,…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Use static URLs to folders, regardless renaming the folder

    At the moment if you change the name of a folder any URL you have shared with a colleague breaks - as the URL is make up of explicit folder names. Instead we should use ids in the URL (like you already do for documents/files), which stay the same regardless of re-naming. This would also mean that if a user MOVES a folder we can still link to it.
    Rather than: .../Shared Documents/My First Folder/My Second Folder/My Third Folder
    We would expect to see something like: .../12345
    This ID would exist within a tree, and would therefore not need all…

    11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Suppress individual files from search results at SharePoint Online

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

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. In SharePoint Online, the search does not trim spaces at the end of search string for custom templates, resulting into "We dint find..".

    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.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Improve the accuracy of the word breaking process for Japanese users in SharePoint People Search

    Several of the Japanese users (ja) are being detected as Chinese (zh-tw) due to the user properties and they are being indexed incorrectly by the word breaker.
    Japanese characters are very unique and often uses Chinese characters.
    For example Japanese names often only uses Chinese characters.

    When user profile is created in SharePoint Online with user's properties containing a lot of Chinese characters, they are detected as Chinese instead of Japanese.
    As a result, their names and other properties are being tokenized in Chinese by the word breaker.

    So when the user is searched by the name as a whole…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Busqueda de elementos en Calendarios de sitio sharepoint

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

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Crawling each HNSC using separate content source

    Now only possibility is to set root web as content source if you want to crawl HNSC.
    It's very inconvenient if you have few big HNSCs and want to crawl them separately.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add the possibility in de Web mail to attach SharePoint documents

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

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support Federal Information Processing Standard (FIPS) 140-2 compliant OS configuration

    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.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Fixing how {Today} token is replaced

    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.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Crawl Document Properties for DLP

    The following image contains a use case that I have provided MS support for a design change request.

    https://onedrive.live.com/redir?resid=3FD50FD56BA55AA1!214204&authkey=!AOi2bIALcOJNcbk&v=3&ithint=photo%2cjpg

    The ultimate issue here is that SharePoint Online search does NOT crawl document level properties. Therefore, DLP cannot use these properties to help protect that document from leaking since DLP is reliant on the search index.

    The workaround I have been given is to create a column in the document library where the file is stored; this allows the custom document property to populate the list column in the library upon upload. The challenge with this approach is that this column…

    11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add IndexedProperties on ListItem level

    Currently you can only add indexed properties on Site, Web, List or Folder level - I suggest you to add the same on ListItem level.

    Reason:
    If you want to enrich items with additional metadata you have to use list columns or content enrichment (not available with SPO or with hybrid cloud search service).

    Another option would be to add "normal" columns to the items (and maybe hide them from editview) and rely on the normal indexing - for a large scenario this is simply not possible.

    Indexing of the propertybag would greatly simplify this.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Auto Classification of Documents During Indexing

    Currently we have a large amount of file share and SharePoint data that contains Personally Identifiable Information and Sensitive Data. It would be ideal to be able to auto tag documents at the index level to filter out those documents in Search results. Additionally, it would also allow for tagging documents in a positive way, for more refined searching.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add a search driven column type

    It would be great to have a column type for lists or libraries that stores a search-query.
    In column settings you would create a query with a reference to the list-item (something like "author:{Item.Author} AND ContentType:Tasks").
    This way you could dynamically link content to a list item.

    7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Provide API to allow crawling of SharePoint online using a standalone (3PP) search engine. Today we do this for SP 2013.

    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.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Search refiners of text should have a search box

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

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

SharePoint Search

Categories

Feedback and Knowledge Base