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,249 votes
Vote
Sign in
(thinking…)
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 →

34 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • Padgett Rowell commented  ·   ·  Flag as inappropriate

    +1 for the ability to be able to change pricing tiers. Recreating the index is painful.

    +1 for the ability to change the properties on indexed fields (searchable, facet, retrievable etc) without having to recreate the index.

  • Mads Laumann commented  ·   ·  Flag as inappropriate

    I just ran into this and thought I was doing something wrong/blind...apparently not. As other mentions, you can up/down scale things in general in Azure, why this is confusing and frustrating.
    The "Start out free/Scale as needed" mantra doesn't really fit here, as you need to start all over.
    Besides that, I really think Azure Search is a nice product, but way too expensive :S

  • Dhananjay commented  ·   ·  Flag as inappropriate

    This feature very much required to save cost on backup Index. Why we need to maintain even backup index in same price tier.

  • Vishal Sharma commented  ·   ·  Flag as inappropriate

    yup... this is a important need. deleting and creating another index doesn't look the right way.

  • Dave C commented  ·   ·  Flag as inappropriate

    I really question if this is really a serious product for MSFT? There are so many basic capabilities/needs like this that are just left hanging.

  • Glen Boonzaier commented  ·   ·  Flag as inappropriate

    Why would they implement this for all other Azure functions and not this one? Is there some complexity that we are not aware of?

2 Next →

Feedback and Knowledge Base