Skip to content

Commit 03aa62e

Browse files
HeidiSteenHeidiSteen
committed
port PR 7150
1 parent 86cded8 commit 03aa62e

7 files changed

+160
-82
lines changed

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

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: 'Create a Search Service in the Azure Portal'
33
titleSuffix: Azure AI Search
4-
description: Learn how to set up an Azure AI Search resource in the Azure portal. Choose resource groups, regions, and a pricing tier.
4+
description: Learn how to set up an Azure AI Search service in the Azure portal. Choose a resource group, region, and pricing tier.
55
manager: nitinme
66
author: haileytap
77
ms.author: haileytapia
88
ms.service: azure-ai-search
99
ms.update-cycle: 180-days
1010
ms.topic: how-to
11-
ms.date: 08/08/2025
11+
ms.date: 09/25/2025
1212
ms.custom:
1313
- references_regions
1414
- build-2024
@@ -41,7 +41,7 @@ Some properties are fixed for the lifetime of the search service. Before you cre
4141
| [Name](#name-your-service) | Becomes part of the URL endpoint. The name must be unique and follow naming rules. |
4242
| [Region](search-region-support.md) | Determines data residency and availability of certain features. For example, semantic ranker and Azure AI integration have region requirements. Choose a region that supports the features you need. |
4343
| [Tier](search-sku-tier.md) | Determines infrastructure, service limits, and billing. Some features aren't available on lower or specialized tiers. After you create your service, you can [switch between Basic and Standard (S1, S2, and S3) tiers](search-capacity-planning.md#change-your-pricing-tier). |
44-
44+
| [Compute type](search-security-overview.md#data-in-use) | Determines virtualization and security model. You can choose between standard VMs (recommended) and confidential VMs, which are intended for select workloads requiring data-in-use privacy and isolation. |
4545
## Subscribe to Azure
4646

4747
Azure AI Search requires a free or Standard Azure subscription.
@@ -141,6 +141,16 @@ The Basic and Standard tiers are the most common for production workloads, but m
141141
> [!NOTE]
142142
> Services created after April 3, 2024 have larger partitions and higher vector quotas at every billable tier.
143143
144+
## Choose a compute type
145+
146+
The compute type determines the virtualization and security model used to deploy your search service. There are two compute types:
147+
148+
+ **Default** (base cost) deploys your search service on standard Azure infrastructure, encrypting data at rest and in transit but not in use. Recommended for most search workloads.
149+
150+
+ **Confidential** (10% surcharge) uses [Azure confidential computing](/azure/confidential-computing/use-cases-scenarios) to isolate processing in a hardware-based trusted execution environment, protecting unencrypted data in use from unauthorized access. Recommended only if you have advanced privacy, compliance, or regulatory requirements.
151+
152+
Confidential computing has limited regional availability, disables or restricts certain features, and increases the cost of running your search service. For a detailed comparison of both compute types, see [Data in use](search-security-overview.md#data-in-use).
153+
144154
## Create your service
145155

146156
After providing the necessary inputs, create your search service.

‎articles/search/search-manage-azure-cli.md‎

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.custom:
1010
- devx-track-azurecli
1111
- ignite-2023
1212
ms.topic: how-to
13-
ms.date: 08/01/2025
13+
ms.date: 09/25/2025
1414
ms.update-cycle: 365-days
1515
---
1616

@@ -25,6 +25,7 @@ Use the [**az search module**](/cli/azure/search) to perform the following tasks
2525
> * [Return service information](#get-search-service-information)
2626
> * [Create or delete a service](#create-or-delete-a-service)
2727
> * [Create a service with a private endpoint](#create-a-service-with-a-private-endpoint)
28+
> * [Create a service with confidential computing](#create-a-service-with-confidential-computing)
2829
> * [Regenerate admin API-keys](#regenerate-admin-keys)
2930
> * [Create or delete query api-keys](#create-or-delete-query-keys)
3031
> * [Scale up or down with replicas and partitions](#scale-replicas-and-partitions)
@@ -306,6 +307,23 @@ az search private-endpoint-connection delete \
306307
--resource-group <search-service-resource-group-name>
307308
```
308309

310+
## Create a service with confidential computing
311+
312+
[Confidential computing](search-security-overview.md#data-in-use) is an optional compute type for data-in-use protection. When configured, your search service is deployed on confidential VMs (DCasv5 or DCesv5) instead of standard VMs. This compute type also incurs a 10% surcharge for billable tiers. For more information, see the [pricing page](https://azure.microsoft.com/pricing/details/search/).
313+
314+
For daily usage, confidential computing isn't necessary. We only recommend this compute type for stringent regulatory, compliance, or security requirements. For more information, see [Confidential computing use cases](/azure/confidential-computing/use-cases-scenarios).
315+
316+
The compute type is fixed for the lifetime of your search service. To permanently configure confidential computing, set the `compute-type` property to `confidential` on a new service.
317+
318+
```azurecli-interactive
319+
az search service create \
320+
--name <search-service-name> \
321+
--resource-group <search-service-resource-group-name> \
322+
--location <search-service-region> \
323+
--sku basic \
324+
--compute-type confidential
325+
```
326+
309327
## Regenerate admin keys
310328

311329
To roll over admin [API keys](search-security-api-keys.md), use [**az search admin-key renew**](/cli/azure/search/admin-key#az-search-admin-key-renew). Two admin keys are created with each service for authenticated access. Keys are required on every request. Both admin keys are functionally equivalent, granting full write access to a search service with the ability to retrieve any information, or create and delete any object. Two keys exist so that you can use one while replacing the other.

‎articles/search/search-manage-rest.md‎

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: azure-ai-search
88
ms.custom:
99
- ignite-2023
1010
ms.topic: how-to
11-
ms.date: 08/01/2025
11+
ms.date: 09/25/2025
1212
ms.update-cycle: 365-days
1313
---
1414

@@ -22,6 +22,8 @@ The Management REST API is available in stable and preview versions. Be sure to
2222
> * [Create or update a service](#create-or-update-a-service)
2323
> * [Upgrade a service](#upgrade-a-service)
2424
> * [Change pricing tiers](#change-pricing-tiers)
25+
> * [Configure role-based access control for data plane](#configure-role-based-access-for-data-plane)
26+
> * [Configure confidential computing](#configure-confidential-computing)
2527
> * [Enable Azure role-based access control for data plane](#enable-rbac)
2628
> * [Enforce a customer-managed key policy](#enforce-cmk)
2729
> * [Disable semantic ranker](#disable-semantic-ranker)
@@ -239,6 +241,32 @@ PATCH https://management.azure.com/subscriptions/{{subscription-id}}/resourcegro
239241
}
240242
```
241243

244+
## Configure confidential computing
245+
246+
[Confidential computing](search-security-overview.md#data-in-use) is an optional compute type for data-in-use protection. When configured, your search service is deployed on confidential VMs (DCasv5 or DCesv5) instead of standard VMs. This compute type also incurs a 10% surcharge for billable tiers. For more information, see the [pricing page](https://azure.microsoft.com/pricing/details/search/).
247+
248+
For daily usage, confidential computing isn't necessary. We only recommend this compute type for stringent regulatory, compliance, or security requirements. For more information, see [Confidential computing use cases](/azure/confidential-computing/use-cases-scenarios).
249+
250+
The compute type is fixed for the lifetime of your search service. To permanently configure confidential computing, set the `computeType` property to `confidential` on a new service.
251+
252+
```http
253+
### Configure confidential computing
254+
@resource-group = PUT-YOUR-RESOURCE-GROUP-NAME-HERE
255+
@search-service = PUT-YOUR-SEARCH-SERVICE-NAME-HERE
256+
PUT https://management.azure.com/subscriptions/{{subscription-id}}/resourcegroups/{{resource-group}}/providers/Microsoft.Search/searchServices/{{search-service}}?api-version=2025-05-01 HTTP/1.1
257+
Content-type: application/json
258+
Authorization: Bearer {{token}}
259+
{
260+
"location": "{{region}}",
261+
"sku": {
262+
"name": "basic"
263+
},
264+
"properties": {
265+
"computeType": "confidential"
266+
}
267+
}
268+
```
269+
242270
<a name="enforce-cmk"></a>
243271

244272
## Enforce a customer-managed key policy

‎articles/search/search-region-support.md‎

Lines changed: 70 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Shows supported regions and feature availability across regions for
55
author: haileytap
66
ms.author: haileytapia
77
manager: nitinme
8-
ms.date: 08/08/2025
8+
ms.date: 09/25/2025
99
ms.service: azure-ai-search
1010
ms.topic: conceptual
1111
ms.custom:
@@ -26,6 +26,7 @@ When you create an Azure AI Search service, your region selection might depend o
2626
| [AI enrichment](cognitive-search-concept-intro.md) | Refers to [built-in skills](cognitive-search-predefined-skills.md) that make internal calls to Azure AI for enrichment and transformation during indexing. Integration requires that Azure AI Search coexists with an [Azure AI services multi-service account](/azure/ai-services/multi-service-resource#azure-ai-services-resource-for-azure-ai-search-skills) in the same physical region. You can bypass region requirements by using [identity-based connections](cognitive-search-attach-cognitive-services.md#bill-through-a-keyless-connection), currently in public preview. | Regional support is noted in this article. |
2727
| [Availability zones](/azure/reliability/reliability-ai-search#availability-zone-support) | Divides a region's data centers into distinct physical location groups, providing high availability within the same geo. | Regional support is noted in this article. |
2828
| [Agentic retrieval](search-agentic-retrieval-concept.md) | Takes a dependency on semantic ranker, which is another premium feature. | Regional support is noted in this article. |
29+
| [Confidential computing](search-security-overview.md#data-in-use) | Deploys your search service on confidential VMs to process data in a hardware-based trusted execution environment.<p>Confidential computing disables or restricts certain features, including agentic retrieval, semantic ranker, query rewrite, and skillset execution. | Regional support is noted in this article. |
2930
| [Semantic ranker](semantic-search-overview.md) | Takes a dependency on Microsoft-hosted models in specific regions. | Regional support is noted in this article. |
3031
| [Query rewrite](semantic-how-to-query-rewrite.md) | Takes a dependency on Microsoft-hosted models in specific regions. | Regional support is noted in this article. |
3132
| [Extra capacity](search-limits-quotas-capacity.md#service-limits) | Higher-capacity partitions became available in select regions starting in April 2024, with a second wave following in May 2024. Currently, there are just a few regions that *don't* offer higher-capacity partitions.<p>If you have an older search service in a supported region, check if you can [upgrade your service](search-how-to-upgrade.md). Otherwise, create a new search service to benefit from more capacity at the same billing rate. | Regional support is noted in the footnotes of this article. |
@@ -38,96 +39,96 @@ You can create an Azure AI Search service in any of the following Azure public r
3839

3940
### Americas
4041

41-
| Region | AI enrichment | Availability zones | Agentic retrieval | Semantic ranker | Query rewrite |
42-
|--|--|--|--|--|--|
43-
| Brazil South​​ ​| ✅ | | ✅ | ✅ | ✅ |
44-
| Canada Central​​ | ✅ | ✅ | ✅ | ✅ | ✅ |
45-
| Canada East​​ ​| | | ✅ | ✅ | |
46-
| ​Central US​​ | ✅ | ✅ | ✅ | ✅ | ✅ |
47-
| East US​ | ✅ | ✅ | ✅ | ✅ | |
48-
| East US 2 | ✅ | ✅ | ✅ | ✅ | ✅ |
49-
| Mexico Central | | ✅ | | | |
50-
| North Central US​ ​| ✅ | | ✅ | ✅ | ✅ |
51-
| South Central US​ | ✅ | ✅ | ✅ | ✅ | ✅ |
52-
| West US​​ | ✅ | | ✅ | ✅ | ✅ |
53-
| West US 2​ ​| ✅ | ✅ | ✅ | ✅ | ✅ |
54-
| West US 3​ | ✅ | ✅ | ✅ | ✅ | ✅ |
55-
| West Central US​ ​ | ✅ | | ✅ | ✅ | |
42+
| Region | AI enrichment | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
43+
|--|--|--|--|--|--|--|
44+
| Brazil South​​ ​| ✅ | | ✅ | ✅ | ✅ | ✅ |
45+
| Canada Central​​ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
46+
| Canada East​​ ​| | | ✅ | | ✅ | |
47+
| ​Central US​​ | ✅ | ✅ | ✅ | | ✅ | ✅ |
48+
| East US​ | ✅ | ✅ | ✅ | | ✅ | |
49+
| East US 2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
50+
| Mexico Central | | ✅ | | ✅ | | |
51+
| North Central US​ ​| ✅ | | ✅ | | ✅ | ✅ |
52+
| South Central US​ | ✅ | ✅ | ✅ | | ✅ | ✅ |
53+
| West US​​ | ✅ | | ✅ | | ✅ | ✅ |
54+
| West US 2​ ​| ✅ | ✅ | ✅ | | ✅ | ✅ |
55+
| West US 3​ | ✅ | ✅ | ✅ | | ✅ | ✅ |
56+
| West Central US​ ​ | ✅ | | ✅ | | ✅ | |
5657

5758
### Europe
5859

59-
| Region | AI enrichment | Availability zones | Agentic retrieval | Semantic ranker | Query rewrite |
60-
|--|--|--|--|--|--|
61-
| France Central​​ | ✅ | ✅ | ✅ | ✅ | ✅ |
62-
| Germany West Central​ ​| ✅ | ✅ | ✅ | ✅ | |
63-
| Italy North​​ | | ✅ | ✅ | ✅ | |
64-
| Norway East​​ | ✅ | ✅ | | | |
65-
| North Europe​​ | ✅ | ✅ | ✅ | ✅ | ✅ |
66-
| Poland Central​​ | | | ✅ | ✅ | |
67-
| Spain Central <sup>1</sup> | | ✅ | | | |
68-
| Sweden Central​​ | ✅ | ✅ | ✅ | ✅ | ✅ |
69-
| Switzerland North​ | ✅ | ✅ | ✅ | ✅ | ✅ |
70-
| Switzerland West​ | ✅ | ✅ | ✅ | ✅ | |
71-
| UK South​ | ✅ | ✅ | ✅ | ✅ | ✅ |
72-
| UK West​ ​| | | ✅ | ✅ | |
73-
| West Europe​​ | ✅ | ✅ | ✅ | ✅ | ✅ |
60+
| Region | AI enrichment | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
61+
|--|--|--|--|--|--|--|
62+
| France Central​​ | ✅ | ✅ | ✅ | | ✅ | ✅ |
63+
| Germany West Central​ ​| ✅ | ✅ | ✅ | | ✅ | |
64+
| Italy North​​ | | ✅ | ✅ | ✅ | ✅ | |
65+
| Norway East​​ | ✅ | ✅ | | ✅ | | |
66+
| North Europe​​ | ✅ | ✅ | ✅ | | ✅ | ✅ |
67+
| Poland Central​​ | | | ✅ | | ✅ | |
68+
| Spain Central <sup>1</sup> | | ✅ | | ✅ | | |
69+
| Sweden Central​​ | ✅ | ✅ | ✅ | | ✅ | ✅ |
70+
| Switzerland North​ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
71+
| Switzerland West​ | ✅ | ✅ | ✅ | | ✅ | |
72+
| UK South​ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
73+
| UK West​ ​| | | ✅ | | ✅ | |
74+
| West Europe​​ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
7475

7576
<sup>1</sup> [Higher storage limits](search-limits-quotas-capacity.md#service-limits) aren't available in this region. If you want higher limits, choose a different region.
7677

7778
### Middle East
7879

79-
| Region | AI enrichment | Availability zones | Agentic retrieval | Semantic ranker | Query rewrite |
80-
|--|--|--|--|--|--|
81-
| Israel Central​ <sup>1</sup> | | ✅ | | | |
82-
| Qatar Central​ <sup>1</sup> | | ✅ | ✅ | ✅ | |
83-
| UAE North​​ | ✅ | ✅ | ✅ | ✅ | |
80+
| Region | AI enrichment | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
81+
|--|--|--|--|--|--|--|
82+
| Israel Central​ <sup>1</sup> | | ✅ | | | | |
83+
| Qatar Central​ <sup>1</sup> | | ✅ | ✅ | | ✅ | |
84+
| UAE North​​ | ✅ | ✅ | ✅ | ✅ | ✅ | |
8485

8586
<sup>1</sup> [Higher storage limits](search-limits-quotas-capacity.md#service-limits) aren't available in this region. If you want higher limits, choose a different region.
8687

8788
### Africa
8889

89-
| Region | AI enrichment | Availability zones | Agentic retrieval | Semantic ranker | Query rewrite |
90-
|--|--|--|--|--|--|
91-
| South Africa North​ | ✅ | ✅ | ✅ | ✅ | |
90+
| Region | AI enrichment | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
91+
|--|--|--|--|--|--|--|
92+
| South Africa North​ | ✅ | ✅ | ✅ | ✅ | ✅ | |
9293

9394
### Asia Pacific
9495

95-
| Region | AI enrichment | Availability zones | Agentic retrieval | Semantic ranker | Query rewrite |
96-
|--|--|--|--|--|--|
97-
| Australia East​ ​| ✅ | ✅ | ✅ | ✅ | ✅ |
98-
| Australia Southeast​​​ | | | ✅ | ✅ | |
99-
| Central India | ✅ | ✅ | ✅ | ✅ | ✅ |
100-
| East Asia​ | ✅ | ✅ | ✅ | ✅ | ✅ |
101-
| Indonesia Central | | ✅ | | | |
102-
| Jio India West​​ | ✅ | | ✅ | ✅ | ✅ |
103-
| Jio India Central​​ | | | | | |
104-
| Japan East | ✅ | ✅ | ✅ | ✅ | ✅ |
105-
| Japan West​ | ✅ | | ✅ | ✅ | |
106-
| Korea Central | ✅ | ✅ | ✅ | ✅ | ✅ |
107-
| Korea South​​ | | | ✅ | ✅ | |
108-
| Malaysia West | | ✅ | | | |
109-
| New Zealand North | | ✅ | | | |
110-
| South India | | ✅ | | | |
111-
| Southeast Asia​​ | ✅ | ✅ | ✅ | ✅ | ✅ |
96+
| Region | AI enrichment | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
97+
|--|--|--|--|--|--|--|
98+
| Australia East​ ​| ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
99+
| Australia Southeast​​​ | | | ✅ | | ✅ | |
100+
| Central India | ✅ | ✅ | ✅ | | ✅ | ✅ |
101+
| East Asia​ | ✅ | ✅ | ✅ | | ✅ | ✅ |
102+
| Indonesia Central | | ✅ | | | | |
103+
| Jio India West​​ | ✅ | | ✅ | | ✅ | ✅ |
104+
| Jio India Central​​ | | | | | | |
105+
| Japan East | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
106+
| Japan West​ | ✅ | | ✅ | | ✅ | |
107+
| Korea Central | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
108+
| Korea South​​ | | | ✅ | | ✅ | |
109+
| Malaysia West | | ✅ | | | | |
110+
| New Zealand North | | ✅ | | | | |
111+
| South India | | ✅ | | | | |
112+
| Southeast Asia​​ | ✅ | ✅ | ✅ | | ✅ | ✅ |
112113

113114
## Azure Government regions
114115

115-
| Region | AI enrichment | Availability zones | Agentic retrieval | Semantic ranker | Query rewrite |
116-
|--|--|--|--|--|--|
117-
| Arizona | ✅ | | ✅ | ✅ | ✅ |
118-
| Texas | | | | | |
119-
| Virginia | ✅ | ✅ | ✅ | ✅ | ✅ |
116+
| Region | AI enrichment | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
117+
|--|--|--|--|--|--|--|
118+
| Arizona | ✅ | | ✅ | | ✅ | ✅ |
119+
| Texas | | | | | | |
120+
| Virginia | ✅ | ✅ | ✅ | | ✅ | ✅ |
120121

121122
## Azure operated by 21Vianet
122123

123-
| Region | AI enrichment | Availability zones | Agentic retrieval | Semantic ranker | Query rewrite |
124-
|--|--|--|--|--|--|
125-
| China East | | | | | |
126-
| China East 2 <sup>1</sup> | ✅ | | | |
127-
| China East 3 | | | | | |
128-
| China North | | | | | |
129-
| China North 2 <sup>1</sup> | | | | | |
130-
| China North 3 | | ✅ | ✅ | ✅ | ✅ |
124+
| Region | AI enrichment | Availability zones | Agentic retrieval | Confidential computing | Semantic ranker | Query rewrite |
125+
|--|--|--|--|--|--|--|
126+
| China East | | | | | | |
127+
| China East 2 <sup>1</sup> | ✅ | | | | | |
128+
| China East 3 | | | | | | |
129+
| China North | | | | | | |
130+
| China North 2 <sup>1</sup> | | | | | | |
131+
| China North 3 | | ✅ | ✅ | | ✅ | ✅ |
131132

132133
<sup>1</sup> [Higher storage limits](search-limits-quotas-capacity.md#service-limits) aren't available in this region. If you want higher limits, choose a different region.
133134

0 commit comments

Comments
 (0)