Azure AI Search - Changing pricing tiers

Chris Buley 51 Reputation points

Our Azure AI Search capacity quota has been reached on our search service so I'm aware we need to remove the search service and create a new one. However, I need some clarification on any potential ramifications:

  1. If we delete the search service (Name: X, URL: and create a new one with a higher pricing tier, are we able to use the original name and, subsequently, the same URL?
  2. Our search service is linked to Azure Cosmos DB, so if we delete the search service, is just the indexes/indexer that gets removed, and not the Azure Cosmos DB documents?
  3. Once the new search service is created successfully, can we simply use the Import Data feature, link Azure Cosmos DB and it will automatically create new indexes without issues?

Kind regards

Azure AI Search
Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
856 questions
Azure Cosmos DB
Azure Cosmos DB
An Azure NoSQL database service for app development.
1,533 questions
{count} votes

1 answer

Sort by: Most helpful
  1. VenkateshDodda-MSFT 19,641 Reputation points Microsoft Employee

    @Chris Buley Thanks for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

    Please find the below responses for the above questions

    1. You can delete and recreate the search service with the same. When you are recreating the search service with same name if you are facing any issues. I would suggest you try changing the location for the new search service.
    2. When you delete a search service, the indexes and indexers associated with that service will also be deleted. However, the documents in your Azure Cosmos DB will not be deleted.
    3. Yes, you can use the import wizard, or create indexers for pulling in data. It is a completely n ew indexing.

    Feel free to reach back to me if you have any further questions on this.

    1 person found this answer helpful.
    0 comments No comments