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. Support schema changes with automated reindexing

    Azure Search should support safe schema changes, such as deletion of fields, or maybe even safe field type changes (e.g., int -> string, or string -> string collection)

    727 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support "swapping" indexes

    Let's say you want to make some changes to an index, like changing from tokenized to indexed or from Edm.String to Collection(Edm.String), ... or even re-index all the data with some additional information.

    It would be great if we could have a "production" and a "staging" slot in an index (similar to Cloud Services for example) where we can do whatever we need to do in the staging slot, and as soon as we're ready (all data has been indexed), we simply swap the staging slot to the production slot and from that point on the new index is used.

    563 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  3. Increase the number of fields per index

    Using certain platforms or applications require the usage of over 1000 fields per index. The limitation is on the low end for a platform like Sitecore - can this be increased?

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

    168 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 →
  5. 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.

    158 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 →
  6. 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.

    57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  7. 46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  8. Extend spatial features to allow indexing and searching of polygons and multi-polygons

    Extend spatial features to allow indexing and searching of polygons and multi-polygons

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  9. Managed service identity support

    Indexing Azure Storage requires a storage account key which makes it more cumbersome to rotate that storage account key. Indexing Azure SQL DB requires a username/password making it more cumbersome to rotate that password. Please allow us to enable a Managed Service Identity (MSI) for Azure Search so that we can index data sources using that identity rather than with account keys and passwords.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow to rename search index column

    Allow to rename search index column

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

    Thank you for your feedback. This is a fair suggestion and something I’d agree we should support. We’re considering this for a future release of Azure Search. Suggestions are typically addressed based on the total number of votes received.

    Thanks,
    Mike Carter
    Azure Search Product Team

  11. Access to queue of azure indexers waiting to run

    I think it would be nice to allow the SDK to have access to the queue of azure indexers waiting to run, that way you can tell which ones will be running next

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  12. Ability to iterate over all documents in an index

    Other search engines have the ability to examine the contents of an index by simply iterating over the document collection. This is extremely use for maintenance operations like reconciling the contents of the index to records in a database. It is quite easy for records to be left behind in the index which no longer have relevance. The only way to accomplish this now is by searching and paging through the results. My current index has over 100,000 entries which is the limitation of the Skip directive. The recommended workaround is to filter the data on another field, however this…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add a skill to merge arrays

    Create a skill that can merge arrays. This would be useful when extracting key-phrases from a set of pages, and then you need to merge them and don't want duplicates

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  14. Indexer(crawler) on Sharepoint document library or any external data source

    Customer has a lot of documents in sharepoint document library.Unlike pushing data to an index, crawling all the documents from external data source(here it is sharepoint) and creating an index in azure search so that we can leverage cognitive services.

    We understood sharepoint integration with azure search is present in your roadmap, but if there is a possibility to leverage index(crawler) to index external data source it would be great. There are lot of clients approaching for this usecase.

    Thanks for your time.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  15. Use a XSD schema to populate the index fields

    We have large scehams that define individual aspects of healthcare data. We would like to use these schemas to define the fields than entering most of these manually. For this to work, obviously we need support for crawling XML data (similar to what you have for JSON). XML provides a good structure and has many industry standard schemas that we can leverage.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  16. Ability to specify a skillset to be used when adding documents to Search Index via DocumentsOperations SDK and REST API

    Need to be able to specify the skillset to be used when adding documents to Azure Search index using the SDK (or even the REST API one - https://docs.microsoft.com/en-us/rest/api/searchservice/addupdate-or-delete-documents). Currently it's only possible by having an indexer. Please refer StackOverflow question for the scenario in which this would be useful:
    https://stackoverflow.com/questions/54529101/using-a-skillset-when-adding-documents-to-azure-search-index/54539852?noredirect=1#comment95962064_54539852

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

Feedback and Knowledge Base