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. Support multi-fields

    It would be nice to have one data value analyzed multiple different ways.

    https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html

    6 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 →
  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. Specify maintenance window times

    In the middle of the day yesterday, my service had an outage. We traced it to Azure Search, and upon logging into the Azure Portal, Azure Search was showing in a "Provisioning" state. When we contacted Azure support, they stated "service was undergoing a planned deployment at this time. The deployment hit an issue that required a VM restart. Please note that we make no guarantees about availability for write operations such as indexing in services with less than 3 replicas."

    We have 2 replica instance. I understand a 2 replica only provides high availability for READ operations.

    So for…

    3 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 →
  4. CORS support for management API (like create index, run indexer and etc)

    It would be great if index/indexer/datasource management REST API will support CORS. Azure Resource Manager REST API for ex. supports such kind of working with. Why Azure Search management API does not? If I already have an admin key I can use local powershell to call Invoke-RestMethod, or make a server side calls... Why I cannot use a locally hosted AngularJs/AJAX client to do a management work? Thanks.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide option to return total facet counts without all facet values included in response

    We have facets with thousands of unique values, sometimes up to around 100k. In our UI, we'd like to show the top 10 or so values of each facet to allow the user to filter by them, but we have no need to display all 100k. That said, we need to display the facet counts so they know roughly how much data is being searched.

    To do that currently, we have to set the facet counts arbitrarily high to make sure the accurate counts are retrieved, but that means we're getting back huge HTTP responses when really we just want…

    45 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 →
  7. Add a paid shared option between the Free tier and the Basic tier

    While the basic tier was a step in the right direction, it's not working perfectly for us.

    We are running a single basic instance for budgetary reasons. As a result, we see occasional (albeit brief) slowdowns/outages when code updates are deployed by the azure search team.

    My understanding is that the free tier actually has better availability than a single dedicated instance.

    Our index fits in the free tier. However, we wouldn't have enough room for QA and DEV indexes.

    This has me considering the odd arrangement of running our production index in the free tier for higher availability, and…

    9 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 →
  8. 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

  9. Add combo field support

    Add ability to combine existing fields in index.

    Similar to SQL example below:

    ALTER TABLE SearchData ADD
    Combo As
    [Name] + char(32) +
    [Description] + char(32) +
    [MetaData] + char(32) +
    [OwnerData] + char(32) +
    [CategoryData] + char(32) PERSISTED

    Example in Azure Search:
    e.g.
    idx.FirstName = "John" Edm.String
    idx.LastName = "Doe" Edm.String
    idx.Name = "John Doe"; (Combo, of Firstname and lastname) (Internally could act as Collection(Edm.String) ??)

    3 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 →
  10. 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 →
  11. Localization of date

    As of now, Azure Search store and only filters date in UTC format, 2009-06-15T13:45:30.0000000Z.

    But user search date in their localized format:
    1. aves vistas em 05/06/2009
    2. livros vendidos em 5 de junho de 2009

    THANKS

    4 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 →
  12. Pricing based on transactional throughput, similar to SQL Azure

    The current model is a lot like the old SQL Azure models, where it was the volume of data that largely drove the cost of the service. SQL Azure became an affordable breakthrough when it shifted toward pricing based on overall transactional throughput (i.e., large databases that did not need to handle huge volumes were now affordable).

    Search should work the same way. If I operate a marginally popular web forum, for example, I may have several gigs of data to index, but the storage of that is the cheap part. It doesn't get a lot of queries, and new…

    312 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  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  13. SQL Server integrated change detection for VIEWS

    Currently, only tables can use SQL Server integrated change detection, for automatically detect if rows are changed or deleted.

    For views, this is manually coded.

    Please, add support to it.

    THANKS


    Text removed from https://azure.microsoft.com/en-us/documentation/articles/search-howto-connecting-azure-sql-database-to-azure-search-using-indexers-2015-02-28/

    If the data is scattered across multiple tables, you can create a view and use that view with the indexer. However, be aware that if you use a view, you won’t be able to use SQL Server integrated change detection. See this section for more details.

    13 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 →
  14. Provide a Ruby SDK for Azure Search

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

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

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

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

    143 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  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 →
  19. Support vertically scale-up by choosing VM size

    Right now, we can only scale out the search service by setting partition and replica. It is nice to be able to scale up the service vertically by choose more powerful VM, say A4, A7 etc..., so hide the VM details but expose CPU/Memory options to user.

    9 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 →
  20. Clustering

    Clustering is a well known field in data mining. When applied to text it can be used for

    Organisation
    Summarisation
    Classification

    of text (documents/phrases etc).

    I would like to see clustering in azure Search or perhaps made available in Azure ML and applied against Azure Search.

    An example of clustering can be found in Mahout

    https://mahout.apache.org/users/clustering/latent-dirichlet-allocation.html

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

Feedback and Knowledge Base