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/azure-cache-for-redis/cache-azure-active-directory-for-authentication.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,8 @@ To use the ACL integration, your client application must assume the identity of
58
58
> [!IMPORTANT]
59
59
> Once the enable operation is complete, the nodes in your cache instance reboots to load the new configuration. We recommend performing this operation during your maintenance window or outside your peak business hours. The operation can take up to 30 minutes.
60
60
61
+
For information on using Microsoft Entra ID with Azure CLI, see the [references pages for identity](/cli/azure/redis/identity).
62
+
61
63
## Using data access configuration with your cache
62
64
63
65
If you would like to use a custom access policy instead of Redis Data Owner, go to the **Data Access Configuration** on the Resource menu. For more information, see [Configure a custom data access policy for your application](cache-configure-role-based-access-control.md#configure-a-custom-data-access-policy-for-your-application).
@@ -128,6 +130,8 @@ The following table includes links to code samples, which demonstrate how to con
128
130
129
131
- When calling the Redis server `AUTH` command periodically, consider adding a jitter so that the `AUTH` commands are staggered, and your Redis server doesn't receive lot of `AUTH` commands at the same time.
130
132
131
-
## Next steps
133
+
## Related content
132
134
133
135
-[Configure role-based access control with Data Access Policy](cache-configure-role-based-access-control.md)
136
+
-[Reference pages for identity](/cli/azure/redis/identity)
Copy file name to clipboardExpand all lines: articles/dns/dns-private-resolver-get-started-portal.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: In this quickstart, you create and test a private DNS resolver in A
4
4
services: dns
5
5
author: greg-lindsay
6
6
ms.author: greglin
7
-
ms.date: 02/28/2024
7
+
ms.date: 04/05/2024
8
8
ms.topic: quickstart
9
9
ms.service: dns
10
10
ms.custom: mode-ui, ignite-2022
@@ -155,6 +155,9 @@ Add or remove specific rules your DNS forwarding ruleset as desired, such as:
155
155
- A rule to resolve an on-premises zone: internal.contoso.com.
156
156
- A wildcard rule to forward unmatched DNS queries to a protective DNS service.
157
157
158
+
> [!IMPORTANT]
159
+
> The rules shown in this quickstart are examples of rules that can be used for specific scenarios. None of the fowarding rules described in this article are required. Be careful to test your forwarding rules and ensure that the rules don't cause DNS resolution issues.
160
+
158
161
### Delete a rule from the forwarding ruleset
159
162
160
163
Individual rules can be deleted or disabled. In this example, a rule is deleted.
Create a forwarding rule for a ruleset to one or more target DNS servers. You must specify the fully qualified domain name (FQDN) with a trailing dot. The **New-AzDnsResolverTargetDnsServerObject** cmdlet sets the default port as 53, but you can also specify a unique port.
234
236
235
237
```Azure PowerShell
@@ -247,6 +249,9 @@ In this example:
247
249
- 192.168.1.2 and 192.168.1.3 are on-premises DNS servers.
248
250
- 10.5.5.5 is a protective DNS service.
249
251
252
+
> [!IMPORTANT]
253
+
> The rules shown in this quickstart are examples of rules that can be used for specific scenarios. None of the fowarding rules described in this article are required. Be careful to test your forwarding rules and ensure that the rules don't cause DNS resolution issues.
254
+
250
255
## Test the private resolver
251
256
252
257
You should now be able to send DNS traffic to your DNS resolver and resolve records based on your forwarding rulesets, including:
Copy file name to clipboardExpand all lines: articles/search/cognitive-search-skill-ocr.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,8 @@ The **Optical character recognition (OCR)** skill recognizes printed and handwri
19
19
An OCR skill uses the machine learning models provided by [Azure AI Vision](../ai-services/computer-vision/overview.md) API [v3.2](https://westus.dev.cognitive.microsoft.com/docs/services/computer-vision-v3-2/operations/5d986960601faab4bf452005) in Azure AI services. The **OCR** skill maps to the following functionality:
20
20
21
21
+ For the languages listed under [Azure AI Vision language support](../ai-services/computer-vision/language-support.md#optical-character-recognition-ocr), the [Read API](../ai-services/computer-vision/overview-ocr.md) is used.
22
-
+ For Greek and Serbian Cyrillic, the [legacy OCR](https://westus.dev.cognitive.microsoft.com/docs/services/computer-vision-v3-2/operations/56f91f2e778daf14a499f20d) API is used.
22
+
23
+
+ For Greek and Serbian Cyrillic, the legacy [OCR in version 3.2](https://github.com/Azure/azure-rest-api-specs/tree/master/specification/cognitiveservices/data-plane/ComputerVision/stable/v3.2) API is used.
23
24
24
25
The **OCR** skill extracts text from image files. Supported file formats include:
25
26
@@ -41,7 +42,7 @@ Parameters are case-sensitive.
41
42
42
43
| Parameter name | Description |
43
44
|--------------------|-------------|
44
-
|`detectOrientation`| Detects image orientation. Valid values are `true` or `false`. </p>This parameter only applies if the [legacy OCR](https://westus.dev.cognitive.microsoft.com/docs/services/computer-vision-v3-2/operations/56f91f2e778daf14a499f20d) API is used. |
45
+
|`detectOrientation`| Detects image orientation. Valid values are `true` or `false`. </p>This parameter only applies if the [legacy OCR version 3.2](https://github.com/Azure/azure-rest-api-specs/tree/master/specification/cognitiveservices/data-plane/ComputerVision/stable/v3.2) API is used. |
45
46
|`defaultLanguageCode`| Language code of the input text. Supported languages include all of the [generally available languages](../ai-services/computer-vision/language-support.md#analyze-image) of Azure AI Vision. You can also specify `unk` (Unknown). </p>If the language code is unspecified or null, the language is set to English. If the language is explicitly set to `unk`, all languages found are auto-detected and returned.|
46
47
|`lineEnding`| The value to use as a line separator. Possible values: "Space", "CarriageReturn", "LineFeed". The default is "Space". |
47
48
@@ -210,8 +211,6 @@ The above skillset example assumes that a normalized-images field exists. To gen
210
211
}
211
212
```
212
213
213
-
214
-
215
214
## See also
216
215
217
216
+[What is optical character recognition](../ai-services/computer-vision/overview-ocr.md)
Copy file name to clipboardExpand all lines: articles/search/search-indexer-howto-access-private.md
+18-9Lines changed: 18 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.service: cognitive-search
10
10
ms.custom:
11
11
- ignite-2023
12
12
ms.topic: how-to
13
-
ms.date: 02/22/2024
13
+
ms.date: 04/03/2024
14
14
---
15
15
16
16
# Make outbound connections through a shared private link
@@ -28,12 +28,15 @@ Shared private link is a premium feature that's billed by usage. When you set up
28
28
29
29
Azure AI Search makes outbound calls to other Azure PaaS resources in the following scenarios:
30
30
31
-
+ Indexer connection requests to supported data sources
32
-
+ Indexer (skillset) connections to Azure Storage for caching enrichments or writing to a knowledge store
31
+
+ Indexer or search engine connects to Azure OpenAI for text-to-vector embeddings
32
+
+ Indexer connects to supported data sources
33
+
+ Indexer (skillset) connections to Azure Storage for caching enrichments, debug session sate, or writing to a knowledge store
33
34
+ Encryption key requests to Azure Key Vault
34
35
+ Custom skill requests to Azure Functions or similar resource
35
36
36
-
In service-to-service communications, Azure AI Search typically sends a request over a public internet connection. However, if your data, key vault, or function should be accessed through a [private endpoint](../private-link/private-endpoint-overview.md), you must create a *shared private link*.
37
+
Shared private links only work for Azure-to-Azure connections. If you're connecting to OpenAI or another external model, the connection must be over the public internet.
38
+
39
+
Shared private links are for operations and data accessed through a [private endpoint](../private-link/private-endpoint-overview.md) for Azure resources or clients that run in an Azure virtual network.
37
40
38
41
A shared private link is:
39
42
@@ -51,21 +54,24 @@ There are two scenarios for using [Azure Private Link](../private-link/private-l
51
54
52
55
+ Scenario two: [configure search for a private *inbound* connection](service-create-private-endpoint.md) from clients that run in a virtual network.
53
56
57
+
Scenario one is covered in this article.
58
+
54
59
While both scenarios have a dependency on Azure Private Link, they are independent. You can create a shared private link without having to configure your own search service for a private endpoint.
55
60
56
61
### Limitations
57
62
58
63
When evaluating shared private links for your scenario, remember these constraints.
59
64
60
-
+ Several of the resource types used in a shared private link are in preview. If you're connecting to a preview resource (Azure Database for MySQL, Azure Functions, or Azure SQL Managed Instance), use a preview version of the Management REST API to create the shared private link. These versions include `2020-08-01-preview` or `2021-04-01-preview`.
65
+
+ Several of the resource types used in a shared private link are in preview. If you're connecting to a preview resource (Azure Database for MySQL, Azure Functions, or Azure SQL Managed Instance), use a preview version of the Management REST API to create the shared private link. These versions include `2020-08-01-preview`, `2021-04-01-preview`, and `2024-03-01-preview`.
61
66
62
67
+ Indexer execution must use the private execution environment that's specific to your search service. Private endpoint connections aren't supported from the multitenant environment. The configuration setting for this requirement is covered in this article.
63
68
64
69
## Prerequisites
65
70
66
71
+ An Azure AI Search at the Basic tier or higher. If you're using [AI enrichment](cognitive-search-concept-intro.md) and skillsets, the tier must be Standard 2 (S2) or higher. See [Service limits](search-limits-quotas-capacity.md#shared-private-link-resource-limits) for details.
67
72
68
-
+ An Azure PaaS resource from the following list of supported resource types, configured to run in a virtual network.
73
+
+ An Azure PaaS resource from the following list of [supported resource types](#supported-resource-types), configured to run in a virtual network.
74
+
69
75
70
76
+ Permissions on both Azure AI Search and the data source:
71
77
@@ -275,11 +281,14 @@ A `202 Accepted` response is returned on success. The process of creating an out
275
281
276
282
## 2 - Approve the private endpoint connection
277
283
278
-
Approval of the private endpoint connection is granted on the Azure PaaS side. If the service consumer has a role assignment on the service provider resource, the approval will be automatic. Otherwise, manual approval is required. For details, see [Manage Azure private endpoints](/azure/private-link/manage-private-endpoint).
284
+
Approval of the private endpoint connection is granted on the Azure PaaS side. Explicit approval by the resource owner is required. The following steps cover approval using the Azure portal, but here are some links to approve the connection programmatically from the Azure PaaS side:
285
+
286
+
+ On Azure Storage, use [Private Endpoint Connections - Put](/rest/api/storagerp/private-endpoint-connections/put)
287
+
+ On Azure Cosmos DB, use [Private Endpoint Connections - Create Or Update](/rest/api/cosmos-db-resource-provider/private-endpoint-connections/create-or-update)
279
288
280
-
This section assumes manual approval and the portal for this step, but you can also use the REST APIs of the Azure PaaS resource. [Private Endpoint Connections (Storage Resource Provider)](/rest/api/storagerp/privateendpointconnections) and [Private Endpoint Connections (Cosmos DB Resource Provider)](/rest/api/cosmos-db-resource-provider/2023-03-15/private-endpoint-connections) are two examples.
289
+
Using the Azure portal, perform the following steps:
281
290
282
-
1.In the Azure portal, open the **Networking** page of the Azure PaaS resource.[text](https://ms.portal.azure.com/#blade%2FHubsExtension%2FResourceMenuBlade%2Fid%2F%2Fsubscriptions%2Fa5b1ca8b-bab3-4c26-aebe-4cf7ec4791a0%2FresourceGroups%2Ftest-private-endpoint%2Fproviders%2FMicrosoft.Network%2FprivateEndpoints%2Ftest-private-endpoint)
291
+
1.Open the **Networking** page of the Azure PaaS resource.[text](https://ms.portal.azure.com/#blade%2FHubsExtension%2FResourceMenuBlade%2Fid%2F%2Fsubscriptions%2Fa5b1ca8b-bab3-4c26-aebe-4cf7ec4791a0%2FresourceGroups%2Ftest-private-endpoint%2Fproviders%2FMicrosoft.Network%2FprivateEndpoints%2Ftest-private-endpoint)
283
292
284
293
1. Find the section that lists the private endpoint connections. The following example is for a storage account.
Copy file name to clipboardExpand all lines: articles/search/search-manage-azure-cli.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.custom:
11
11
- devx-track-azurecli
12
12
- ignite-2023
13
13
ms.topic: how-to
14
-
ms.date: 02/21/2024
14
+
ms.date: 04/05/2024
15
15
---
16
16
17
17
# Manage your Azure AI Search service with the Azure CLI
@@ -21,10 +21,12 @@ ms.date: 02/21/2024
21
21
> *[Azure CLI](search-manage-azure-cli.md)
22
22
> *[REST API](search-manage-rest.md)
23
23
24
-
You can run Azure CLI commands and scripts on Windows, macOS, Linux, or in [Azure Cloud Shell](../cloud-shell/overview.md) to create and configure Azure AI Search. The [**az search**](/cli/azure/search) module extends the [Azure CLI](/cli/) with full parity to the [Search Management REST APIs](/rest/api/searchmanagement) and the ability to perform the following tasks:
24
+
You can run Azure CLI commands and scripts on Windows, macOS, Linux, or in Azure Cloud Shell to create and configure Azure AI Search.
25
+
26
+
Use the [**az search module**](/cli/azure/search) to perform the following tasks:
25
27
26
28
> [!div class="checklist"]
27
-
> *[List search services in a subscription](#list-search-services)
29
+
> *[List search services in a subscription](#list-services-in-a-subscription)
28
30
> *[Return service information](#get-search-service-information)
29
31
> *[Create or delete a service](#create-or-delete-a-service)
30
32
> *[Create a service with a private endpoint](#create-a-service-with-a-private-endpoint)
@@ -45,7 +47,7 @@ Preview administration features are typically not available in the **az search**
45
47
46
48
Azure CLI versions are [listed on GitHub](https://github.com/Azure/azure-cli/releases).
47
49
48
-
<aname="list-search-services"></a>
50
+
The [**az search**](/cli/azure/search) module extends the [Azure CLI](/cli/) with full parity to the stable versions of the [Search Management REST APIs](/rest/api/searchmanagement).
Copy file name to clipboardExpand all lines: articles/search/search-manage-powershell.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: PowerShell scripts using `Az.Search` module
2
+
title: PowerShell scripts using Azure Search PowerShell module
3
3
titleSuffix: Azure AI Search
4
4
description: Create and configure an Azure AI Search service with PowerShell. You can scale a service up or down, manage admin and query api-keys, and query for system information.
5
5
@@ -9,7 +9,7 @@ ms.author: heidist
9
9
ms.service: cognitive-search
10
10
ms.devlang: powershell
11
11
ms.topic: how-to
12
-
ms.date: 02/21/2024
12
+
ms.date: 04/05/2024
13
13
ms.custom:
14
14
- devx-track-azurepowershell
15
15
- ignite-2023
@@ -22,7 +22,9 @@ ms.custom:
22
22
> *[Azure CLI](search-manage-azure-cli.md)
23
23
> *[REST API](search-manage-rest.md)
24
24
25
-
You can run PowerShell cmdlets and scripts on Windows, Linux, or in [Azure Cloud Shell](../cloud-shell/overview.md) to create and configure Azure AI Search. The **Az.Search** module extends [Azure PowerShell](/powershell/) with full parity to the [Search Management REST APIs](/rest/api/searchmanagement) and the ability to perform the following tasks:
25
+
You can run PowerShell cmdlets and scripts on Windows, Linux, or in Azure Cloud Shell to create and configure Azure AI Search.
26
+
27
+
Use the [**Az.Search** module](/powershell/module/az.search/) to perform the following tasks:
26
28
27
29
> [!div class="checklist"]
28
30
> *[List search services in a subscription](#list-search-services)
@@ -42,6 +44,8 @@ You can't use tools or APIs to transfer content, such as an index, from one serv
42
44
43
45
Preview administration features are typically not available in the **Az.Search** module. If you want to use a preview feature, [use the Management REST API](search-manage-rest.md) and a preview API version.
44
46
47
+
The [**Az.Search** module](/powershell/module/az.search/) extends [Azure PowerShell](/powershell/) with full parity to the stable versions of the [Search Management REST APIs](/rest/api/searchmanagement).
0 commit comments