How can we improve Azure Search?

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,267 votes
Sign in
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Jean-Sébastien Goupil shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Microsoft
Signed in as (Sign out)
An error occurred while saving the comment
  • Corby commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    3 years and 3 months later still not implemented yet... Dear Azure Team please implement this, 1243 votes should be enough!

  • Anonymous commented  ·   ·  Flag as inappropriate

    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!!

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please do add the support for upgrading. This is causing us a lot of unnecessary manual work.

  • Lukasz K commented  ·   ·  Flag as inappropriate

    this is a very annoying limitation - any further updates when we can expect it

  • Souvik Ghosh commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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?

  • Adam M commented  ·   ·  Flag as inappropriate

    2.5 years since this feedback, and the only progress is "it is being considered..." ?!

  • Mixie commented  ·   ·  Flag as inappropriate

    Microsoft please implement this feature. With the ability to go up from BASIC to Standard and down from Standard to BASIC.
    Justification: as a developer we do a Proof of Concept using customer data, requiring Standard. Then after approval, we remove all but sample data. We would like then to switch back to BASIC -- the customer is now paying in their own environment for Standard. So no loss to Microsoft.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Hit against this today. Importing a large number of documents for a test run, hit against the individual file limit - went to upgrade the tier to carry (in the same way I would for any other Azure service) only to find this is not possible.

    Can't re-create the index as this would involve re-running my import and indexing which I do not really have time for.

← Previous 1

Feedback and Knowledge Base