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. Allow to upgrade the pricing tier

    Everywhere in the portal, we can increase/decrease the pricing tier based on our needs.
    With the introduction of Azure Search Basic, we need a way to upgrade to the next level (Standard) when we are close to reach the service limits.

    The only way today to go around this is to bring the index down and create another one.

    1,199 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    30 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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…

    273 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  3. Storage Optimized tier in the Basic tier pricing range (L0)

    For a small business with low traffic and data just over the 2GB limit of the Basic tier it´s really hard to justify to upgrade to standard tier for 3.3x more cost. The performance and scaling for Basic tier is more the enough but the 2GB limit is just to low.
    It would be nice if you could introduce storage optimized layer(L0) for the lower end of the price range where performance and scaling is not important but the storage amount is more than 2GB.

    105 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  4. Pricing for more documents with less storage size / less documents with more storage

    It would be great to have a pricing model where we can index large amounts of small sized documents. (e.g.: 15M documents in 12 GB of storage).
    Same goes the other way around, less documents, with a greater storage size.

    102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →

    The current Azure Search business model charges for storage consumed and not by document count. 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.

    Thanks,
    Mike
    Azure Search Product Team

  5. Provide the ability to hibernate/revive the index

    There are many scenarios where indexes are only needed for particular periods. A simple example is for demo purposes. I want to be able to have an index ready to use, but only use it periodically. It's too expensive to keep it running. It would be more 'cloudy' to have the ability to save/hibernate it to storage, and to be able to revive it from there. (I saw another suggestion to backup/snapshot. That's good but it also needs the ability to be deleted and still be recovered).

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  6. increase the number of available free search services

    We would ideally deploy our entire system using a script to provision and configure all the necessary Azure resources. This is helpful for clean per client deployments and also for qa/test deployments, however being limited to 1 free search service means having to have an expensive basic tier search service per qa/test deployment, or having to share a single shared free tier search service for qa/test/dev. Ideally we'd just be able to deploy 3 free tier search services.

    An alternative to this would be a more finely graduated billing scheme based on usage (currently the cost of the search service…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  7. Turn off Azure Search during off periods.

    My company works from 8:0 am to 5:00 pm
    I would like to turn off the search when I don't need it.
    In addition,
    I would like to have access to the data behind the scenes to provide full control over the results sets.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  8. Create mechanism to increase the maximum running time for cognitive search skillsets or blob indexing with image analysis beyond 1 hour.

    The limit of 1 hour is not enough for using the indexer with cognitive services using OCR.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →

    While the OCR should not take that long, I think what you are saying is that indexers that require a bit of processing don’t index too many documents in a given time period (1 hour).

    We are looking for mechanisms to improve throughput in our enrichment pipeline at this time. Thanks for the feedback!

    -Luis Cabrera
    Azure Search Product Team

  • Don't see your idea?

Azure Search

Feedback and Knowledge Base