Merge pull request #312444 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-27 23:00 UTC

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

articles/api-management/api-management-howto-api-inspector.md

@@ -19,7 +19,7 @@ ms.custom:
 
 This tutorial describes how to inspect, or *trace*, request processing in Azure API Management. Tracing helps you debug and troubleshoot your API.
 
-[!INCLUDE [api-management-workspace-try-it](../../includes/api-management-workspace-try-it.md)]
+[!INCLUDE [api-management-workspace-availability](../../includes/api-management-workspace-availability.md)]
 
 In this tutorial, you learn how to:
 

articles/api-management/api-management-howto-manage-protocols-ciphers.md

@@ -46,7 +46,7 @@ API Management supports TLS versions up to TLS 1.3 for client and backend connec
 1. Select **Save**.
 
 > [!NOTE]
-> Some protocols or cipher suites (such as backend-side TLS 1.2) can't be enabled or disabled from the Azure portal. Instead, you'll need to apply the REST API call. Use the `properties.customProperties` structure in the [Create/Update API Management Service](/rest/api/apimanagement/current-ga/api-management-service/create-or-update) REST API.
+> Some protocols or cipher suites such as backend-side TLS 1.2 can't be enabled or disabled from the Azure portal. Instead, you'll need to apply the REST API call for these updates (backend side only). Use the `properties.customProperties` structure in the [Create/Update API Management Service](/rest/api/apimanagement/current-ga/api-management-service/create-or-update) REST API.
 
 ## TLS 1.3 support
 

articles/api-management/how-to-self-hosted-gateway-on-kubernetes-in-production.md

@@ -1,12 +1,12 @@
 ---
-title: Tutorial - Import and Publish Your First API in Azure API Management
-description: In this tutorial, you import an OpenAPI specification API into Azure API Management, and then test your API in the Azure portal.
+title: "Tutorial: Import and Publish Your First API in Azure API Management"
+description: Learn how to import an OpenAPI specification API into Azure API Management, and then test your API in the Azure portal.
 
 author: dlepow
 ms.service: azure-api-management
 ms.custom: mvc, devdivchpfy22, engagement-fy23
 ms.topic: tutorial
-ms.date: 01/20/2026
+ms.date: 02/23/2026
 ms.author: danlep
 
 ---
@@ -18,7 +18,7 @@ This tutorial shows how to import an OpenAPI specification backend API in JSON f
 
 [!INCLUDE [api-management-workspace-try-it](../../includes/api-management-workspace-try-it.md)]
 
-When you import the backend API into API Management, your API Management API becomes a façade for the backend API. You can customize the façade to your needs in API Management without changing the backend API. For more information, see [Transform and protect your API](transform-api.md).
+When you import the backend API into API Management, your API Management API becomes the gateway for the backend API. You can customize the gateway to your needs in API Management without changing the backend API. For more information, see [Transform and protect your API](transform-api.md).
 
 In this tutorial, you learn how to:
 
@@ -35,24 +35,26 @@ After import, you can manage the API in the Azure portal.
 ## Prerequisites
 
 - Understand [Azure API Management terminology](api-management-terminology.md).
-- [Create an Azure API Management instance](get-started-create-service-instance.md).
+- Create an [Azure API Management instance](get-started-create-service-instance.md).
 
 [!INCLUDE [api-management-navigate-to-instance.md](../../includes/api-management-navigate-to-instance.md)]
 
 ## Import and publish a backend API
 
 This section shows how to import and publish an OpenAPI specification backend API.
 
-1. In the left navigation of your API Management instance, under **APIs**, select **APIs**.
+1. In your API Management instance, under **APIs** in the sidebar menu, select **APIs**.
+
 1. Select the **OpenAPI** tile.
+
 1. In the **Create from OpenAPI specification** window, select **Full**.
