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

    107 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

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

    105 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
    unplanned  ·  AdminThe Azure Team on UserVoice (Product Owner, Microsoft Azure) responded

    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

  3. Implement other highlighters

    Right now only Postings highlighter is implemented, which highlights single terms instead of full phrase query. Would be good to have other highlighters.
    As said here : https://stackoverflow.com/questions/42411353/azure-search-highlights-for-phrases-with-double-quotes

    102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →

  4. Offer Elastic Search as PaaS service

    Offer Elastic Search as PaaS service or managed cluster like Redis.
    Do not want Azure search but the native ES as service with its native interface and api.

    99 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

  5. 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…

    88 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →

  6. Add support for using Azure Data Lake with blob indexer or new indexer

    Customer would want to use ADL as a centralized store and then use various services like Azure Search, HDInsight on top of the same document store

    83 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    6 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →

  7. Rename existing index name.

    81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    6 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →

  8. Allow suggestions for custom analyzers

    Just what the title says.

    74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →

  9. Support for Geo.distance function on customer location compared to index data

    We have clients that we want to expose using the search feature. They do not want to appear if customer is outside there catchment area.
    The Geo.Distance function can only be compared to fixed data.
    I'd like to compare this with data held in the index.

    73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    6 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →

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

    73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →

  11. Add machine learned ranking models

    Similar to Solr's (small) capabilities
    https://cwiki.apache.org/confluence/display/solr/Learning+To+Rank

    71 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Scoring  ·  Flag idea as inappropriate…  ·  Admin →

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

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →

  13. Adding hard delete policy to all of Indexer

    Can we add hard delete policy to all of indexer as same as soft delete policy?
    Some senario in custmer immideiately want to refect source change result. We know we can do it by making push base approach, but it's much easier and simplyer to ensure single data update way.

    Cosmos:
    https://docs.microsoft.com/en-us/azure/search/search-howto-index-cosmosdb#indexing-deleted-documents

    Azure Table:
    https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-tables#incremental-indexing-and-deletion-detection

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →

  14. Azure Search should be able to index Cosmos DB Table API accounts / collections

    Similar to the suggestion for MongoDB support

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →

  15. Extend Tag Boosting by "searching" instead of "filtering"

    Azure Search with Tag Boosting will give a boost to documents that have "exact" tags in common with the input query.

    If a tag in index is "salt lake city" and one from query is "salt lake", the document doesn't get a boost. Even worse, since I believe Tag matching is using "filter" routine, it is case-sensitive.

    Yes, we can do multi-column search, but one column search with tag boosting is a way more fast and returns better relevance results focusing on the main column.

    So it would be great if Azure Search extends the current Tag Boosting to use…

    60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Scoring  ·  Flag idea as inappropriate…  ·  Admin →

  16. Extract text in a readable manner for pages using landscape orientation in PDF

    There is a known issue with PDFs that display certain pages with text oriented in a vertical manner. The issue is not that the text is not extracted, but rather that it is extracted in an unreadable manner since current extraction methods expect text to be horizontal. Unfortunately there is not currently a work around within Azure Search.

    We would need to inspect thousands of documents and rotate the vertical/landscape pages of the PDF manually before it can work as expected.

    59 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →

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

    56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →

  18. Provide the ability to hibernate/revive the index

    There are many scenarios where indexes are only needed for particular periods. A simple example is for demo purposes. I want to be able to have an index ready to use, but only use it periodically. It's too expensive to keep it running. It would be more 'cloudy' to have the ability to save/hibernate it to storage, and to be able to revive it from there. (I saw another suggestion to backup/snapshot. That's good but it also needs the ability to be deleted and still be recovered).

    53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →

  19. Support expressions in $orderby

    Let us have an Azure Search index with three columns:
    1. Id [Edm.String]
    2. Tags [Collection(Edm.String)]
    3. MaxScore [Edm.Int32]

    The index contains the following two entries:
    Id Tags MaxScore
    1 Paris,London,Rome 30
    2 Paris 10

    We have also a scoring profile and a scoring function of type Tag (Sum, Linear) which evaluate every tag by 10 points (boost = 10).

    We want to search the records with tags "Paris, London" in this index and sort it according to the percentage of compliance, while 100% is the value in column MaxScore.

    The problem is that by default Azure Search sorts records…

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

  20. Support operators like startsWith, contains, and endsWith in filters

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 3 5 … 14 15
  • Don't see your idea?

Azure Search

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice