Merge pull request #84631 from HeidiSteen/heidist-quick

Azure Search: refresh service provisioning doc

Author: ktoliver

articles/search/media/search-create-service-portal/new-service3.png

@@ -6,7 +6,7 @@ author: HeidiSteen
 services: search
 ms.service: search
 ms.topic: quickstart
-ms.date: 07/09/2019
+ms.date: 08/09/2019
 ms.author: heidist
 ms.custom: seodec2018
 ---
@@ -34,11 +34,26 @@ Alternatively, [activate MSDN subscriber benefits](https://azure.microsoft.com/p
 
 ![Navigate to an Azure Search resource](./media/search-create-service-portal/find-search3.png "Navigation path to Azure Search")
 
-## Name the service and URL endpoint
+## Select a subscription
+
+If you have more than one subscription, choose one that also has data or file storage services. Azure Search can autodetect Azure Table and Blob storage, SQL Database, and Azure Cosmos DB for indexing via [*indexers*](search-indexer-overview.md), but only for services under the same subscription.
+
+## Select a resource group
+
+A resource group is required and is useful for managing resources all-up, including cost management. A resource group can consist of one service, or multiple services used together. For example, if you are using Azure Search to index an Azure Cosmos DB database, you could make both services part of the same resource group for management purposes. 
 
-A service name is part of the URL endpoint against which API calls are issued: `https://your-service-name.search.windows.net`. Enter your service name in the **URL** field.
+If you aren't combining resources into a single group, or if existing resource groups are filled with resources used in unrelated solutions, create a new resource group just for your Azure Search resource. 
 
-For example, if you want the endpoint to be `https://my-app-name-01.search.windows.net`, you would enter `my-app-name-01`.
+As you use the service, you can track current and projected costs all-up (as shown in the screenshot) or scroll down to view charges for individual resources.
+
+![Manage costs at the resource group level](./media/search-create-service-portal/resource-group-cost-management.png "Manage costs at the resource group level")
+
+> [!TIP]
+> Deleting a resource group also deletes the services within it. For prototype projects utilizing multiple services, putting all of them in the same resource group makes cleanup easier after the project is over.
+
+## Name the service and URL endpoint
+
+In Instance Details, provide a service name in the **URL** field. The name is part of the URL 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`.
 
 Service name requirements:
 
@@ -48,26 +63,16 @@ Service name requirements:
 * Avoid dashes ("-") in the first 2 characters or as the last single character
 * No consecutive dashes ("--") anywhere
 
-## Select a subscription
-
-If you have more than one subscription, choose one that also has data or file storage services. Azure Search can autodetect Azure Table and Blob storage, SQL Database, and Azure Cosmos DB for indexing via [*indexers*](search-indexer-overview.md), but only for services in the same subscription.
-
-## Select a resource group
-
-A resource group is a collection of Azure services and resources used together. For example, if you are using Azure Search to index a SQL database, then both services should be part of the same resource group.
-
-If you aren't combining resources into a single group, or if existing resource groups are filled with resources used in unrelated solutions, create a new resource group just for your Azure Search resource.
-
 > [!TIP]
-> Deleting a resource group also deletes the services within it. For prototype projects utilizing multiple services, putting all of them in the same resource group makes cleanup easier after the project is over.
+> If you think you'll be using multiple services, we recommend including the region (or location) in the service name as a naming convention. Services within the same region can exchange data at no charge, so if Azure Search is in West US, and you have other services also in West US, a name like `mysearchservice-westus` can save you a trip to the properties page when deciding how to combine or attach resources.
 
 ## Select a location
 
 As an Azure service, Azure Search can be hosted in datacenters around the world. The list of supported regions can be found in the [pricing page](https://azure.microsoft.com/pricing/details/search/). 
 
-If you are indexing data provided by another Azure service (Azure storage, Azure Cosmos DB, Azure SQL Database), we recommend creating your Azure Search service in the same region to avoid bandwidth charges. There are no charges for outbound data when services are in the same region.
+You can minimize or avoid bandwidth charges by choosing the same location for multiple services. For example, if you are indexing data provided by another Azure service (Azure storage, Azure Cosmos DB, Azure SQL Database), creating your Azure Search service in the same region avoids bandwidth charges (there are no charges for outbound data when services are in the same region).
 
-If you are using cognitive search AI enrichments, create your service in the same region as your Cognitive Services resource. *Co-location of Azure Search and Cognitive Services in the same region is a requirement for AI enrichment*.
+Additionally, if you are using cognitive search AI enrichments, create your service in the same region as your Cognitive Services resource. *Co-location of Azure Search and Cognitive Services in the same region is a requirement for AI enrichment*.
 
 > [!Note]
 > Central India is currently unavailable for new services. For services already in Central India, you can scale up with no restrictions, and your service is fully supported in that region. The restriction on this region is temporary and limited to new services only. We will remove this note when the restriction no longer applies.
@@ -76,13 +81,13 @@ If you are using cognitive search AI enrichments, create your service in the sam
 
 [Azure Search is currently offered in multiple pricing tiers](https://azure.microsoft.com/pricing/details/search/): Free, Basic, or Standard. Each tier has its own [capacity and limits](search-limits-quotas-capacity.md). See [Choose a pricing tier or SKU](search-sku-tier.md) for guidance.
 
-Standard is usually chosen for production workloads, but most customers start with the Free service.
+Basic and Standard are the most common choices for production workloads, but most customers start with the Free service.
 
-A pricing tier cannot be changed once the service is created. If you need a higher or lower tier later, you have to re-create the service.
+Remember that a pricing tier cannot be changed once the service is created. If you need a higher or lower tier later, you have to re-create the service.
 
 ## Create your service
 
-Enter the necessary inputs to create the service. 
+After you've provided the necessary inputs, go ahead and create the service. 
 
 ![Review and create the service](./media/search-create-service-portal/new-service3.png "Review and create the service")
 
@@ -92,7 +97,7 @@ Your service is deployed within minutes, which you can monitor through Azure not
 
 ## Get a key and URL endpoint
 
-Unless you are using the portal, accessing your new service requires that you provide the URL endpoint and an authentication api-key.
+Unless you are using the portal, programmatic access to your new service requires that you provide the URL endpoint and an authentication api-key.
 
 1. In the service overview page, locate and copy the URL endpoint on the right side of the page.
 
@@ -135,7 +140,7 @@ Although most customers use just one service, service redundancy might be necess
 * For globally deployed applications, you might require an instance of Azure Search in multiple regions to minimize latency of your application’s international traffic.
 
 > [!NOTE]
-> In Azure Search, you cannot segregate indexing and querying workloads; thus, you would never create multiple services for segregated workloads. An index is always queried on the service in which it was created (you cannot create an index in one service and copy it to another).
+> In Azure Search, you cannot 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 cannot create an index in one service and copy it to another).
 
 A second service is not required for high availability. High availability for queries is achieved when you use 2 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/).