Merge pull request #313138 from cdpark/refresh-apicenter-march5

Feature 551038: Q&M: Content Freshness for API Center - March 5

Author: v-dirichards

articles/api-management/media/mock-api-responses/http-api.png

@@ -1,11 +1,11 @@
 ---
-title: Tutorial - Mock API responses in API Management - Azure portal  | Microsoft Docs
-description: Use Azure API Management to set a policy on an API. The policy returns a mock response even if the backend isn't available to send real responses.
+title: "Tutorial: Mock API Responses in API Management"
+description: Use Azure API Management to set a policy on an API to return a mock response even if the backend isn't available to send real responses.
 
 author: dlepow
 ms.service: azure-api-management
 ms.topic: tutorial
-ms.date: 03/24/2025
+ms.date: 03/12/2026
 ms.author: danlep
 ms.custom:
   - mvc
@@ -21,20 +21,20 @@ ms.custom:
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-Backend APIs are imported into an Azure API Management API or created and managed manually. The steps in this tutorial describe how to:
+Backend APIs can be imported into an Azure API Management API or created and managed manually. The steps in this tutorial describe how to:
 
 + Use API Management to create a blank HTTP API.
 + Manually manage an HTTP API.
 + Set a policy on an API so that it returns a mock response.
 
-This method enables developers to continue with the implementation and testing of the API Management instance even if the backend isn't available to send real responses.
+This method allows developers to continue with the implementation and testing of the API Management instance even if the backend isn't available to send real responses.
 
 [!INCLUDE [api-management-workspace-try-it](../../includes/api-management-workspace-try-it.md)]
 
 The ability to create mock responses is useful in many scenarios:
 
-+ When the API façade is designed first and the backend implementation occurs later, or when the backend is being developed in parallel.
-+ When the backend is temporarily not operational or is not able to scale.
++ When the API gateway is designed first and the backend implementation occurs later, or when the backend is being developed in parallel.
++ When the backend is temporarily not operational or isn't able to scale.
 
 In this tutorial, you learn how to:
 
@@ -56,15 +56,20 @@ In this tutorial, you learn how to:
 
 The steps in this section show how to create an HTTP API with no backend.
 
