Merge pull request #306591 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-07 17:00 UTC

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

articles/api-management/azure-ai-foundry-api.md

@@ -5,7 +5,7 @@ ms.service: azure-api-management
 author: dlepow
 ms.author: danlep
 ms.topic: how-to
-ms.date: 05/16/2025
+ms.date: 10/07/2025
 ms.update-cycle: 180-days
 ms.collection: ce-skilling-ai-copilot
 ms.custom: template-how-to, build-2024
@@ -24,15 +24,15 @@ Learn more about managing AI APIs in API Management:
 
 ## Client compatibility options
 
-API Management supports two client compatibility options for AI APIs. Choose the option suitable for your model deployment. The option determines how clients call the API and how the API Management instance routes requests to the AI service.
+API Management supports two client compatibility options for AI APIs from Azure AI Foundry. When you import the API using the wizard, choose the option suitable for your model deployment. The option determines how clients call the API and how the API Management instance routes requests to the AI service.
 
-* **Azure AI** - Manage model endpoints in Azure AI Foundry that are exposed through the [ Azure AI Model Inference API](/azure/ai-studio/reference/reference-model-inference-api).
+* **Azure OpenAI** - Manage Azure OpenAI in Azure AI Foundry model deployments. 
 
-    Clients call the deployment at a `/models` endpoint such as `/my-model/models/chat/completions`. Deployment name is passed in the request body. Use this option if you want flexibility to switch between models exposed through the Azure AI Model Inference API and those deployed in Azure OpenAI in Foundry Models.
+    Clients call the deployment at an `/openai` endpoint such as `/openai/deployments/my-deployment/chat/completions`. Deployment name is passed in the request path. Use this option if your AI service only includes Azure OpenAI model deployments. 
 
-* **Azure OpenAI** - Manage model endpoints deployed in Azure OpenAI. 
+* **Azure AI** - Manage model endpoints in Azure AI Foundry that are exposed through the [Azure AI Model Inference API](/azure/ai-studio/reference/reference-model-inference-api).
 
-    Clients call the deployment at an `/openai` endpoint such as `/openai/deployments/my-deployment/chat/completions`. Deployment name is passed in the request path. Use this option if your AI service only includes Azure OpenAI model deployments. 
+    Clients call the deployment at a `/models` endpoint such as `/my-model/models/chat/completions`. Deployment name is passed in the request body. Use this option if you want flexibility to switch between models exposed through the Azure AI Model Inference API and those deployed in Azure OpenAI in Foundry Models.
 
 ## Prerequisites
 
