Skip to content

Commit 19efe67

Browse files
authored
Merge pull request #104204 from tchristiani/freshness-pass-12FEB20
freshness-pass-readability-12FEB20
2 parents bdd824a + 1fada0e commit 19efe67

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

articles/search/search-create-service-portal.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 02/10/2020
1313

1414
# Quickstart: Create an Azure Cognitive Search service in the portal
1515

16-
Azure Cognitive Search is a standalone resource used to plug in a search experience in custom apps. Although Azure Cognitive Search integrates easily with other Azure services, you can also use it as a standalone component, or integrate it with apps on network servers, or with software running on other cloud platforms.
16+
Azure Cognitive Search is a standalone resource used to plug a search experience into custom apps. Azure Cognitive Search integrates easily with other Azure services, with apps on network servers, or with software running on other cloud platforms.
1717

1818
In this article, learn how to create a resource in the [Azure portal](https://portal.azure.com/).
1919

@@ -41,18 +41,18 @@ If you have more than one subscription, choose one for your search service.
4141

4242
## Set a resource group
4343

44-
A resource group is required and is useful for managing resources all-up, including costs. A resource group can consist of one service, or multiple services used together. For example, if you are using Azure Cognitive Search to index an Azure Cosmos DB database, you could make both services part of the same resource group for management purposes.
44+
A resource group is a container that holds related resources for your Azure solution. It is required for the search service. It is also useful for managing resources all-up, including costs. A resource group can consist of one service, or multiple services used together. For example, if you are using Azure Cognitive Search to index an Azure Cosmos DB database, you could make both services part of the same resource group for management purposes.
4545

4646
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 Cognitive Search resource.
4747

4848
![Create a new resource group](./media/search-create-service-portal/new-resource-group.png "Create a new resource group")
4949

50-
Over time, you can track current and projected costs all-up (as shown in the screenshot) or scroll down to view charges for individual resources. The following screenshot shows the kind of cost information you can eventually expect to see when you combine multiple resources into one group.
50+
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.
5151

5252
![Manage costs at the resource group level](./media/search-create-service-portal/resource-group-cost-management.png "Manage costs at the resource group level")
5353

5454
> [!TIP]
55-
> Resource groups simplify cleanup because deleting a 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.
55+
> Resource groups simplify cleanup because deleting a group deletes all of 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.
5656
5757
## Name the service
5858

@@ -61,10 +61,10 @@ In Instance Details, provide a service name in the **URL** field. The name is pa
6161
Service name requirements:
6262

6363
* It must be unique within the search.windows.net namespace
64-
* 2 and 60 characters in length
65-
* Use lowercase letters, digits, or dashes ("-")
66-
* Avoid dashes ("-") in the first 2 characters or as the last single character
67-
* No consecutive dashes ("--") anywhere
64+
* It must be between 2 and 60 characters in length
65+
* You must use lowercase letters, digits, or dashes ("-")
66+
* Do not use dashes ("-") in the first 2 characters or as the last single character
67+
* You may not use consecutive dashes ("--") anywhere
6868

6969
> [!TIP]
7070
> 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 Cognitive 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.
@@ -75,7 +75,7 @@ As an Azure service, Azure Cognitive Search can be hosted in datacenters around
7575

7676
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 Cognitive Search service in the same region avoids bandwidth charges (there are no charges for outbound data when services are in the same region).
7777

78-
Additionally, if you are using AI enrichment, create your service in the same region as Cognitive Services. *Co-location of Azure Cognitive Search and Cognitive Services in the same region is a requirement for AI enrichment*.
78+
If you are using AI enrichment, create your search service in the same region as Cognitive Services. *Co-location of Azure Cognitive Search and Cognitive Services in the same region is a requirement for AI enrichment*.
7979

8080
> [!Note]
8181
> 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.
@@ -86,15 +86,15 @@ Additionally, if you are using AI enrichment, create your service in the same re
8686

8787
Basic and Standard are the most common choices for production workloads, but most customers start with the Free service. Key differences among tiers is partition size and speed, and limits on the number of objects you can create.
8888

89-
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.
89+
Remember, a pricing tier cannot be changed once the service is created. If you need a higher or lower tier, you will have to re-create the service.
9090

9191
## Create your service
9292

9393
After you've provided the necessary inputs, go ahead and create the service.
9494

9595
![Review and create the service](./media/search-create-service-portal/new-service3.png "Review and create the service")
9696

97-
Your service is deployed within minutes, which you can monitor through Azure notifications. Consider pinning the service to your dashboard for easy access in the future.
97+
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.
9898

9999
![Monitor and pin the service](./media/search-create-service-portal/monitor-notifications.png "Monitor and pin the service")
100100

0 commit comments

Comments
 (0)