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

How can we improve Azure Search?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

    345 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      8 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
    • 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…

      109 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        1 comment  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
      • 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.

        25 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
        • Cursor-based pagination

          When new elements are added to the beginning of an index paginating with $top/$skip will return duplicated elements. The cursor-based pagination solves such problems.

          13 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
          • Make errors and warnings as helpful and constructive as possible

            Please try not to provide cryptic error and warning statements that are only understandable by project developers but rather try to provide HELPFUL and CONSTRUCTIVE errors and warnings that more quickly help the poor user.

            I'm a newbie who quickly encountered the error:

            400: {"result":{"Message":"Missing request parameters: definition"}}

            when I tried to create a new index without a fields element. Why couldn't it provide (it certainly "knows" what the problem is) a more helpful, constructive error like

            400: {"result":{"Message":"Missing required fields element when creating a new index"}}

            11 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
            • 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
              Check!
              (thinking…)
              Reset
              or sign in with
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
              • 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
                Check!
                (thinking…)
                Reset
                or sign in with
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
                • 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.…

                  7 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
                  • 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/7_2_Multipart.html) would be more meaningful.

                    2 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
                    • filterAndMergeMany

                      We need a way to update/merge all documents matching a filter criteria. E.g. only change one field for all documents matching a $filter specified.

                      1 vote
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
                      • Don't see your idea?

                      Azure Search

                      Feedback and Knowledge Base