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-manage-rest.md
+12-40Lines changed: 12 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,11 +36,11 @@ All of the Management REST APIs have examples. If a task isn't covered in this a
36
36
37
37
## Prerequisites
38
38
39
-
* An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-search/)
39
+
* An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-search/).
40
40
41
-
*[Postman](https://www.postman.com/downloads/) or another REST client that sends HTTP requests
41
+
*[Postman](https://www.postman.com/downloads/) or another REST client that sends HTTP requests.
42
42
43
-
*[Azure CLI](/cli/azure/install-azure-cli) used to set up a security principle for the client
43
+
*[Azure CLI](/cli/azure/install-azure-cli) used to set up a security principle for the client. You must have owner or administrator permissions to create a security principle.
44
44
45
45
## Create a security principal
46
46
@@ -201,19 +201,9 @@ To use Azure role-based access control (Azure RBAC) for data plane operations, s
201
201
If you want to use Azure RBAC exclusively, [turn off API key authentication](search-security-rbac.md#disable-api-key-authentication) by following up with a second request, this time setting "disableLocalAuth" to "true".
202
202
203
203
```rest
204
-
PUT https://management.azure.com/subscriptions/{{subscriptionId}}/resourcegroups/{{resource-group}}/providers/Microsoft.Search/searchServices/{{search-service-name}}?api-version=2021-04-01-preview
@@ -233,16 +223,9 @@ If you're using [customer-managed encryption](search-security-manage-encryption-
233
223
When you enable this policy, any REST calls that create objects containing sensitive data, such as the connection string within a data source, will fail if an encryption key isn't provided: `"Error creating Data Source: "CannotCreateNonEncryptedResource: The creation of non-encrypted DataSources is not allowed when encryption policy is enforced."`
234
224
235
225
```rest
236
-
PUT https://management.azure.com/subscriptions/{{subscriptionId}}/resourcegroups/{{resource-group}}/providers/Microsoft.Search/searchServices/{{search-service-name}}?api-version=2021-04-01-preview
@@ -258,16 +241,12 @@ PUT https://management.azure.com/subscriptions/{{subscriptionId}}/resourcegroups
258
241
Although [semantic search isn't enabled](semantic-search-overview.md#enable-semantic-search) by default, you could lock down the feature at the service level.
259
242
260
243
```rest
261
-
PUT https://management.azure.com/subscriptions/{{subscriptionId}}/resourcegroups/{{resource-group}}/providers/Microsoft.Search/searchServices/{{search-service-name}}?api-version=2021-04-01-Preview
@@ -277,16 +256,9 @@ PUT https://management.azure.com/subscriptions/{{subscriptionId}}/resourcegroups
277
256
Azure Cognitive Search [writes to external data sources](search-indexer-securing-resources.md) when updating a knowledge store, saving debug session state, or caching enrichments. The following example disables these workloads at the service level.
278
257
279
258
```rest
280
-
PUT https://management.azure.com/subscriptions/{{subscriptionId}}/resourcegroups/{{resource-group}}/providers/Microsoft.Search/searchServices/{{search-service-name}}?api-version=2021-04-01-preview
0 commit comments