Merge pull request #6052 from MicrosoftDocs/main

Auto Publish – main to live - 2025-07-16 05:06 UTC

Author: learn-build-service-prod[bot]

articles/ai-foundry/agents/how-to/virtual-networks.md

@@ -68,6 +68,9 @@ For customers without an existing virtual network, the Standard Setup with Priva
        az provider register --namespace 'Microsoft.Storage'
        az provider register --namespace 'Microsoft.MachineLearningServices'
        az provider register --namespace 'Microsoft.Search'
+       az provider register --namespace 'Microsoft.Network'
+       az provider register --namespace 'Microsoft.App'
+       az provider register --namespace 'Microsoft.ContainerService'
        # only to use Grounding with Bing Search tool
        az provider register --namespace 'Microsoft.Bing'
     ```
@@ -169,6 +172,8 @@ The following DNS zones are configured:
 ### Virtual network (Vnet) capabilities
 Virtual networks enable you to specify which endpoints can make API calls to your resources. The Azure service automatically rejects API calls from devices outside your defined network. You can establish allowed networks using either formula-based definitions or by creating an exhaustive list of permitted endpoints. This security layer can be combined with other security measures for enhanced protection.
 
+> [!NOTE]
+> If you bring your existing virtual network and subnet with the *Microsoft.App/environments* delegation, the minimize size of your subnet should be /27 (32 addresses). We recommend a subnet size of /24 (256 addresses) and is the default subnet size set in the network secured template. 
 
 ### Network rules
 

articles/ai-services/content-understanding/quickstart/use-rest-api.md

@@ -5,7 +5,7 @@ description: Learn about Content Understanding REST APIs
 author: PatrickFarley 
 ms.author: paulhsu
 manager: nitinme
-ms.date: 05/19/2025
+ms.date: 07/15/2025
 ms.service: azure-ai-content-understanding
 ms.topic: quickstart
 ms.custom:
@@ -20,15 +20,11 @@ ms.custom:
 
 ## Prerequisites
 
-To get started, you need **an active Azure subscription**. If you don't have an Azure account, [create one for free](https://azure.microsoft.com/free/).
-
-* Once you have your Azure subscription, create an [Azure AI Foundry resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesAIFoundry) in the Azure portal.
-
+* To get started, you need **an active Azure subscription**. If you don't have an Azure account, [create one for free](https://azure.microsoft.com/free/).
+* Once you have your Azure subscription, create an [Azure AI Foundry resource](https://portal.azure.com/#create/Microsoft.CognitiveServicesAIFoundry) in the Azure portal. Be sure to create it in a [supported region](/azure/ai-services/content-understanding/language-region-support).
    * This resource is listed under **AI Foundry** > **AI Foundry** in the portal.
-
      :::image type="content" source="../media/overview/azure-multi-service-resource.png" alt-text="Screenshot of the AI Foundry resource page in the Azure portal.":::
-
-In this guide, we use the cURL command line tool. If it isn't installed, you can [download](https://everything.curl.dev/install/index.html) the appropriate version for your dev environment.
+* In this guide, we use the cURL command line tool. If it isn't installed, you can [download](https://everything.curl.dev/install/index.html) the appropriate version for your dev environment.
 
 ## Get started with a prebuilt analyzer
 
@@ -73,34 +69,33 @@ curl -i -X POST "{endpoint}/contentunderstanding/analyzers/{analyzerId}:analyze?
 ```
 
 #### POST response
-The response includes a JSON body containing the `resultId`, which you use to retrieve the results of the asynchronous analysis operation. Additionally, the `Operation-Location` header provides the direct URL to access the analysis result.
+The response includes a `request-id`, which you use to retrieve the results of the asynchronous analysis operation. Additionally, the `Operation-Location` header provides the direct URL to access the analysis result.
 
 ```
-202 Accepted
-Operation-Location: {endpoint}/contentunderstanding/analyzerResults/{resultId}?api-version=2024-12-01-preview
-{
-  "id": {resultId},
-  "status": "Running",
-  "result": {
-    "analyzerId": {analyzerId},
-    "apiVersion": "2025-05-01-preview",
-    "createdAt": "YYYY-MM-DDTHH:MM:SSZ",
-    "warnings": [],
-    "contents": []
-  }
-}
+HTTP/1.1 202 Accepted
+Transfer-Encoding: chunked
+Content-Type: application/json
+request-id: aaa-bbb-ccc-ddd
+x-ms-request-id: aaa-bbb-ccc-ddd
+Operation-Location: {endpoint}/contentunderstanding/analyzerResults/{request-id}?api-version=2025-05-01-preview
+api-supported-versions: 2024-12-01-preview,2025-05-01-preview,2025-10-01
+x-envoy-upstream-service-time: 800
+apim-request-id: {request-id}
+Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
+x-content-type-options: nosniff
+x-ms-region: West US
 ```
 
 ### Get analyze result
 
-Use the `resultId` from the [`POST` response](#post-response) and retrieve the result of the analysis.
+Use the `request-id` from the [`POST` response](#post-response) and retrieve the result of the analysis.
 
 1. Replace `{endpoint}` and `{key}` with the endpoint and key values from your Azure portal Azure AI Foundry instance.
-2. Replace `{analyzerResultId}` with the `id` from the `POST` response or use the complete URL from the `Operation-Location` response header.
+2. Replace `{request-id}` with the `request-id` from the `POST` response, or use the complete URL from the `Operation-Location` response header.
 
 #### GET request
 ```bash
-curl -i -X GET "GET {endpoint}/contentunderstanding/analyzerResults/{analyzerResultId}?api-version=2025-05-01-preview" \
+curl -i -X GET "{endpoint}/contentunderstanding/analyzerResults/{request-id}?api-version=2025-05-01-preview" \
   -H "Ocp-Apim-Subscription-Key: {key}"
 ```
 
@@ -112,7 +107,7 @@ The 200 (`OK`) JSON response includes a `status` field indicating the status of
 
 ```json
 {
-  "id": {resultId},
+  "id": "<request-id>",
   "status": "Succeeded",
   "result": {
     "analyzerId": "prebuilt-documentAnalyzer",
@@ -206,7 +201,7 @@ The 200 (`OK`) JSON response includes a `status` field indicating the status of
 
 ```json
 {
-  "id": {resultId},
+  "id": "<request-id>",
   "status": "Succeeded",
   "result": {
     "analyzerId": "prebuilt-imageAnalyzer",
@@ -242,7 +237,7 @@ The 200 (`OK`) JSON response includes a `status` field indicating the status of
 
 ```json
 {
-  "id": {resultId},
+  "id": "<request-id>",
   "status": "Succeeded",
   "result": {
     "analyzerId": "prebuilt-audioAnalyzer",
@@ -287,7 +282,7 @@ The 200 (`OK`) JSON response includes a `status` field indicating the status of
 
 ```json
 {
-  "id": {resultId},
+  "id": "<request-id>",
   "status": "Succeeded",
   "result": {
     "analyzerId": "prebuilt-videoAnalyzer",
@@ -345,7 +340,7 @@ The 200 (`OK`) JSON response includes a `status` field indicating the status of
 
 ---
 
-## Next steps
+## Next step
 
 Learn more about creating [custom analyzers](../tutorial/create-custom-analyzer.md) for your use case.