Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Azure Search

Azure Search is a search-as-a-service solution that allows developers to incorporate a sophisticated search experience into web and mobile applications without having to worry about the complexities of full-text search and without having to deploy, maintain or manage any infrastructure

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Table Storage Indexing of multiple tables at scale

    I believe that a good pattern for Azure Table Storage is to enable fast deletes by simply dropping tables. I've implemented a multi-tenant model for my data using a table per tenant, and would like to aggregate search data across tables.

    The current recommendation is to create an indexer per table. This means the number of tenants I support (which I'm hoping to be in the thousands) is limited to the number of indexers I can create, which is a very low number.

    The latest table storage SDK has methods to asynchronously list tables in a segmented fashion using continuation…

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  2. Provide warmup procedure

    When we scale out Search replica, we can find delay peak right after it scaled. It gives throttled query, so I want to reduce it when we apply scheduled replica change.

    It would be good to provide "predefined warm-up query sets" After-Scaleout event. What about to give textbox, and GET-queries are performed line by line multiple times.

    Note that I'm using Azure Automation with this script to change replica count by schedule; https://gallery.technet.microsoft.com/scriptcenter/azure-search-change-c0b49c4c

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Multi-tenancy  ·  Flag idea as inappropriate…  ·  Admin →
  3. SAT support for query tokens

    As with Blog/containers it's possible to have a SAT token and time limit it. This would be a great benefit for azure search too, to allow query keys with the same concept.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Proximity Search with exact order support

    The lucene query syntax for proximity search allows us to find 2 terms X number of words apart.

    https://docs.microsoft.com/en-us/rest/api/searchservice/lucene-query-syntax-in-azure-search#bkmk_proximity

    A search for "hotel airport"~5 could return documents with "Find a hotel airport" or "hotel near airport" or "going to airport? check out this hotel".

    It would be a big benefit to our clients if we could have a mode for proximity search where it doesn't matter what the order of the words are, as well as a different, more restrictive mode, where proximity search will only find results with the words in in explicit order.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  5. Configurable matching strategy for more natural searches.

    You can see full details here:
    http://stackoverflow.com/questions/43505244/how-to-make-searches-more-natural/43509264#43509264

    The idea is to have something like:
    EnableFuzzy, Enable PartialMatching on the SearchParameters to avoid constructing weird search strings.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide ability of collection Type field to be searched against individual values separately

    For a document, where there are multiple values in its collection type column, it gives it lesser score (and hence either to come lower or may not even come in the result) to it even though the search query has matched with ONE of the values in the list COMPLETELY.

    This is because, currently Azure Search considers list of all the values provided in the collection type as a single string by concatenating all of them.
    My requirement is that if the search query (for that field) matches with any of the values in the collection, it should consider it…

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  7. Provide option to facet on all facetable fields in a Search request

    Some applications can have a large number of facets and it is inconvenient to have to specify them all explicitly in the Search API, as reported here: http://stackoverflow.com/questions/28542665/azure-search-what-if-i-have-a-lot-of-facets

    If there were an option like facet=* that returned facets on all facetable fields, that would be easier for such cases.

    76 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  8. allow indexers to call DocumentDB stored procedures

    We have difficulty in transferring documents where we require multiple maps of our data into the flat search index. There is a limit of two user defined functions (which we use to do this) and there doesn't appear to be a way to call a stored procedure through the query language. Having the search indexers support DocumentDB stored procedures gives us far more power and flexibility to map the data correctly. At the moment we have had to revert back to writing our own code to do this.

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support indexing JSON-LD embedded in HTML documents

    Support indexing structured data (e.g. schema.org) in HTML documents.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add a description field to index for better manageability between indexes with similar names.

    We create a lot of indexes for experiments. Over time it becomes harder to remember the differences between indexes with similar names. We could add something to the index name to distinguish them. But it makes the name messy. It'd be better to have a description field in index to describe what the index is.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  11. Create tools for developing search in Visual Studio

    I would like to have a set of tools for developing an Azure Search instance in Visual Studio, analogous to what SSDT is for SQL Server.

    In an ideal world, these tools would allow me to define indexes, indexers, datasources, and all other components necessary for my search index. The tools would also include ability to publish my changes to the instance, either through Visual Studio itself or from a CI build in Release Management.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support scoring profiles on suggesters

    I think it would be valuable to expand the capabilities of suggesters. Right now, they're somewhat limited. I think it would be nice if they provided the flexibility of scoring profiles. The reason why is because sometimes, it might be nice to show the most recently added or viewed documents (i.e. Edm.DateTimeOffset) as suggestions. Other times, you may want to show the most popular, or most viewed, documents (i.e Edm.Int32). These are just two scenarios that I would like to cover with suggestions, but, I'm a bit limited.

    41 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support geo.distance in select result

    Azure Search does not support returning the distance data from geo.distance in search results. geo.distance can be used in only filter and orderby.

    I would like to get distance data from geo.distance.

    173 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.

    There are a few ways you can do this currently in code per document, for example (https://stackoverflow.com/questions/6544286/calculate-distance-of-two-geo-points-in-km-c-sharp). But we are considering how we might make it available as a document property.

    Thanks,
    Vinod
    Azure Search Product Team

  14. Cursor-based pagination

    When new elements are added to the beginning of an index paginating with $top/$skip will return duplicated elements. The cursor-based pagination solves such problems.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add tagging to each token such as POS, allowing to filter on them and receive them in results

    In Lucene you can add metadata to each token, which is then returned on search results.

    It would be great to be able to add predefined tags/metadata during indexing that will be later returned on search results. Filtering results based on these tags would also be great.

    Examples of tags can be:
    Part of Speech
    Dates
    Numbers
    Entities (person names, organizations)
    Locations (city, country names)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  16. Run multiple Indexers at once

    We have many indexes with matching indexers that scan SQL Server tables to import/update data.

    I found that during the initial import of a new large index (millions of records, taking several hours), none of the other indexers on the same service are run at all. This means that just by adding a new index, all other indexes will become stale until the large index is finished!

    Please add the ability for multiple indexers to run simultaneously.

    72 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  17. clone index

    I'd like to implement 'versioning' indexes for each DocDB repository.
    In example, DocDB collections are crawler-2016 and crawler-2015, each of which will be indexed to index-2016 and index-2015 in Azure Search.

    In this operation, 'Clone Index' button could be helpful greatly as I have to create each index one by one. Actually I screen-captured previous index fields and tick-tick index checkboxes which created from DocDB import datasource.

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  18. Provide sum and average on facet

    It would be nice to have agregation on certain facetable Field.
    We would define another numeric field to be computed.

    On the FacetResult, we could get sum and average exactly in the same way as count.

    61 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  19. Index specific admin keys

    As of today Azure Search providee index specific query keys, but only global admin keys. In a multitenant scenario all tenants then have to share the admin key in order to index data. In order to provide sufficient tenant isolation in multi-tenant scenarios we need index specific admin keys. Especially for those cases where each tenant run in process isolation - hence the individual tenants can't access other tenants connection strings.

    146 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Multi-tenancy  ·  Flag idea as inappropriate…  ·  Admin →
  20. term boosting in synonym map

    Synonym maps now exist as a preview feature, but the values mapped are considered truly synonymous. It would be great if we could basically use the synonym map feature and input a map that contains static term boosting.

    For example:
    castle => fortress^2, fort^1.5, stronghold^1.75, fortification^2, keep^2.7, citadel^1.8

    rather than
    castle => fortress, fort, stronghold, fortification, keep, citadel

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base