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. Possibility to delete all documents in an index without deleting and recreating the index

    You should provide a possibility to delete all documents in an index without having to delete it and creating it again.

    408 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow create, update, delete of Data Sources, Indexes, and Indexers with Service through ARM templates

    You currently can only create a service instance through an ARM template, you then need to make REST calls to create, update, or delete Data Sources, Indexes, and Indexers. This makes using Azure Search a challenge in solutions that are released in a Continuous Delivery model. If I want to use Release Management in VSTS to automate deployments, I need to write additional PowerShell scripts to call Azure Cmdlets to get the Primary Key for the service, then call REST APIs through PowerShell, and suck in JSON files to send as part of the request. It's a very complicated process…

    131 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  3. sintax highlight length

    Could we get a parameter to specify the length of a highlight fragment that is returned when the highlight parameter is used on a field? The string returned is too short for some of our users because they are searching very techincal data and need more context. It would be very useful to be able to return longer fragments depending on the field we're searching so we need control over this.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  4. New Suggestions metadata in response (2014-10-20-Preview)

    Right now when you use the new suggestions feature, you get a match with some optional pre/post tags and a list of fields you indicated in OData select.

    For example, using names from AdventureWorksLT and a suggestor that searches the FirstName and LastName fields, I could make this query:

    https://[instance].search.windows.net/indexes/[index]/docs/suggest?api-version=2014-10-20-Preview&search=bon&suggesterName=namesuggestor&highlightPreTag=%3Cmark%3E&highlightPostTag=%3C%2Fmark%3E&$top=10&$select=FirstName,LastName

    {
    "value": [

    {
    
    "@search.text": "<mark>Bon</mark>ifaz",
    "FirstName": "Luis",
    "LastName": "Bonifaz"
    }

    ]
    }

    The payload is amazing already! For client libraries, it would be incredibly useful to also have an option to return an additional metadata field @search.field. This could indicate which field was "matched" when providing the result. So…

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Return the request URL when running a query operation

    It would be great if the query operation would return the original request's URL. Thus, it would be possible to parse the request back to the facets used on the query, which would help in having the correct selected facets shown on the search results page rather than have them saved in a middle repository (cookie, cache, posted etc.).

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  6. For the batch requests, leverage multipart content-type

    For the batch requests (Index Population APIs), leveraging the multipart content-type (http://www.w3.org/Protocols/rfc1341/72Multipart.html) would be more meaningful.

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

Feedback and Knowledge Base