Nick

My feedback

  1. 58 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Nick supported this idea  · 
  2. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API Management  ·  Flag idea as inappropriate…  ·  Admin →
    Nick shared this idea  · 
  3. 31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Storage » Queues  ·  Flag idea as inappropriate…  ·  Admin →
    Nick supported this idea  · 
  4. 607 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  Azure Search » Indexing  ·  Flag idea as inappropriate…  ·  Admin →
    Nick commented  · 

    Yes, I've been thinking about this too. Alternatively, supporting the ability to rename indexes could be a viable workaround for this. It would mean your production index could be, for example, idx-products, and you could additionally have an idx-products-staging. Then, when you want to swap, you could rename idx-products to something else (eg idx-products-old) and rename idx-products-staging to idx-products. Granted it's not the neatest solution as it can't be done in an atomic operation, but it could work for some.

    Nick supported this idea  · 

Feedback and Knowledge Base