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

How can we improve Azure Search?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add support for field collapsing

    I've utilized field collapsing (aka result grouping) quite a bit utilizing Solr. Being able to group results together by a common element, then being able to page and sort based on that result list.

    175 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  2. Export/Import search indexes

    Allow users to export and import search indexes. Creating a search index via the portal takes quite a bit of time and if the service has to be moved you end up doing it all over again.

    169 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Possibility to delete documents that correspond to a filter

    It would be useful to be able to remove from an index documents that correspond a specified filter or a facet. Currently you need to retrieve all those documents from the index and only then can you delete them.

    160 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  4. Time to Live for data

    Also nice to have feature would be to purge data which is more than x days old by issuing explicit command or having TTL on documents.

    155 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  5. Backup/Snapshot of Index

    It should be possible for us to snapshot our indices at an interval of our choosing. The location for the snapshot should be Blob Storage.

    Why

    A data load goes wrong. Currently you are stuffed if this happens. You have no way to rollback.

    You want to take a production index + data and restore it into UAT/TEST/DEV. Currently there is no way to do this other than to load from source.

    151 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Enterprise  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow customer to provide encryption key for indexed data

    To meet enterprise security requirements, it would be great if index data could be encrypted (ideally with a key provided by the customer.)

    140 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow handling spelling errors in search "Did you mean ''?"

    It would be really nice to have spell check and auto correct as part of search.

    137 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    137 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Multi-tenancy  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support for disaster recovery/failover

    This would ensure high availability in case a DC goes offline/down so that customer doesn't need to write data to multiple geo-located accounts

    136 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

    131 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 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

  11. Azure Search Alerts

    Azure Search should have alerts similar to Azure SQL database. For example, I should be able to set up an alert to warn me if my index is almost full, et.c

    127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  12. Indexer for Azure File shares

    Index Azure File shares similar to blobs

    124 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support custom dictionary

    Some domestic senario like, Legal, really domestic topic require custome dictionary for more accurate wordbreaking, stemming and normalization. I think custome dictionary with easy maintemance like SharePoint or FAST provide today is help this type of senario.

    123 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow create, update, delete of Data Sources, Indexes, and Indexers with Service through ARM templates

    You currently can only create a service instance through an ARM template, you then need to make REST calls to create, update, or delete Data Sources, Indexes, and Indexers. This makes using Azure Search a challenge in solutions that are released in a Continuous Delivery model. If I want to use Release Management in VSTS to automate deployments, I need to write additional PowerShell scripts to call Azure Cmdlets to get the Primary Key for the service, then call REST APIs through PowerShell, and suck in JSON files to send as part of the request. It's a very complicated process…

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support Explain API

    The explain api computes a score explanation for a query and a specific document. This can give useful feedback whether a document matches or didn’t match a specific query.

    118 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  16. Storage Optimized tier in the Basic tier pricing range (L0)

    For a small business with low traffic and data just over the 2GB limit of the Basic tier it´s really hard to justify to upgrade to standard tier for 3.3x more cost. The performance and scaling for Basic tier is more the enough but the 2GB limit is just to low.
    It would be nice if you could introduce storage optimized layer(L0) for the lower end of the price range where performance and scaling is not important but the storage amount is more than 2GB.

    108 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  17. Pricing for more documents with less storage size / less documents with more storage

    It would be great to have a pricing model where we can index large amounts of small sized documents. (e.g.: 15M documents in 12 GB of storage).
    Same goes the other way around, less documents, with a greater storage size.

    102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →

    The current Azure Search business model charges for storage consumed and not by document count. 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.

    Thanks,
    Mike
    Azure Search Product Team

  18. Create the ability to get the Query Key in an ARM template

    At the moment it is not possible to list the Query Keys in the ARM template, to use the output as the input for let's say a Web App configuration.

    97 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add support to search Sharepoint Document Library directly

    Customer has a lot of documents in SharePoint document library that they want to be able to Search.

    93 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support 'skip' in facet queries

    Currently the results of facet queries can be limited adding the "count:n" parameter to select only the top n results.
    If one is interested in seeing all results of a facet query, there is no other way than setting the 'count' value sufficiently high to make sure that all result are included in the response.
    In the scenario of a large number of distinct values for the facet field those queries may, however, result in a large response with poor performance.
    In order to be able to provide paging through facet results for better performance, it's necessary to have a…

    85 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Search

Feedback and Knowledge Base