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. Language analyzer - ability to disable word decompounding

    Azure Search has word decompounding (in languages like German, Danish, Dutch, Swedish, Norwegian, Estonian, Finish, Hungarian, Slovak)
    https://docs.microsoft.com/en-us/rest/api/searchservice/language-support

    However often it doesn't lead to desired output as we need to find only compound words.
    Especially interested to have it in "et.microsoft" analyzer.

    42 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 →
  2. Provide a PHP SDK for Azure Search

    Provide a PHP SDK for Azure Search that covers the same functionality as the .NET SDK.

    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  ·  Client SDK  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support picking existing index when creating an indexer in Azure Portal

    Today is only possible to create an indexer if you follow the entire process through import data workflow:

    -Select the data Source
    -Add Cognitive skills (optional)
    -Create an Index
    -Create an Indexer

    However, there are times we want to set a different schedule for an indexer or create a new one, without recreating the index.

    41 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 →
  4. 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 →
  5. Add support for inheritance ($type)

    Sometimes we have inheritance in our database tables. In my case, I have inheritance mapped to a table using EF Code First, and the table contains a generated column, [Discriminator], that tells the EF which type should be activated when fetching the entity.

    There should be a way for Azure Search (a field transformation function maybe) to map discriminators in the database to fully qualified non-searchable $type fields in the indexes, in order for the SDK to be able to deserialize the types correctly using the TypeNameHandling setting of the Json.net serializer.

    40 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  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 →
  7. 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 →
  8. Elastic Azure Search

    Provide an elasticity option as with Azure SQL Databases, for search it's a MUST HAVE feature!!!

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow access to stored term frequencies for searchable fields

    Term frequencies are maintained for searchable fields in order to compute things like TF/IDF quickly. It should be possible to access those term frequencies for additional analysis.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Given the current API surface area of Azure Search, how would you actually use these term frequencies? Said another way, what other capabilities would you require in the API in order for term frequencies to actually be useful?

    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 Carter
    Azure Search Product Team

  10. 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 →
  11. Ignore thumbnails when indexing word documents

    Word supports saving documents with a thumbnail which contains the text content from the first page. When Azure Search indexes documents, it also indexes their embedded documents. Generally speaking this is useful behaviour, but in this case it leads to content duplication of the first page.

    We cannot control documents provided by users so Azure Search should handle this and ignore thumbnails when indexing Word Documents.

    26 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 →
  12. 26 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  ·  Scoring  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 →
  14. Implement Data Lake Gen2 Search Indexer

    It seems like MSFT is pushing Data Lake as a more robust implementation of Azure Blob.

    Implementing a Data Lake Gen2 Search Indexer would give my team confidence that Azure Search will align with our move to Data Lake.

    23 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  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 →
  16. Highlight search text on blob documents

    search API should return document that should highlight search text inside the document. So that when i download view the document it should highlight search terms/text in documents like pdf, excel,word and etc.

    same like JFK it will do only for image but good to have document highlighting

    18 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 →
  17. Support prefix matching for suggestions

    The suggester in Azure Search has only 1 SearchMode and that is it will match on any word within the field. Although this might be appropriate for many applications, it also is not for many others. It would be useful if we can configure the suggester so that a match occurs only when the beginning of the field is a match.

    15 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 →

    Thank you for your feedback. This sounds a lot like the Autocomplete API, which provides the words in the index that starts with the provided term. This may be the underlying use case the suggestion was looking for.

    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. Support an Azure SQL Data Warehouse as a data source (with enable change tracking).

    It would be useful to be able to connect a SQL DW table to an index. I did try this but it seems SQL DW does not support the ENABLE CHANGE_TRACKING option so that means I could not synch changes which is key. Also I believe Azure search needs a PK on the table to manage changes - and DW does not use primary keys. So it may need new features in SQL DW first.....

    15 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  ·  Indexing  ·  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.

    One thing we will also require for your request is for Azure SQL database to support Integrated Change Tracking as seen in SQL Server.

    Thanks,
    Liam
    Azure Search Product Team

  19. 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 →
  20. provide top N DISTINCT values from suggester API

    At the moment the suggester API return the top N results, but if I want use this feature on a field that contains duplicate values, this request could show me N identical values.
    For example, my index contains the searchable fields address and city (address as the key) and the city field contains only the cities "Parma" and "Pavia". I want to add autocomplete on the city field on the web app. The suggester API with TOP 5 could give me 5 identical values with the city "pavia". But I like to see both the cities in the TOP 5.…

    14 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  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base