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

    108 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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).

    41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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: Microsoft
    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?

Feedback and Knowledge Base