@@ -69,7 +69,7 @@ To import an AI Foundry API to API Management:
     1. In **Base path**, enter a path that your API Management instance uses to access the deployment endpoint.
     1. Optionally select one or more **Products** to associate with the API.  
     1. In **Client compatibility**, select either of the following based on the types of client you intend to support. See [Client compatibility options](#client-compatibility-options) for more information.
-        * **Azure OpenAI** - Select this option if your clients only need to access Azure OpenAI model deployments.
+        * **Azure OpenAI** - Select this option if your clients only need to access Azure OpenAI in AI Foundry model deployments.
         * **Azure AI** - Select this option if your clients need to access other models in Azure AI Foundry. 
     1. Select **Next**.
 

articles/api-management/graphql-api.md

@@ -1,15 +1,17 @@
 ---
 title: Add a GraphQL API to Azure API Management | Microsoft Docs
-description: Learn how to add an existing GraphQL service as an API in Azure API Management using the Azure portal, Azure CLI, or Azure PowerShell. Manage the API and enable queries to pass through to the GraphQL endpoint.
+description: Learn how to add an existing GraphQL service as an API in Azure API Management. Manage the API and enable queries to pass through to the GraphQL endpoint.
 ms.service: azure-api-management
 author: dlepow
 ms.author: danlep
 ms.topic: how-to
-ms.date: 04/10/2023
+ms.date: 10/07/2025
 ms.custom:
   - devx-track-azurepowershell
   - devx-track-azurecli
   - sfi-image-nochange
+
+# Customer intent: As an API admin, I want to add a GraphQL API to Azure API Management by passing through to an existing GraphQL endpoint.
 ---
 
 # Import a GraphQL API
@@ -23,87 +25,90 @@ In this article, you'll:
 > * Add a pass-through GraphQL API to your API Management instance.
 > * Test your GraphQL API.
 
-If you want to import a GraphQL schema and set up field resolvers using REST or SOAP API endpoints, see [Import a GraphQL schema and set up field resolvers](graphql-schema-resolve-api.md).
+If you want to import a GraphQL schema and set up field resolvers that use REST or SOAP API endpoints, see [Import a GraphQL schema and set up field resolvers](graphql-schema-resolve-api.md).
 
 ## Prerequisites
 
-- An existing API Management instance. [Create one if you haven't already](get-started-create-service-instance.md).
-- A GraphQL API. 
-- Azure CLI
+- An Azure API Management instance. [Create one if you haven't already](get-started-create-service-instance.md).
+- Azure CLI, if you want to use it to import the API.
     [!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
 
-- Azure PowerShell
+- Azure PowerShell, if you want to use it to import the API.
     [!INCLUDE [azure-powershell-requirements-no-header](~/reusable-content/ce-skilling/azure/includes/azure-powershell-requirements-no-header.md)]
 
 ## Add a GraphQL API
 
 #### [Portal](#tab/portal)
 
-1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
-1. In the left menu, select **APIs** > **+ Add API**.
-1. Under **Define a new API**, select the **GraphQL** icon.
+1. In the [Azure portal](https://portal.azure.com), go to your API Management instance.
+1. In the left pane, select **APIs** > **APIs**.
+1. Select **Add API**.
+1. Under **Define a new API**, select the **GraphQL** tile.
 
-    :::image type="content" source="media/graphql-api/import-graphql-api.png" alt-text="Screenshot of selecting GraphQL icon from list of APIs.":::
+    :::image type="content" source="media/graphql-api/import-graphql-api.png" alt-text="Screenshot of selecting the GraphQL tile.":::
 
-1. In the dialog box, select **Full** and complete the required form fields.
+1. In the resulting dialog box, select **Full**, and then enter values in the required fields, as described in the following table.
 
-    :::image type="content" source="media/graphql-api/create-from-graphql-endpoint.png" alt-text="Screenshot of fields for creating a GraphQL API.":::
+    :::image type="content" source="media/graphql-api/create-from-graphql-endpoint.png" alt-text="Screenshot of the Create from GraphQL schema page." lightbox="media/graphql-api/create-from-graphql-endpoint.png":::
 
-    | Field | Description |
+    | Value | Description |
     |----------------|-------|
     | **Display name** | The name by which your GraphQL API will be displayed. |
-    | **Name** | Raw name of the GraphQL API. Automatically populates as you type the display name. |
+    | **Name** | The raw name of the GraphQL API. Automatically populates as you type the display name. |
     | **GraphQL type** | Select **Pass-through GraphQL** to import from an existing GraphQL API endpoint.  |
-    | **GraphQL API endpoint** | The base URL with your GraphQL API endpoint name. <br /> For example: *`https://example.com/your-GraphQL-name`*. You can also use a common "swapi" GraphQL endpoint such as `https://swapi-graphql.azure-api.net/graphql` as a demo. |
-    | **Upload schema** | Optionally select to browse and upload your schema file to replace the schema retrieved from the GraphQL endpoint (if available).  |
+    | **GraphQL API endpoint** | The base URL with your GraphQL API endpoint name. <br /> For example: *`https://example.com/your-GraphQL-name`*. You can also use a common SWAPI GraphQL endpoint like `https://swapi-graphql.azure-api.net/graphql` for the purpose of demonstration. |
+    | **Upload schema** | Optionally select to upload your schema file to replace the schema that's retrieved from the GraphQL endpoint (if you have one).  |
     | **Description** | Add a description of your API. |
-    | **URL scheme** |  Make a selection based on your GraphQL endpoint. Select one of the options that includes a WebSocket scheme (**WS** or **WSS**) if your GraphQL API includes the subscription type. Default selection: *HTTP(S)*. |
-    | **API URL suffix**| Add a URL suffix to identify this specific API in this API Management instance. It has to be unique in this API Management instance. |
-    | **Base URL** | Uneditable field displaying your API base URL |
-    | **Tags** | Associate your GraphQL API with new or existing tags. |
+    | **URL scheme** |  Select a scheme based on your GraphQL endpoint. Select one of the options that includes a WebSocket scheme (**WS** or **WSS**) if your GraphQL API includes the subscription type. The default selection is **HTTP(S)**. |
+    | **API URL suffix**| Add a URL suffix to identify the specific API in the API Management instance. It has to be unique in the API Management instance. |
+    | **Base URL** | Uneditable field displaying your API base URL. |
+    | **Tags** | Optionally associate your GraphQL API with new or existing tags. |
     | **Products** | Associate your GraphQL API with a product to publish it. |
-    | **Version this API?** | Select to apply a versioning scheme to your GraphQL API. |
+    | **Version this API?** | Select the checkbox to apply a versioning scheme to your GraphQL API. |
 
 1. Select **Create**.
-1. After the API is created, browse or modify the schema on the **Design** tab.
-       :::image type="content" source="media/graphql-api/explore-schema.png" alt-text="Screenshot of exploring the GraphQL schema in the portal.":::
+1. After the API is created, review or modify the schema on the **Schema** tab.
+       :::image type="content" source="media/graphql-api/explore-schema.png" alt-text="Screenshot of the GraphQL schema in the portal." lightbox="media/graphql-api/explore-schema.png":::
 
 #### [Azure CLI](#tab/cli)
 
 The following example uses the [az apim api import](/cli/azure/apim/api#az-apim-api-import) command to import a GraphQL passthrough API from the specified URL to an API Management instance named *apim-hello-world*. 
 
-```azurecli-interactive
-# API Management service-specific details
+```azurecli
+# Details specific to API Management instance.
 APIMServiceName="apim-hello-world"
 ResourceGroupName="myResourceGroup"
 
-# API-specific details
+# API-specific details.
 APIId="my-graphql-api"
 APIPath="myapi"
 DisplayName="MyGraphQLAPI"
 SpecificationFormat="GraphQL"
 SpecificationURL="<GraphQL backend endpoint>"
 
-# Import API
-az apim api import --path $APIPath --resource-group $ResourceGroupName \
+# Import API.
+az apim api import \
+    --path $APIPath \
+    --resource-group $ResourceGroupName \
     --service-name $APIMServiceName --api-id $APIId \
-    --display-name $DisplayName --specification-format $SpecificationFormat --specification-url $SpecificationURL
+    --display-name $DisplayName --specification-format $SpecificationFormat \
+    --specification-url $SpecificationURL
 ```
 
-After importing the API, if needed, you can update the settings by using the [az apim api update](/cli/azure/apim/api#az-apim-api-update) command.
+After importing the API, you can update the settings by using the [az apim api update](/cli/azure/apim/api#az-apim-api-update) command, if you need to.
 
 
 #### [PowerShell](#tab/powershell)
 
 The following example uses the [Import-AzApiManagementApi](/powershell/module/az.apimanagement/import-azapimanagementapi?) Azure PowerShell cmdlet to import a GraphQL passthrough API from the specified URL to an API Management instance named *apim-hello-world*. 
 
-```powershell-interactive
-# API Management service-specific details
+```azurepowershell
+# Details specific to API Management instance.
 $apimServiceName = "apim-hello-world"
 $resourceGroupName = "myResourceGroup"
 
-# API-specific details
+# API-specific details.
 $apiId = "my-graphql-api"
 $apiPath = "myapi"
 $specificationFormat = "GraphQL"
@@ -112,30 +117,32 @@ $specificationUrl = "<GraphQL backend endpoint>"
 # Get context of the API Management instance. 
 $context = New-AzApiManagementContext -ResourceGroupName $resourceGroupName -ServiceName $apimServiceName
 
-# Import API
+# Import API.
 Import-AzApiManagementApi -Context $context -ApiId $apiId -SpecificationFormat $specificationFormat -SpecificationUrl $specificationUrl -Path $apiPath
 ```
 
-After importing the API, if needed, you can update the settings by using the [Set-AzApiManagementApi](/powershell/module/az.apimanagement/set-azapimanagementapi) cmdlet.
+After importing the API, you can update the settings by using the [Set-AzApiManagementApi](/powershell/module/az.apimanagement/set-azapimanagementapi) cmdlet, if you need to.
 
 ---
 
 [!INCLUDE [api-management-graphql-test.md](../../includes/api-management-graphql-test.md)]
 
 ### Test a subscription
-If your GraphQL  API supports a subscription, you can test it in the test console.
+
+If your GraphQL API supports a subscription, you can test it in the test console.
 
 1. Ensure that your API allows a WebSocket URL scheme (**WS** or **WSS**) that's appropriate for your API. You can enable this setting on the **Settings** tab.
 1. Set up a subscription query in the query editor, and then select **Connect** to establish a WebSocket connection to the backend service. 
 
-    :::image type="content" source="media/graphql-api/test-graphql-subscription.png" alt-text="Screenshot of a subscription query in the query editor.":::
+    :::image type="content" source="media/graphql-api/test-graphql-subscription.png" alt-text="Screenshot of a subscription query in the query editor." lightbox="media/graphql-api/test-graphql-subscription.png":::
+
 1. Review connection details in the **Subscription** pane. 
 
     :::image type="content" source="media/graphql-api/graphql-websocket-connection.png" alt-text="Screenshot of WebSocket connection in the portal.":::
 
-1. Subscribed events appear in the **Subscription** pane. The WebSocket connection is maintained until you disconnect it or you connect to a new WebSocket subscription.  
+1. Subscribed events appear in the **Subscription** pane. The WebSocket connection is maintained until you disconnect it or connect to a new WebSocket subscription.  
 
-    :::image type="content" source="media/graphql-api/graphql-subscription-event.png" alt-text="Screenshot of GraphQL subscription events in the portal.":::
+    :::image type="content" source="media/graphql-api/graphql-subscription-event.png" alt-text="Screenshot of GraphQL subscription events in the portal." lightbox="media/graphql-api/graphql-subscription-event.png":::
 
 ## Secure your GraphQL API
 

articles/api-management/media/graphql-api/create-from-graphql-endpoint.png

@@ -5,7 +5,7 @@ author: msangapu-msft
 ms.author: msangapu
 ms.topic: how-to
 ms.custom: devx-track-azurecli
-ms.date: 01/15/2025
+ms.date: 10/07/2025
 ROBOTS: NOINDEX
 ms.service: azure-app-service
 
@@ -16,6 +16,9 @@ ms.service: azure-app-service
 
 # Set up an Azure Arc-enabled Kubernetes cluster to run App Service, Functions, and Logic Apps (Preview)
 
+> [!IMPORTANT]
+> [Azure App Service on Arc enabled Kubernetes will be **retired on March 31, 2026**](https://azure.microsoft.com/updates/?id=500016). From September 30, 2025, customers will no longer be able to install the extension. We request you [migrate to other solutions such as Azure Container Apps on Arc enabled Kubernetes](migrate-app-service-arc.md), migrating also allows you to take advantage of [Logic Apps Hybrid](/azure/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements) for your integration workloads.
+
 If you have an [Azure Arc-enabled Kubernetes cluster](/azure/azure-arc/kubernetes/overview), you can use it to create an [App Service enabled custom location](overview-arc-integration.md) and deploy web apps, function apps, and logic apps to it.
 
 Azure Arc-enabled Kubernetes lets you make your on-premises or cloud Kubernetes cluster visible to App Service, Functions, and Logic Apps in Azure. You can create an app and deploy to it just like another Azure region.