You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/search-create-service-portal.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.date: 02/10/2020
13
13
14
14
# Quickstart: Create an Azure Cognitive Search service in the portal
15
15
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.
17
17
18
18
In this article, learn how to create a resource in the [Azure portal](https://portal.azure.com/).
19
19
@@ -41,18 +41,18 @@ If you have more than one subscription, choose one for your search service.
41
41
42
42
## Set a resource group
43
43
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.
45
45
46
46
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.
47
47
48
48

49
49
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.
51
51
52
52

53
53
54
54
> [!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.
56
56
57
57
## Name the service
58
58
@@ -61,10 +61,10 @@ In Instance Details, provide a service name in the **URL** field. The name is pa
61
61
Service name requirements:
62
62
63
63
* 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
68
68
69
69
> [!TIP]
70
70
> 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
75
75
76
76
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).
77
77
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*.
79
79
80
80
> [!Note]
81
81
> 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
86
86
87
87
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.
88
88
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.
90
90
91
91
## Create your service
92
92
93
93
After you've provided the necessary inputs, go ahead and create the service.
94
94
95
95

96
96
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.
98
98
99
99

0 commit comments