@@ -9,8 +9,8 @@ ms.author: heidist
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: reference
-ms.date: 09/19/2024
+ms.topic: concept-article
+ms.date: 02/19/2025
 ---
 
 # Troubleshooting common indexer errors and warnings in Azure AI Search

@@ -4,85 +4,94 @@ titleSuffix: Azure AI Search
 description: Learn how to set up an Azure AI Search resource in the Azure portal. Choose resource groups, regions, and a pricing tier.
 
 manager: nitinme
-author: HeidiSteen
-ms.author: heidist
+author: haileytap
+ms.author: haileytapia
 ms.service: azure-ai-search
 ms.custom:
   - references_regions
   - build-2024
-ms.topic: conceptual
-ms.date: 01/15/2025
+ms.topic: how-to
+ms.date: 02/20/2025
 ---
 
 # Create an Azure AI Search service in the Azure portal
 
-[**Azure AI Search**](search-what-is-azure-search.md) is an information retrieval platform for the enterprise. It supports traditional search and conversational AI-driven search for "chat with your data" experiences over your proprietary content.
+[Azure AI Search](search-what-is-azure-search.md) is an information retrieval platform for the enterprise. It supports traditional search and conversational, AI-driven search for "chat with your data" experiences across your proprietary content.
 
-The easiest way to create a service is using the [Azure portal](https://portal.azure.com/), which is covered in this article.
+The easiest way to create a search service is through the [Azure portal](https://portal.azure.com/), which is covered in this article.
 
-You can also use [Azure PowerShell](search-manage-powershell.md#create-or-delete-a-service), [Azure CLI](search-manage-azure-cli.md#create-or-delete-a-service), the [Management REST API](search-manage-rest.md#create-or-update-a-service), an [Azure Resource Manager service template](search-get-started-arm.md), a [Bicep file](search-get-started-bicep.md), or [Terraform](search-get-started-terraform.md).
+[![Animated GIF showing how to create an Azure AI Search service in the Azure portal.](./media/search-create-service-portal/AnimatedGif-AzureSearch-small.gif)](./media/search-create-service-portal/AnimatedGif-AzureSearch.gif#lightbox)
 
-[![Animated GIF](./media/search-create-service-portal/AnimatedGif-AzureSearch-small.gif)](./media/search-create-service-portal/AnimatedGif-AzureSearch.gif#lightbox)
+You can also use:
 
-## Before you start
-
-A few service properties are fixed for the lifetime of the service. Before creating the service, decide on a name, region, and tier.
++ [Azure PowerShell](search-manage-powershell.md#create-or-delete-a-service)
++ [Azure CLI](search-manage-azure-cli.md#create-or-delete-a-service)
++ [Management REST API](search-manage-rest.md#create-or-update-a-service)
++ [Azure Resource Manager template](search-get-started-arm.md)
++ [Bicep](search-get-started-bicep.md)
++ [Terraform](search-get-started-terraform.md)
 
-+ [Service name](#name-the-service) becomes part of the URL endpoint. The name must be unique and it must conform to naming rules.
+## Before you start
 
-+ [Region](search-region-support.md) determines data residency and the availability of certain features. Semantic ranker and Azure AI integration come with region requirements. Make sure your region of choice supports the features you need.
+Some properties are fixed for the lifetime of the search service. Before creating your service, decide on the following properties:
 
-+ [Service tier](search-sku-tier.md) determines infrastructure, service limits, and billing. Some features aren't available on lower or specialized tiers.
+| Property | Description |
+|--|--|
+| [Name](#name-your-service) | Becomes part of the URL endpoint. The name must be unique and follow naming rules. |
+| [Region](search-region-support.md) | Determines data residency and availability of certain features. For example, semantic ranker and Azure AI integration have region requirements. Choose a region that supports the features you need. |
+| [Tier](search-sku-tier.md) | Determines infrastructure, service limits, and billing. Some features aren't available on lower or specialized tiers. |
 
-## Subscribe (free or paid)
+## Subscribe to Azure
 
-Paid (or billable) search occurs when you choose a billable tier (Basic or higher) when creating the resource on a billable Azure subscription.
+Azure AI Search requires a free or pay-as-you-go Azure subscription.
 
-To try Azure AI Search for free, [open a trial subscription](https://azure.microsoft.com/pricing/free-trial/?WT.mc_id=A261C142F) and then create your search service by choosing the **Free** tier. You can have one free search service per Azure subscription. Free search services are intended for short-term evaluation of the product for nonproduction applications. Generally, you can complete all of the quickstarts and most tutorials, except for those featuring semantic ranker (it requires a billable service). Free services that are inactive for an extended period of time can be deleted by Microsoft to make room for other services.
+To try Azure AI Search for free, [start a trial subscription](https://azure.microsoft.com/pricing/free-trial/?WT.mc_id=A261C142F) and then [create your search service on the Free tier](#choose-a-tier). Each Azure subscription can have one free search service, which is intended for short-term, non-production evaluation of the product. You can complete all of our quickstarts and most of our tutorials on the Free tier. For more information, see [Try Azure AI Search for free](search-try-for-free.md).
 
-Alternatively, you can use free credits to try out paid Azure services. With this approach, you can create your search service at **Basic** or higher to get more capacity. Your credit card is never charged unless you explicitly change your settings and ask to be charged. Another approach is to [activate Azure credits in a Visual Studio subscription](https://azure.microsoft.com/pricing/member-offers/msdn-benefits-details/?WT.mc_id=A261C142F). A Visual Studio subscription gives you credits every month you can use for paid Azure services.
+> [!IMPORTANT]
+> To make room for other services, Microsoft might delete free services that are inactive for an extended period of time.
 
 ## Find the Azure AI Search offering
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 
-1. Select (**Create Resource"**) in the top-left corner.
+1. In the upper-left corner of your dashboard, select **Create a resource**.
 
-1. Use the search bar to find "Azure AI Search*.
+   :::image type="content" source="media/search-create-service-portal/create-resource.png" lightbox="media/search-create-service-portal/create-resource.png" alt-text="Screenshot of the Create a Resource button in the Azure portal." border="true":::
 
-:::image type="content" source="media/search-create-service-portal/find-search3.png" lightbox="media/search-create-service-portal/find-search3.png" alt-text="Screenshot of the Create Resource page in the Azure portal." border="true":::
+1. Use the search box to find **Azure AI Search**.
+
+   :::image type="content" source="media/search-create-service-portal/azure-ai-search-tile.png" lightbox="media/search-create-service-portal/azure-ai-search-tile.png" alt-text="Screenshot of the Azure AI Search tile in the Azure portal." border="true":::
 
 ## Choose a subscription
 
-If you have more than one subscription, choose one for your search service. If you're implementing [customer-managed encryption](search-security-manage-encryption-keys.md) or if you use other features that depend on managed service identities for [external data access](search-indexer-securing-resources.md), choose the same subscription as the one used for Azure Key Vault or other services for which managed identities are used.
+If you have multiple Azure subscriptions, choose one for your search service.
 
-## Set a resource group
+If you're implementing [customer-managed encryption](search-security-manage-encryption-keys.md) or using other features that rely on managed service identities for [external data access](search-indexer-securing-resources.md), choose the same subscription you use for Azure Key Vault or other services that use managed identities.
 
-A resource group is a container that holds related resources for your Azure solution. It's useful for consolidating same-solution resources, monitoring costs, and for checking the creation date of your search service.
+## Set a resource group
 
-:::image type="content" source="media/search-create-service-portal/new-resource-group.png" lightbox="media/search-create-service-portal/new-resource-group.png" alt-text="Screenshot of the Create Resource Group page in the Azure portal." border="true":::
+A resource group is a container that holds related resources for an Azure solution. Use it to consolidate same-solution resources, monitor costs, and check the creation date of your search service.
 
-Over time, you can track current and projected costs all-up or you can view charges for individual resources. The following screenshot shows the kind of cost information you can expect to see when you combine multiple resources into one group.
+:::image type="content" source="media/search-create-service-portal/create-resource-group.png" lightbox="media/search-create-service-portal/create-resource-group.png" alt-text="Screenshot of the Create a Resource Group dialog on the Create a Search Service page." border="true":::
 
-:::image type="content" source="media/search-create-service-portal/resource-group-cost-management.png" lightbox="media/search-create-service-portal/resource-group-cost-management.png" alt-text="Screenshot of the Managing costs page in the Azure portal." border="true":::
+Over time, you can track current and projected costs for individual resources and for the overall resource group. The following screenshot shows the cost information that's available when you combine multiple resources into one group:
 
-> [!TIP]
-> Resource groups simplify cleanup because deleting a resource group deletes everything within it.
+:::image type="content" source="media/search-create-service-portal/resource-group-cost-management.png" lightbox="media/search-create-service-portal/resource-group-cost-management.png" alt-text="Screenshot of the Cost Management page in the Azure portal." border="true":::
 
-## Name the service
+## Name your service
 
-In Instance Details, provide a service name in the **URL** field. The name is part of the endpoint against which API calls are issued: `https://your-service-name.search.windows.net`. For example, if you want the endpoint to be `https://myservice.search.windows.net`, you would enter `myservice`.
+Enter a name for your search service. The name is part of the endpoint against which API calls are issued: `https://your-service-name.search.windows.net`. For example, if you enter `myservice`, the endpoint becomes `https://myservice.search.windows.net`.
 
-Service name requirements:
+When naming your service, follow these rules:
 
-+ Unique within the search.windows.net namespace
-+ Between 2-60 characters in length
-+ Consist of lowercase letters, digits, or dashes (`-`)
-+ Don't use dashes in the first two characters or as the last single character
-+ Don't use consecutive dashes anywhere
++ Use a name that's unique within the `search.windows.net` namespace.
++ Use between 2 and 60 characters.
++ Use only lowercase letters, digits, and dashes (-).
++ Don't use dashes as the first two characters or the last character.
++ Don't use consecutive dashes.
 
 > [!TIP]
-> If you have multiple search services, it helps to include the region (or location) in the service name as a naming convention. A name like `mysearchservice-westus` can save you a trip to the properties page when deciding how to combine or attach resources.
+> If you have multiple search services, it's helpful to include the region in the service name. For example, when deciding how to combine or attach resources, the name `myservice-westus` might save you a trip to the Properties page.
 
 ## Choose a region
 
@@ -91,144 +100,149 @@ Service name requirements:
 
 If you use multiple Azure services, putting all of them in the same region minimizes or voids bandwidth charges. There are no charges for data egress among same-region services.
 
-Generally, choose a region near you, unless the following considerations apply:
+In most cases, choose a region near you, unless any of the following apply:
 
-+ Your nearest region is [at capacity](search-sku-tier.md#region-availability-by-tier). One advantage to using the Azure portal for resource setup is that it provides only those regions and tiers that are available.
++ Your nearest region is [at capacity](search-sku-tier.md#region-availability-by-tier). The Azure portal has the advantage of hiding unavailable regions and tiers during resource setup.
 
 + You want to use integrated data chunking and vectorization or built-in skills for AI enrichment. Integrated operations have region requirements.
 
-+ You want to use Azure Storage for indexer-based indexing or you need to store application data that isn't in an index. Debug session state, enrichment caches, and knowledge stores are Azure AI Search features that have a dependency on Azure Storage. The region you choose for Azure Storage has implications for network security. Specifically, if you're setting up a firewall, you should place the resources in *separate regions*. For more information, see [Outbound connections from Azure AI Search to Azure Storage](search-indexer-securing-resources.md).
++ You want to use Azure Storage for indexer-based indexing, or you want to store application data that isn't in an index. Debug session state, enrichment caches, and knowledge stores are Azure AI Search features that depend on Azure Storage. The region you choose for Azure Storage has implications for network security. If you're setting up a firewall, you should place the resources in separate regions. For more information, see [Outbound connections from Azure AI Search to Azure Storage](search-indexer-securing-resources.md).
 
 ### Checklist for choosing a region
 
-1. Is Azure AI Search available in a nearby region? Check the [supported regions list](search-region-support.md).
+1. Is Azure AI Search available in a nearby region? Check the [list of supported regions](search-region-support.md).
 
 1. Do you have a specific tier in mind? Check [region availability by tier](search-sku-tier.md#region-availability-by-tier).
 
 1. Do you have business continuity and disaster recovery (BCDR) requirements? Create two or more search services in [regional pairs](/azure/reliability/cross-region-replication-azure#azure-paired-regions) within [availability zones](search-reliability.md#availability-zones). For example, if you're operating in North America, you might choose East US and West US, or North Central US and South Central US, for each search service.
 
 1. Do you need [AI enrichment](cognitive-search-concept-intro.md), [integrated data chunking and vectorization](vector-search-integrated-vectorization.md), or [multimodal image search](search-get-started-portal-image-search.md)? Azure AI Search, Azure OpenAI, and Azure AI multiservice must coexist in the same region.
 
-   + Start with [Azure OpenAI regions](/azure/ai-services/openai/concepts/models#model-summary-table-and-region-availability) because it has the most variability. Azure OpenAI provides embedding models and chat models for RAG and integrated vectorization.
+   + Start with [Azure OpenAI regions](/azure/ai-services/openai/concepts/models#model-summary-table-and-region-availability) because they have the most variability. Azure OpenAI provides embedding models and chat models for RAG and integrated vectorization.
 
-   + Check [Azure AI Search regions](search-region-support.md) for a match to your Azure OpenAI region. If you're using OCR, entity recognition, or other skills backed by Azure AI, the **AI Integration** column indicates whether Azure AI multiservice is in the same region as Azure AI Search.
+   + Check [Azure AI Search regions](search-region-support.md#azure-public-regions) for a match to your Azure OpenAI region. If you're using OCR, entity recognition, or other skills backed by Azure AI, the **AI service integration** column indicates whether Azure AI multiservice and Azure AI Search are in the same region.
 
-   + Check [multimodal embedding regions](/azure/ai-services/computer-vision/overview-image-analysis#region-availability) for multimodal APIs and image search. This API is accessed through an Azure AI multiservice account, but it's available in fewer regions than Azure AI multiservice in general.
+   + Check [multimodal embedding regions](/azure/ai-services/computer-vision/overview-image-analysis#region-availability) for multimodal APIs and image search. This API is accessed through an Azure AI multiservice account, but in general, it's available in fewer regions than Azure AI multiservice.
 
 ### Regions with the most overlap
 
-Currently, the following regions offer cross-region among all three services (Azure AI Search, Azure OpenAI, Azure AI Vision multimodal). This list isn't definitive, and there might be more choices beyond the regions listed here depending on the tier. Also, region status can change quickly, so be sure to confirm region choice before installing.
+Currently, the following regions offer cross-regional availability for Azure AI Search, Azure OpenAI, and Azure AI Vision multimodal:
 
-+ **Americas**: West US, East US
-+ **Europe**: Switzerland North, Sweden Central
++ Americas: West US, East US
++ Europe: Switzerland North, Sweden Central
+
+This list isn't definitive, and depending on your tier, you might have more choices. Region status can also change quickly, so confirm your region choice before creating your search service.
 
 ## Choose a tier
 
-Azure AI Search is offered in [multiple pricing tiers](https://azure.microsoft.com/pricing/details/search/): Free, Basic, Standard, or Storage Optimized. Each tier has its own [capacity and limits](search-limits-quotas-capacity.md). There are also several features that are tier-dependent.
+Azure AI Search is offered in multiple [pricing tiers](https://azure.microsoft.com/pricing/details/search/):
 
-Review the [tier descriptions](search-sku-tier.md) for computing characteristics, [feature availability](search-sku-tier.md#feature-availability-by-tier), and [region availability](search-sku-tier.md#region-availability-by-tier).
++ Free
++ Basic
++ Standard
++ Storage Optimized
 
-Basic and Standard are the most common choices for production workloads, but many customers start with the Free service. Among the billable tiers, key differences are partition size and speed, and limits on the number of objects you can create.
+Each tier has its own [capacity and limits](search-limits-quotas-capacity.md), and some features are tier dependent. For information about computing characteristics, feature availability, and region availability, see [Choose a service tier for Azure AI Search](search-sku-tier.md).
 
-:::image type="content" source="media/search-create-service-portal/select-pricing-tier.png" lightbox="media/search-create-service-portal/select-pricing-tier.png" alt-text="Screenshot of Select a pricing tier page." border="true":::
+The Basic and Standard tiers are the most common for production workloads, but many customers start with the Free tier. The billable tiers differ primarily in partition size, partition speed, and limits on the number of objects you can create.
 
-Search services created after April 3, 2024 have larger partitions and higher vector quotas at every billable tier.
+:::image type="content" source="media/search-create-service-portal/select-pricing-tier.png" lightbox="media/search-create-service-portal/select-pricing-tier.png" alt-text="Screenshot of the Select Pricing Tier page in the Azure portal." border="true":::
 
-Remember, a pricing tier can't be changed once the service is created. If you need a higher or lower tier, you should re-create the service.
+> [!NOTE]
+> + You can't change the tier after creating your search service, so choose carefully.
+> + Search services created after April 3, 2024 have larger partitions and higher vector quotas at every billable tier.
 
 ## Create your service
 
-After you've provided the necessary inputs, go ahead and create the service.
+After providing the necessary inputs, create your search service.
 
-:::image type="content" source="media/search-create-service-portal/new-service3.png" lightbox="media/search-create-service-portal/new-service3.png" alt-text="Screenshot of the Review and create the service page." border="true":::
+:::image type="content" source="media/search-create-service-portal/create-search-service.png" lightbox="media/search-create-service-portal/create-search-service.png" alt-text="Screenshot of the Review and Create button on the Create a Search Service page." border="true":::
 
-Your service is deployed within minutes. You can monitor progress through Azure notifications. Consider pinning the service to your dashboard for easy access in the future.
+Your service is deployed within minutes, and you can monitor its progress with Azure notifications. Consider pinning the service to your dashboard for easy access in the future.
 
-:::image type="content" source="media/search-create-service-portal/monitor-notifications.png" lightbox="media/search-create-service-portal/monitor-notifications.png" alt-text="Screenshot of the Monitor and pin the service page." border="true":::
+:::image type="content" source="media/search-create-service-portal/portal-notifications.png" lightbox="media/search-create-service-portal/portal-notifications.png" alt-text="Screenshot of the Notifications tab in the Azure portal." border="true":::
 
 ## Configure authentication
 
-Unless you're using the Azure portal, programmatic access to your new service requires that you provide the URL endpoint and an authenticated connection. You can use either or both of these options:
+When you create a search service, key-based authentication is the default, but it's not the most secure option. We recommend that you replace it with role-based access.
 
-+ [Connect using key-based authentication](search-security-api-keys.md)
-+ [Connect using Azure roles](search-security-rbac.md)
+To enable role-based access for your service:
 
-1. When setting up a programmatic connection, you need the search service endpoint. On the **Overview** page, locate and copy the URL endpoint on the right side of the page.
+1. Go to your search service in the [Azure portal](https://portal.azure.com/).
 
-   :::image type="content" source="media/search-create-service-portal/get-endpoint.png" lightbox="media/search-create-service-portal/get-endpoint.png" alt-text="Screenshot of the service Overview page with URL endpoint." border="true":::
+1. From the left pane, select **Settings** > **Keys**. You can connect to your service using [API keys](search-security-api-keys.md), [Azure roles](search-security-rbac.md), or both. Select **Both** until you assign roles, after which you can select **Role-based access control**.
 
-1. To set authentication options, use the **Keys** page. Most quickstarts and tutorials use API keys for simplicity, but if you're setting up a service for production workloads, consider using Azure roles. You can copy keys from this page.
+   :::image type="content" source="media/search-create-service-portal/authentication-options.png" lightbox="media/search-create-service-portal/authentication-options.png" alt-text="Screenshot of the Keys tab with authentication options." border="true":::
 
-   :::image type="content" source="media/search-create-service-portal/set-authentication-options.png" lightbox="media/search-create-service-portal/set-authentication-options.png" alt-text="Screenshot of the Keys page with authentication options." border="true":::
+## Scale your service
 
-An endpoint and key aren't needed for portal-based tasks. The Azure portal is already linked to your Azure AI Search resource with admin rights. For a portal walkthrough, start with [Quickstart: Create an Azure AI Search index in the Azure portal](search-get-started-portal.md).
+After deploying your search service, you can [scale it to meet your needs](search-limits-quotas-capacity.md). Azure AI Search offers two scaling dimensions: *replicas* and *partitions*. Replicas allow your service to handle a higher load of search queries, while partitions allow your service to store and search through more documents.
 
-## Scale your service
+Scaling is available only on billable tiers. On the Free tier, you can't scale your service or configure replicas and partitions.
 
-After a search service is provisioned, you can [scale it to meet your needs](search-limits-quotas-capacity.md). On a billable tier, you can scale the service in two dimensions: replicas and partitions. For the free service, scale up isn't available and replica and partition configuration isn't offered.
+> [!IMPORTANT]
+> Your service must have [two replicas for read-only SLA and three replicas for read/write SLA](https://azure.microsoft.com/support/legal/sla/search/v1_0/).
 
-***Partitions*** allow your service to store and search through more documents.
+Adding resources will increase your monthly bill. Use the [pricing calculator](https://azure.microsoft.com/pricing/calculator/) to understand the billing implications. You can adjust resources based on load, such as increasing resources for initial indexing and decreasing them later for incremental indexing.
 
-***Replicas*** allow your service to handle a higher load of search queries.
+To scale your service:
 
-Adding resources increases your monthly bill. The [pricing calculator](https://azure.microsoft.com/pricing/calculator/) can help you understand the billing ramifications of adding resources. Remember that you can adjust resources based on load. For example, you might increase resources to create a full initial index, and then reduce resources later to a level more appropriate for incremental indexing.
+1. Go to your search service in the [Azure portal](https://portal.azure.com/).
 
-> [!IMPORTANT]
-> A service must have [2 replicas for read-only SLA and 3 replicas for read/write SLA](https://azure.microsoft.com/support/legal/sla/search/v1_0/).
+1. From the left pane, select **Settings** > **Scale**.
 
-1. Go to your search service page in the Azure portal.
-1. In the left-navigation pane, select **Settings** > **Scale**.
-1. Use the slidebar to add resources of either type.
+   :::image type="content" source="media/search-create-service-portal/scale-settings.png" lightbox="media/search-create-service-portal/scale-settings.png" alt-text="Screenshot of the Scale tab with sliders for adding replicas and partitions." border="true":::
 
-:::image type="content" source="media/search-create-service-portal/settings-scale.png" lightbox="media/search-create-service-portal/settings-scale.png" alt-text="Screenshot of the scale page." border="true":::
+1. Use the sliders to add replicas and partitions.
 
 ## When to add a second service
 
-Most customers use just one service provisioned at a tier [sufficient for expected load](search-capacity-planning.md). One service can host multiple indexes, subject to the [maximum limits of the tier you select](search-limits-quotas-capacity.md#index-limits), with each index isolated from another. In Azure AI Search, requests can only be directed to one index, minimizing the chance of accidental or intentional data retrieval from other indexes in the same service.
+Most customers use a single search service at a tier [sufficient for the expected load](search-capacity-planning.md). One service can host multiple indexes, each isolated from the others, within the [maximum limits of your chosen tier](search-limits-quotas-capacity.md#index-limits). In Azure AI Search, you can direct requests to only one index, reducing the chance of retrieving data from other indexes in the same service.
 
-Although most customers use just one service, service redundancy might be necessary if operational requirements include the following:
+However, you might need a second service for the following operational requirements:
 
-+ [Business continuity and disaster recovery (BCDR)](/azure/reliability/cross-region-replication-azure). Azure AI Search doesn't provide instant failover if there's an outage.
++ [Business continuity and disaster recovery (BCDR)](/azure/reliability/cross-region-replication-azure). If there's an outage, Azure AI Search won't provide instant failover.
++ [Multitenant architectures](search-modeling-multitenant-saas-applications.md) that require two or more services.
++ Globally deployed applications that require services in each geography to minimize latency.
 
-+ [Multitenant architectures](search-modeling-multitenant-saas-applications.md) sometimes call for two or more services.
+> [!NOTE]
+> In Azure AI Search, you can't separate indexing and querying operations, so don't create multiple services for separate workloads. An index is always queried on the service in which it was created, and you can't copy an index to another service.
 
-+ Globally deployed applications might require search services in each geography to minimize latency.
+A second service isn't required for high availability. You achieve high availability for queries by using two or more replicas in the same service. Because the replicas are updated sequentially, at least one is operational when a service update is rolled out. For more information about uptime, see [Service Level Agreements](https://azure.microsoft.com/support/legal/sla/search/v1_0/).
 
-> [!NOTE]
-> In Azure AI Search, you can't segregate indexing and querying operations; thus, you would never create multiple services for segregated workloads. An index is always queried on the service in which it was created (you can't create an index in one service and copy it to another).
+## Add more services to your subscription
 
-A second service isn't required for high availability. High availability for queries is achieved when you use two or more replicas in the same service. Replica updates are sequential, which means at least one is operational when a service update is rolled out. For more information about uptime, see [Service Level Agreements](https://azure.microsoft.com/support/legal/sla/search/v1_0/).
+Azure AI Search limits the [number of search services](search-limits-quotas-capacity.md#subscription-limits) you can initially create in a subscription. If you reach your limit, you can request more quotas.
 
-## Add more services to a subscription
+You must have Owner or Contributor permissions for the subscription to request quota. Depending on your region and data center capacity, you might be able to automatically request quota to add services to your subscription. If the request fails, reduce the number or file a support ticket. Expect a one-month turnaround for a large quota increase, such as more than 30 extra services.
 
-Azure AI Search restricts the [number of search services](search-limits-quotas-capacity.md#subscription-limits) you can initially create in a subscription. If you exhaust your maximum limit, you can request more quota.
+To request more subscription quota:
 
-You must have Owner or Contributor permissions on the subscription to request quota.
-Depending on region and datacenter capacity, you can automatically request more quota to add services to your subscription. If the request fails, you should either decrease the number or file a support ticket. For a large increase in quota, such as more than 30 extra services, you should expect a one-month turnaround.
+1. Go to your dashboard in the [Azure portal](https://portal.azure.com/).
 
-1. Sign in to the Azure portal, search for "quotas" in your dashboard, and then select the **Quotas** service.
+1. Use the search box to find the **Quotas** service.
 
-   :::image type="content" source="media/search-create-service-portal/quota-search.png" lightbox="media/search-create-service-portal/quota-search.png" alt-text="Screenshot of the quota search term and Quotas service in the results.":::
+   :::image type="content" source="media/search-create-service-portal/quota-search.png" lightbox="media/search-create-service-portal/quota-search.png" alt-text="Screenshot of the Quota search term and the Quotas service in the results.":::
 
-1. In the Quota's Overview page, select **Search**.
+1. On the **Overview** tab, select the **Search** tile.
 
-   :::image type="content" source="media/search-create-service-portal/quota-overview-page.png" lightbox="media/search-create-service-portal/quota-overview-page.png" alt-text="Screenshot of the search tile in the Quota's overview page.":::
+   :::image type="content" source="media/search-create-service-portal/quota-overview-page.png" lightbox="media/search-create-service-portal/quota-overview-page.png" alt-text="Screenshot of the Search tile on the Overview page.":::
 
-1. Set filters so that you can review existing quota for search services in the current subscription. We recommend filtering by usage.
+1. Set filters to review the existing quota for search services in your current subscription. We recommend filtering by usage.
 
-1. Find the region and tier that needs more quota and select the **Edit** pencil icon to begin your request.
+    :::image type="content" source="media/search-create-service-portal/usage-filter.png" lightbox="media/search-create-service-portal/usage-filter.png" alt-text="Screenshot of the Usage filter for search services in your current subscription.":::
 
-   :::image type="content" source="media/search-create-service-portal/quota-pencil-edit.png" lightbox="media/search-create-service-portal/quota-pencil-edit.png" alt-text="Screenshot of the My Quotas page with a region at maximum quota.":::
+1. Next to the tier and region that need more quotas, select **Request adjustment** <img src=media/search-create-service-portal/request-adjustment-icon.png alt="Screenshot of the Request Adjustment icon, which is the outline of a pencil." width="14">.
 
-1. In **Quota details**, specify the location, tier, and a new limit for your subscription quota. None of the values can be empty. The new limit must be greater than the current limit. If regional capacity is constrained, your request won't be automatically approved. In this scenario, an incident report is generated on your behalf for investigation and resolution.
+1. In **New Quota Request**, enter a new limit for your subscription quota. The new limit must be greater than your current limit. If regional capacity is constrained, your request won't be automatically approved, and an incident report will be generated on your behalf for investigation and resolution.
 
-1. Submit the request.
+1. Submit your request.
 
-1. Monitor notifications in the Azure portal for status updates on the new limit. Most requests are approved within 24 hours.
+1. Monitor notifications in the Azure portal for updates on the new limit. Most requests are approved within 24 hours.
 
 ## Next steps
 
-After provisioning a service, you can continue in the Azure portal to create your first index.
+Now that you've deployed your search service, continue in the Azure portal to create your first index:
 
 > [!div class="nextstepaction"]
 > [Quickstart: Create an Azure AI Search index in the Azure portal](search-get-started-portal.md)

@@ -8,8 +8,8 @@ ms.author: heidist
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: reference
-ms.date: 01/10/2024
+ms.topic: concept-article
+ms.date: 02/19/2025
 ---
 
 # Terms of Use: Partner data sources

@@ -8,8 +8,8 @@ ms.author: beloh
 ms.service: azure-ai-search
 ms.custom:
   - ignite-2023
-ms.topic: reference
-ms.date: 12/10/2024
+ms.topic: concept-article
+ms.date: 02/20/2025
 ---
 
 # moreLikeThis (preview) in Azure AI Search

@@ -6,11 +6,11 @@ items:
   items:
   - name: What's Azure AI Search?
     href: search-what-is-azure-search.md
-  - name: New in Search
+  - name: New in AI Search
     href: whats-new.md
   - name: Features
     href: search-features-list.md
-  - name: Try search for free
+  - name: Try AI Search for free
     href: search-try-for-free.md
   - name: FAQ
     href: search-faq-frequently-asked-questions.yml