-1. Sign in to the Azure portal, and then navigate to your API Management instance.
-1. Select **APIs** > **+ Add API** > **HTTP** tile:
+1. Sign in to the [Azure portal](https://portal.azure.com/), and then navigate to your API Management instance.
+
+1. In the sidebar menu, select **APIs** > **APIs**, and then select **+ Add API**. Choose the **HTTP** tile:
 
    :::image type="content" source="media/mock-api-responses/http-api.png" alt-text="Screenshot that shows the first steps for defining an API." lightbox="media/mock-api-responses/http-api.png":::
 
 1. In the **Create an HTTP API** window, select **Full**.
-1. In **Display name**, enter *Test API*.
+
+1. In **Display name**, enter *Test API*. The **Name** field fills automatically.
+
 1. In **Products**, select *Unlimited*, if that value is available. This value is available only in some tiers. You can leave the value blank for this tutorial, but you need to associate the API with a product to publish it. For more information, see [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api). 
+
 1. In **Gateways**, select **Managed** if this option is available. (This option is available only in certain service tiers.)
+
 1. Select **Create**.
 
     :::image type="content" source="media/mock-api-responses/create-http-api.png" alt-text="Screenshot that shows the Create an HTTP API window." lightbox="media/mock-api-responses/create-http-api.png":::
@@ -76,26 +81,33 @@ An API exposes one or more operations. In this section, you add an operation to
 ### [Portal](#tab/azure-portal)
 
 1. Select the API that you created in the previous step.
+
 1. Select **+ Add Operation**.
+
 1. In the **Frontend** window, enter the following values:
 
-     | Setting             | Value         | Description   |
-    |------|------|-----------------------------------------|
-    | **Display name**    | *Test call*  | The name that's displayed in the [developer portal](api-management-howto-developer-portal.md).    |
+    | Setting          | Value         | Description     |
+    |------------------|---------------|-----------------|
+    | **Display name**    | *Test call*  | The name displayed in the [developer portal](api-management-howto-developer-portal.md). |
+    | **Name**    | *test-call*  | This field fills automatically. |
     | **URL** (first box) | GET | Select one of the predefined HTTP verbs.    |
     | **URL**  (second box)| */test*   | A URL path for the API.            |
-    | **Description** |   |  An optional description of the operation. It provides documentation in the developer portal to the developers who use the API.                         |
+    | **Description** |   |  An optional description of the operation. It provides documentation in the developer portal to the developers who use the API.    |
 
     :::image type="content" source="media/mock-api-responses/frontend-window.png" alt-text="Screenshot that shows the Frontend window." lightbox="media/mock-api-responses/frontend-window.png":::
 
-1. Select the **Responses** tab, which  is located under the **URL**, **Display name**, and **Description** boxes. You'll enter values on this tab to define response status codes, content types, examples, and schemas.
+1. Select the **Responses** tab, which  is located under the **URL**, **Display name**, and **Description** boxes. Enter values on this tab to define response status codes, content types, examples, and schemas.
+
 1. Select **+ Add response**, and then select **200 OK** from the list.
 
     :::image type="content" source="media/mock-api-responses/add-response.png" alt-text="Screenshot that shows the Responses tab." lightbox="media/mock-api-responses/add-response.png":::
 
 1. In the **Representations** section, select **+ Add representation**.
+
 1. Enter *application/json* into the search box and then select the **application/json** content type.
+
 1. In the **Sample** box, enter  `{ "sampleField" : "test" }`.
+
 1. Select **Save**.
 
     :::image type="content" source="media/mock-api-responses/add-representation.png" alt-text="Screenshot that shows the Representations section." lightbox="media/mock-api-responses/add-representation.png":::
@@ -105,7 +117,7 @@ Although it's not required for this example, you can configure more settings for
 |Tab      |Description  |
 |---------|---------|
 |**Query**     |  Add query parameters. Besides providing a name and description, you can also provide values that are assigned to a query parameter. You can mark one of the values as default (optional).        |
-|**Request**     |  Define request content types, examples, and schemas.       |
+|**Request**   |  Define request content types, examples, and schemas.       |
 
 ### [Azure CLI](#tab/azure-cli)
 
@@ -141,8 +153,11 @@ az apim api operation delete --resource-group <resource-group-name> \
 ## Enable response mocking
 
 1. Select the API you created in [Create a test API](#create-a-test-api).
+
 1. Ensure that the **Design** tab is selected.
-1. Select the test operation that you added.
+
+1. Select the **Test call** operation that you added.
+
 1. In the **Inbound processing** section, select **+ Add policy**.
 
     :::image type="content" source="media/mock-api-responses/add-policy.png" alt-text="Screenshot that shows the first steps for enabling response mocking." lightbox="media/mock-api-responses/add-policy.png" :::
@@ -158,11 +173,12 @@ az apim api operation delete --resource-group <resource-group-name> \
 1. Select **Save**.
 
     > [!TIP]
-    > A yellow bar displaying the text **Mocking is enabled** appears. This message indicates that the responses returned from API Management are mocked by the [mocking policy](mock-response-policy.md) and aren't produced by the backend.
+    > A yellow bar displaying the text **Mocking is enabled** appears. This message indicates that the responses returned from API Management are issued by the [mocking policy](mock-response-policy.md) and aren't produced by the backend.
 
 ## Test the mocked API
 
 1. Select the API you created in [Create a test API](#create-a-test-api).
+
 1. On the **Test** tab, ensure that the **Test call** API is selected, and then select **Send** to make a test call:
 
    :::image type="content" source="media/mock-api-responses/test-mock-api.png" alt-text="Screenshot that shows the steps for testing the mocked API." lightbox="media/mock-api-responses/test-mock-api.png":::
@@ -173,7 +189,5 @@ az apim api operation delete --resource-group <resource-group-name> \
 
 ## Next step
 
-Go to the next tutorial:
-
 > [!div class="nextstepaction"]
 > [Transform and protect a published API](transform-api.md)

articles/api-management/media/mock-api-responses/mock-api-response-02.png

@@ -1,18 +1,18 @@
 ---
-title: Import a SOAP API to Azure API Management and convert it to REST using the portal | Microsoft Docs
-description: Learn how to import a SOAP API into Azure API Management as a WSDL specification and convert it to a REST API. Then test the API in the Azure portal.
+title: Import a SOAP API into API Management and Convert it to REST
+description: Learn how to import a SOAP API into Azure API Management as a WSDL specification and convert it to a REST API.
 services: api-management
 author: dlepow
 ms.custom: devdivchpfy22
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 03/27/2025
+ms.date: 03/13/2026
 ms.author: danlep
 
 #customer intent: As a developer, I want to import a SOAP API into API Management and convert it to REST.
 
 ---
-# Import a SOAP API to API Management and convert it to REST
+# Import a SOAP API into Azure API Management and convert it to REST
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
@@ -28,37 +28,42 @@ In this article, you learn how to:
 
 ## Prerequisites
 
-- Complete the quickstart [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)]
 
 ## <a name="create-api"> </a>Import and publish a backend API
 
-1. In the left pane, in the **APIs** section, select **APIs**.
+1. In the sidebar menu, in the **APIs** section, select **APIs**.
+
 1. On the APIs page, select **+ Add API**.
-1. Under **Create from definition**, select **WSDL**:
+
+1. Under **Create from definition**, select the **WSDL** tile:
 
     :::image type="content" source="./media/restify-soap-api/wsdl-api.png" alt-text="Screenshot that shows the WSDL tile in the Azure portal.":::
 
-1. In **WSDL specification**, enter the URL to your SOAP API, or click **Select a file** to select a local WSDL file.
-1. Under **Import method**, select **SOAP to REST**. 
+1. In **WSDL specification**, enter the URL to your SOAP API, or choose **Select a file** to select a local WSDL file.
+
+1. Under **Import method**, select **SOAP to REST**.
+
     When this option is selected, API Management attempts to make an automatic transformation between XML and JSON. In this case, consumers should call the API as a RESTful API, which returns JSON. API Management converts each request to a SOAP call.
 
     :::image type="content" source="./media/restify-soap-api/soap-to-rest.png" alt-text="Screenshot that shows the SOAP to REST option." lightbox="./media/restify-soap-api/soap-to-rest.png":::
 
 1. The **Display name** and **Name** boxes are filled automatically with information from the SOAP API. 
-   
-   **Display name**, **URL**, and **Description** information is automatically entered for operations. Operations also receive a system-generated **Name**.
+
 1. Enter other API settings, and then select **Create**. You can also configure these values later by going to the **Settings** tab. 
 
-    For more information about API settings, see [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api).
+    For more information about API settings, see [Import and publish a backend API](import-and-publish.md#import-and-publish-a-backend-api).
 
 ## Test the new API in the Azure portal
 
 You can call operations directly from the Azure portal. This method provides a convenient way to view and test the operations of an API.  
 
 1. Select the API you created in the previous step.
+
 1. Select the **Test** tab.
+
 1. Select an operation.
 
     The page shows fields for query parameters and fields for the headers. One of the headers is **Ocp-Apim-Subscription-Key**. This header is for the subscription key of the product that's associated with this API. If you created the API Management instance, you're an admin already, so the key is filled in automatically.