+
 1. Enter the values from the following table.
 
    You can set API values during creation or later by going to the **Settings** tab.
 
    :::image type="content" source="media/import-and-publish/open-api-specs.png" alt-text="Screenshot of creating an API in the portal.":::
 
-
    |Setting|Value|Description|
    |-------|-----|-----------|
    |**OpenAPI specification**|*https:\//petstore3.swagger.io/api/v3/openapi.json* -or- *https:\//petstore.swagger.io/v2/swagger.json*|Specifies the backend service implementing the API and the operations that the API supports. <br/><br/>The backend service URL appears later as the **Web service URL** on the API's **Settings** page.<br/><br/>After import, you can add, edit, rename, or delete operations in the specification.  |
@@ -64,25 +66,27 @@ This section shows how to import and publish an OpenAPI specification backend AP
    |**API URL suffix**|*petstore*|The suffix appended to the base URL for the API Management service. API Management distinguishes and routes APIs by their suffix, so the suffix must be unique for every API for a given publisher. Learn more about [how API Management routes requests](#how-api-management-routes-requests). |
    |**Tags**| |Tags for organizing APIs for searching, grouping, or filtering.|
    |**Products**|**Unlimited**|Association of one or more APIs. In certain tiers, API Management instance comes with two sample products: **Starter** and **Unlimited**. You publish an API in the developer portal by associating the API with a product.<br/><br/> You can include several APIs in a product and offer product [subscriptions](api-management-subscriptions.md) to developers through the developer portal. To add this API to another product, type or select the product name. Repeat this step to add the API to multiple products. You can also add APIs to products later from the **Settings** page.<br/><br/>  For more information about products, see [Create and publish a product](api-management-howto-add-products.md).|
-   |**Gateways**|**Managed**|API gateway(s) that expose the API. This field is available only in **Developer** and **Premium** tier services.<br/><br/>**Managed** indicates the gateway built into the API Management service and hosted by Microsoft in Azure. [Self-hosted gateways](self-hosted-gateway-overview.md) are available only in the Premium and Developer service tiers. You can deploy them on-premises or in other clouds.<br/><br/> If you don't select any gateways, the API isn't available and your API requests don't succeed.|
+   |**Gateways**|**Managed**|API gateways that expose the API. This field is available only in **Developer** and **Premium** tier services.<br/><br/>**Managed** indicates the gateway built into the API Management service and hosted by Microsoft in Azure. [Self-hosted gateways](self-hosted-gateway-overview.md) are available only in the Premium and Developer service tiers. You can deploy them on-premises or in other clouds.<br/><br/> If you don't select any gateways, the API isn't available and your API requests don't succeed.|
    |**Version this API?**|Select or deselect|For more information, see [Publish multiple versions of your API](api-management-get-started-publish-versions.md).|
 
 1. Select **Create** to create your API.
 
-If you have problems importing an API definition, see the [list of known issues and restrictions](api-management-api-import-restrictions.md).
+If you have problems importing an API definition, see [API import restrictions and known issues](api-management-api-import-restrictions.md).
 
 ## View and modify API settings
 
 After importing your API, you can view and modify its settings and operations in the Azure portal.
 
-1. In the left navigation of your API Management instance, under **APIs**, select **APIs**.
+1. In your API Management instance, under **APIs** in the sidebar menu, select **APIs**.
+
 1. Select your imported API (for example, **Swagger Petstore**).
     :::image type="content" source="media/import-and-publish/view-api-settings.png" lightbox="media/import-and-publish/view-api-settings.png" alt-text="Screenshot of API settings in API Management in the portal.":::
 
 1. Select the **Design** tab to view and modify API operations in the OpenAPI specification, including:
     - Operation details such as URL, method, and description
     - Request and response definitions
     - Policies to modify requests and responses
+
 1. Select the **Settings** tab to view and modify API configuration details, including:
    - Display name, name, and description
    - Web service URL (backend service), URL scheme, and API URL suffix
@@ -95,10 +99,12 @@ As you go through the API Management tutorials, you learn more about configuring
 
 You can call API operations directly from the Azure portal, which provides a convenient way to view and test the operations. In the portal's test console, by default, APIs are called by using a key from the built-in all-access subscription. You can also test API calls by using a subscription key scoped to a product.
 
-1. In the left navigation of your API Management instance, select **APIs** > **APIs** > **Swagger Petstore**.
+1. In your API Management instance, select **APIs** > **APIs** > **Swagger Petstore**.
+
 1. Select the **Test** tab, and then select **Finds Pets by status**. The page shows the *status* **Query parameter**. Select one of the available values, such as *pending*. You can also add query parameters and headers here. 
 
     In the **HTTP request** section, the **Ocp-Apim-Subscription-Key** header is filled in automatically for you, which you can see if you select the "eye" icon.
+
 1. Select **Send**.
 
    :::image type="content" source="media/import-and-publish/test-new-api.png" alt-text="Screenshot of testing an API in Azure portal." lightbox="media/import-and-publish/test-new-api.png":::
@@ -135,26 +141,18 @@ The following table describes each routing parameter in the context of the Petst
 
 Using the Petstore API imported in this tutorial:
 
-1. **Client calls API Management:**  
+- **Client calls API Management:**  
    `https://apim-hello-world.azure-api.net/petstore/pet/findByStatus?status=pending`
    - API Management gateway URL: `https://apim-hello-world.azure-api.net`
    - API URL suffix: `petstore`
    - Operation endpoint: `/pet/findByStatus`
 
-1. **API Management routes to backend:**  
+- **API Management routes to backend:**  
    `https://petstore3.swagger.io/api/v3/pet/findByStatus?status=pending`
    - Web service URL: `https://petstore3.swagger.io/api/v3`
    - Operation endpoint: `/pet/findByStatus` (same as in the API Management definition)
 
-## Next steps
-
-In this tutorial, you learned how to:
-
-> [!div class="checklist"]
-> * Import your first API
-> * View and modify API settings
-> * Test the API in the Azure portal
-> * Route API requests through API Management
+## Next step
 
 Advance to the next tutorial to learn how to create and publish a product:
 

articles/api-management/import-and-publish.md

@@ -1,5 +1,5 @@
 ---
-title: Quickstart - Create Azure API Management instance - Bicep
+title: "Quickstart: Create Azure API Management instance by using Bicep"
 description: Use this quickstart to create an Azure API Management instance in the Developer tier by using Bicep.
 services: azure-resource-manager
 author: mumian
@@ -8,10 +8,10 @@ tags: azure-resource-manager, bicep
 ms.custom: devx-track-bicep, subject-bicepqs, devx-track-azurecli, devx-track-azurepowershell
 ms.topic: quickstart-bicep
 ms.author: jgao
-ms.date: 03/25/2024
+ms.date: 02/24/2026
 ---
 
-# Quickstart: Create a new Azure API Management service instance using Bicep
+# Quickstart: Create a new Azure API Management instance by using Bicep
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
@@ -31,30 +31,32 @@ This quickstart describes how to use a Bicep file to create an Azure API Managem
 
 - For Azure PowerShell:
 
-
     [!INCLUDE [azure-powershell-requirements-no-header](~/reusable-content/ce-skilling/azure/includes/azure-powershell-requirements-no-header.md)]
 
 ## Review the Bicep file
 
-The Bicep file used in this quickstart is from [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/azure-api-management-create/).
+The Bicep file used in this quickstart is from [Azure quickstart templates](/samples/azure/azure-quickstart-templates/azure-api-management-create/).
 
 :::code language="bicep" source="~/quickstart-templates/quickstarts/microsoft.apimanagement/azure-api-management-create/main.bicep":::
 
 The following resource is defined in the Bicep file:
 
-- **[Microsoft.ApiManagement/service](/azure/templates/microsoft.apimanagement/service)**
+- [Microsoft.ApiManagement/service](/azure/templates/microsoft.apimanagement/service)
 
 In this example, the Bicep file by default configures the API Management instance in the Developer tier, an economical option to evaluate Azure API Management. This tier isn't for production use.
 
-More Azure API Management Bicep samples can be found in [Azure Quickstart Templates](https://azure.microsoft.com/resources/templates/?resourceType=Microsoft.Apimanagement&pageNumber=1&sort=Popular).
+More Azure API Management Bicep samples can be found in [Azure quickstart templates](/samples/browse/?terms=api%20management&languages=bicep).
 
 ## Deploy the Bicep file
 
-You can use Azure CLI or Azure PowerShell to deploy the Bicep file.  For more information about deploying Bicep files, see [Deploy](../azure-resource-manager/bicep/deploy-cli.md).
+You can use Azure CLI or Azure PowerShell to deploy the Bicep file. For more information about deploying Bicep files, see [Deploy Bicep files with the Azure CLI](../azure-resource-manager/bicep/deploy-cli.md).
+
+1. Save the Bicep file as *main.bicep* to your local computer.
 
-1. Save the Bicep file as **main.bicep** to your local computer.
 1. Deploy the Bicep file using either Azure CLI or Azure PowerShell.
 
+    Replace *\<publisher-name\>* and *\<publisher-email\>* with your organization's name and your email address to receive notifications.
+
     # [CLI](#tab/CLI)
 
     ```azurecli
@@ -73,16 +75,14 @@ You can use Azure CLI or Azure PowerShell to deploy the Bicep file.  For more in
 
     ---
 
-    Replace **\<publisher-name\>** and **\<publisher-email\>** with the name of the API publisher's organization and the email address to receive notifications.
-
     When the deployment finishes, you should see a message indicating the deployment succeeded.
 
     > [!TIP]
     >  It can take between 30 and 40 minutes to create and activate an API Management service in the Developer tier. Times vary by tier.
 
 ## Review deployed resources
 
-Use the Azure portal, Azure CLI or Azure PowerShell to list the deployed App Configuration resource in the resource group.
+Use the Azure portal, Azure CLI, or Azure PowerShell to list the deployed App Configuration resource in the resource group.
 
 # [CLI](#tab/CLI)
 
@@ -118,7 +118,7 @@ Remove-AzResourceGroup -Name exampleRG
 
 ---
 
-## Next steps
+## Next step
 
 > [!div class="nextstepaction"]
 > [Tutorial: Import and publish your first API](import-and-publish.md)

articles/api-management/quickstart-bicep.md

@@ -42,7 +42,7 @@ The `validate-graphql-request` policy validates the GraphQL request and authoriz
 |Name|Description|Required|
 |----------|-----------------|--------------|
 | authorize | Add this element to set an appropriate authorization rule for one or more paths. | No |
-| rule | Add one or more of these elements to authorize specific query paths. Each rule can optionally specify a different [action](#request-actions). May be specified conditionally using a policy expression. | No |
+| rule | Add one or more of these elements to authorize specific query paths. Each rule can optionally specify a different [action](#request-actions). May be specified conditionally using a policy expression.<br/><br/>For each GraphQL leaf field, API Management evaluates all matching rules and applies the most specific path match (for example, `/Query/listUsers` overrides `/Query/*`). | No |
 
 
 ### rule attributes

articles/api-management/validate-graphql-request-policy.md

@@ -2,7 +2,7 @@
 title: Troubleshoot with Diagnostics
 description: Learn how to troubleshoot problems with your app in Azure App Service by using the diagnostics tool in the Azure portal. 
 keywords: app service, azure app service, diagnostics, support, web app, troubleshooting, self-help
-ms.topic: conceptual
+ms.topic: overview
 ms.date: 04/23/2025
 ms.update-cycle: 1095-days
 ms.author: msangapu