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.
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team
This feature will be really helpful!
Ajeet Kumar commented
This feature will be very handy for our team where we constantly need to think to select the correct pricing tier for a product where usage might change in future
Dan O'Brien commented
I would like to echo what others have said. I am having a very difficult time pitching this service to my client given the risk involved. They are considering indexing nearly 200 million documents, including image extraction and OCR, so we estimate that the indexing step alone would cost over $600,000. The idea that as they grow they may face having to destroy and rebuild indexes (for another $600,000) just so they can upgrade the pricing tier of the service is kind of a deal breaker. The pricing model on this service seems out of line with the other cloud services where the whole idea is to only pay for what you use, and customers can easily scale up as they grow. Please implement this feature so we can help you sell your products to our clients. In the meantime, you could offer some sort of credit for customers that have to re-index in order to upgrade to a new pricing tier.
David Lahuta commented
It's way too long Microsoft..!
Please deliver ASAP
Devos, Scott P. commented
Three-and-a-half years later and still nothing? What is wrong with you, Microsoft? Don't you realize that the people who need this most are the people who are trying to create marketable apps using your technology? In other words, your best customers? Why would you continue to put a hurdle in the path of those who what to sell your services for you?
Please wake up!
Joseph Ficara commented
This is very important to us as well. As the business grows and becomes more successful the original tier may no longer scale to the current needs. Creating a new search service and loading it from scratch can be very time consuming given the amount of data that exists in current instance. Having a seamless way to upgrade to the next pricing tier would be very helpful in this regard.
Unable to figure out how to go from S1 to S2. We need to open up the additional search indexes as we have maxed out our 50. There appears to be no way to do this within the portal. I've created a support ticket to ask for an Azure tech to help. It takes 2 seconds to resize a VM to a bigger box, I thought upgrading Search would be a similar procedure.
Elia Franke commented
3 years and 3 months later still not implemented yet... Dear Azure Team please implement this, 1243 votes should be enough!
Steve NZ commented
Really??!? how is this still not a thing? What's the limitation/hold up here?
Is that not deployed yet, is it?
David Khu commented
Agreed! Please add this feature
Please add this feature. Installing an App from the Marketplace which automatically installs the Azure Search service automatically installs whatever level of service the developers deemed appropriate which can cause unnecessary costs for a service that is not utilized to it's fullest ability.
Throwing money out the window because of poor design!!
this is ridiculous!!!
Please do add the support for upgrading. This is causing us a lot of unnecessary manual work.
Alex Fiala commented
Agreed, please add this feature.
Me need this.
Plase, do this. Its very helpfull
Lukasz K commented
this is a very annoying limitation - any further updates when we can expect it
Souvik Ghosh commented
Although I re-created a new Search service now and linked to my existing QnAMaker service, I still don't get the QnAMaker service working with the newly linked Search service. Now, it seems I have to create the QnAMaker service again with a new Search service just because the Search service cannot be upgraded. Really painful :(.
Graham Bunce commented
So... "considering it" usually means "it's kicked to the long grass never to return." Give us some dates. Are we 6 months, 12 months, 2 years away? Architecture changes needed? Why is this not feasible to do?