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
-
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,045 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Elad
Azure Search Product Team -
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…
257 votesThank 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,
Liam
Azure Search Product Team -
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 votesThe 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 -
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).
20 votes -
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 voteWhile 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?