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. Document version support for data consistency and indexers

    External Versioning Support

    Are there any plans to support external versioning like the following: https://www.elastic.co/blog/elasticsearch-versioning-support

    We are trying to migrate off of an Elasticsearch system where versioning support is being used to allow multiple Indexers potentially processing the same document (potentially different versions of the same document).
    By using primary store’s version, we ensure that latest version of document is not overwritten by the older version of document.

    I was reading up on stackoverflow (http://stackoverflow.com/questions/28917204/azure-search-data-consistency) even with Etags support, it seems that each writer will need to read the document from AzureSearch to ensure it has the latest…

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

    70 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 →
  3. 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

    35 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 →
  4. 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.

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

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

  6. Add more document allowance to the free tier

    Thank you for the Free Tier!! We really love it! Just one thing to ask. Is it possible to add more document capacity to the free tier? We know you have to cut it off somewhere but 10,000 is just a bit small for eval purposes when working with big datasets. Maybe 100k or 150k?

    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 →
  7. OCR Cognitive Skill for both printed and handwritten text

    When parsing documents and images through the OCR cognitive skill, the 'handwritten' text extraction algorithm fails on printed documents and vice versa. This obviously isn't a bug, but it is an issue when indexing data dumps of both document types. It seems like a fix might be to have a small binary classifier model which can infer which model is appropriate for each document.
    An alternative might be an easy method of flagging documents as handwritten or printed to handle them with the appropriate model.

    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. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.

    While we’re currently not planning on solving this out of the box, we are exploring a new cognitive services for custom document classification, that you could use to build your own classifier, and then wire it as a cognitive skill to your search pipeline. Feel free to reach out to us if you’re interested in exploring this further.

    Thanks,
    Elad
    Azure Search Product Team

  8. Expose Content as searchable field even in structured (JSON) data

    If I want to index JSON files I can either full text search using parsingMode TEXT or I can index fields using fieldMappings.

    Why not make both available? That way a user can get a fast search using an indexeg field (like a Product number), or a slower one using the file content (like Product description).

    8 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 →
  9. API to check availability of documents for search

    Currently there is short delay before documents become available for search after they were created or updated.

    For better consistency a blocking call that returns after all of the documents updates, creates, etc have been indexed and are ready for search would be great.

    Or provide status api for the set of documents updates, creates, etc sent to understand if they have all been indexed and are ready for search

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

    6 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 →
  11. Expose write metrics not just read metrics through the portal

    At the moment the portal only shows read metrics (QPS, Latency, Throttled) but this is only half the picture of what can be impacting an Azure Search Service.

    Write metrics (e.g. index updates per second) are just as important especially for high volume re-indexing operations,

    To get anything like this needs an export of logs, which goes to an unusable Json format (i.e. CSV is more useful for analysis) and/or a PowerBI account.

    Neither of which are particularly useful for this scenario where we just need a quick review of what's actually going on with our index.

    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 →
  12. Azure Data Factory indexer data source

    Currently Azure Search is supported as one of the Destinations in ADF Pipelines. It would be awesome if we have support for them to act as Data sources. In this way migrating from one Azure search index to another would be easy.

    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 →
  13. Index Dynamics 365

    Add Dynamics 365 Customer Engagement to index options. Today, search is costly for smaller customers as they must create a data warehouse for search.

    4 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. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.

    Also, you might want to take a look at Azure Logic Apps to ingest data from this source and then use a HTTP connector to push data into Azure Search.

    Thanks,
    Liam
    Azure Search Product Team

  14. On bulk merge/upload, response should be 200 ok if document was successfully re-indexed

    The issue is documented here:
    https://stackoverflow.com/questions/50746146/does-mergeorupload-action-on-azure-search-index-takes-some-re-indexing-time-even

    Azure search should respond back with success message on successful re-indexing of the merged\uploaded data as against current behavior which seems to indicate "Merge \Upload request is taken up and would be indexed after unknown time, please keep looking"..

    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 →

    Thank you for your feedback. We understand the value this would bring, but there is concern about keeping an update request open the entire time it takes to index everything contain within it. What we may consider here is an API to request the status of the indexing queue to determine what has/hasn’t been processed. We’d like to know if this would be useful to you.

    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

  15. Detailed Request Monitoring

    We use Sitecore CMS which now supports Azure Search indexes. During our implementation we have discovered that re-index process fails. Using Fiddler we found the Azure Search REST requests that returned 207 (Multi status) responses and then reviewed the response body to determine the errors.

    Beyond Fiddler running as a proxy and capturing the HTTPS traffic from Sitecore - we found no other way to get insight into the requests/responses from Azure Search service.

    We enabled Operation Log monitoring but the Operation Log monitoring does not provide details about request body and response body.

    We looked into Search Traffic Analytics,…

    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 →
  16. Inverted Index

    After import data, I would check the words registered in indexes. However, Azure Search doesn't provide such features.

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