Merge pull request #313233 from cdpark/refresh-apicenter-march6

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

Author: v-shils

articles/api-management/media/websocket-api/onhandshake-screen.png

@@ -1,5 +1,5 @@
 ---
-title: Import an SAP API by Using the Azure portal | Microsoft Docs
+title: Import SAP OData Metadata as an API
 titleSuffix:
 description: Learn how to import OData metadata from SAP as an API to Azure API Management, either directly or by converting the metadata to an OpenAPI specification.
 ms.service: azure-api-management
@@ -8,7 +8,7 @@ ms.custom:
 author: martinpankraz
 ms.author: mapankra
 ms.topic: how-to
-ms.date: 03/31/2025
+ms.date: 03/16/2026
 
 #customer intent: As an API developer, I want to import an SAP API to API Management.
 ---
@@ -17,9 +17,9 @@ ms.date: 03/31/2025
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-This article describes how to import an OData service by using its metadata description. [SAP Gateway Foundation](https://help.sap.com/viewer/product/SAP_GATEWAY) is used as an example. 
+This article describes how to import an OData (Open Data Protocol) service into Azure API Management by using OData metadata. The following example uses [SAP Gateway Foundation](https://help.sap.com/docs/SAP_GATEWAY).
 
-In this article, you: 
+In this article, you learn how to: 
 > [!div class="checklist"]
 > * Retrieve OData metadata from your SAP service
 > * Import OData metadata to Azure API Management, either directly or after converting it to an OpenAPI specification
@@ -28,12 +28,12 @@ In this article, you:
 
 ## Prerequisites
 
-- An API Management instance. If you don't have one, complete the steps in  [Create an API Management instance by using the Azure portal](get-started-create-service-instance.md).
+- Create an [API Management instance](get-started-create-service-instance.md).
 - An SAP system and service that's exposed as OData v2 or v4. 
 - If your SAP backend uses a self-signed certificate (for testing), you might need to disable the verification of the trust chain for SSL. To do so, configure a [backend](backends.md) in your API Management instance:
-    1. In the Azure portal, under **APIs**, select **Backends** > **+ Add**.
-    1.  Add a **Custom URL** that points to the SAP backend service.
-    1.  Clear the **Validate certificate chain** and **Validate certificate name** checkboxes. 
+    1. In the Azure portal, under **APIs**, select **Backends** > **+ Create new backend**.
+    1. Add a **Custom URL** that points to the SAP backend service.
+    1. Expand the **Advanced** section, then clear the **Validate certificate chain** and **Validate certificate name** checkboxes. 
 
     > [!NOTE]
     > In production scenarios, use proper certificates for end-to-end SSL verification.
@@ -42,10 +42,8 @@ In this article, you:
 
 Use one of the following methods to retrieve metadata XML from your SAP service. If you plan to convert the metadata XML to an OpenAPI specification, save the file locally. 
 
-* Use the SAP Gateway Client (transaction `/IWFND/GW_CLIENT`).  
-  or
-* Make a direct HTTP call to retrieve the XML:
-`http://<OData server URL>:<port>/<path>/$metadata`.
+* Use the SAP Gateway Client (transaction `/IWFND/GW_CLIENT`).
+* Make a direct HTTP call to retrieve the XML: `http://<OData server URL>:<port>/<path>/$metadata`.
 
 [!INCLUDE [api-management-navigate-to-instance](../../includes/api-management-navigate-to-instance.md)]
 
@@ -63,7 +61,7 @@ Choose one of the following methods to import your API to API Management:
 
 ## Convert OData metadata to OpenAPI JSON
 
-1. Convert the OData XML to OpenAPI JSON format. Use an OASIS open-source tool for [OData v2](https://github.com/oasis-tcs/odata-openapi/tree/main/tools) or [OData v4](https://github.com/oasis-tcs/odata-openapi/tree/main/lib), depending on your metadata XML. 
+1. Use an OASIS open-source tool for [OData v2](https://github.com/oasis-tcs/odata-openapi/tree/main/tools) or [OData v4](https://github.com/oasis-tcs/odata-openapi/tree/main/lib), depending on your metadata XML. 
 
    The following example converts OData v2 XML for the test service `epm_ref_apps_prod_man_srv`:
 
@@ -77,16 +75,17 @@ Choose one of the following methods to import your API to API Management:
     > * For testing with a single XML file, you can use a [web-based converter](https://aka.ms/ODataOpenAPI) that's based on an open-source tool.
     > * With the tool or the web-based converter, specifying the \<IP address>:\<port> of your SAP OData server is optional. Alternatively, add this information later in your generated OpenAPI specification or after you import the file to API Management.
 
-1. Save the `openapi-spec.json` file locally for import to API Management.
+1. Save the *openapi-spec.json* file locally for import to API Management.
 
 ## Import OpenAPI specification
 
-1. In the left navigation pane, in the **APIs** section, select **APIs**.
-1. Under **Create a new definition**, select **OpenAPI**:
+1. In the sidebar menu, in the **APIs** section, select **APIs**.
+
+1. Under **Create from definition**, select the **OpenAPI** tile:
 
     :::image type="content" source="./media/import-api-from-oas/oas-api.png" alt-text="Screenshot that shows the OpenAPI tile.":::
 
-1. Click **Select a file**, and then select the `openapi-spec.json` file that you saved locally in a previous step.
+1. Choose **Select a file**, and then select the *openapi-spec.json* file that you saved locally in a previous step.
 
 1. Enter API settings. You can set these values when you import the API or configure them later by going to the **Settings** tab. 
     * For the **API URL suffix**, we recommend using the same URL path as that of the original SAP service.
@@ -100,7 +99,7 @@ Choose one of the following methods to import your API to API Management:
 
 ## Complete the API configuration
 
-[Add](add-api-manually.md#add-and-test-an-operation) the following three operations to the API that you imported:
+Add the following three operations to the API that you imported. To learn how, see [Add and test an operation](add-api-manually.md#add-and-test-an-operation).
 
 - `GET /$metadata`
 
@@ -122,23 +121,28 @@ Choose one of the following methods to import your API to API Management:
 
     Operation  |Description  |Additional configuration for the operation  |
     |---------|---------|---------|
-    |`GET /`     |   Enables policy configuration at the service root.   |    Configure the following inbound [rewrite-uri](rewrite-uri-policy.md) policy to append a trailing slash to requests that are forwarded to the service root:<br/><br>    `<rewrite-uri template="/" copy-unmatched-params="true" />` <br/><br/>This policy removes potential ambiguity among requests with and without trailing slashes. These two types of requests are treated differently by some backends.|
+    |`GET /`     |   Enables policy configuration at the service root.   |    Configure the following inbound [rewrite-uri](rewrite-uri-policy.md) policy to append a trailing slash to requests that are forwarded to the service root:<br/><br> `<rewrite-uri template="/" copy-unmatched-params="true" />` <br/><br/>This policy removes potential ambiguity among requests with and without trailing slashes. These two types of requests are treated differently by some backends.|
 
     :::image type="content" source="media/sap-api/get-root-operation.png" alt-text="Screenshot that shows the GET operation for the service root.":::
 
-You also need to configure authentication to your backend by using an appropriate method for your environment. For examples, see [API Management authentication and authorization policies](api-management-policies.md#authentication-and-authorization).
+You also need to configure authentication to your backend by using an appropriate method for your environment. For examples, see [Authentication and authorization](api-management-policies.md#authentication-and-authorization).
 
 ## Test your API
 
 1. Navigate to your API Management instance.
-1. In the left navigation pane, in the **APIs** section, select **APIs**.
+
+1. In the sidebar menu, select **APIs** > **APIs**.
+
 1. Under **All APIs**, select your imported API.
+
 1. Select the **Test** tab to access the test console. 
+
 1. Select an operation, enter any required values, and then select **Send**. 
 
     For example, test the `GET /$metadata` call to verify connectivity to the SAP backend.
 
 1. View the response. To troubleshoot, [trace](api-management-howto-api-inspector.md) the call.
+
 1. When you're done testing, exit the test console.
 
 ---
@@ -148,7 +152,7 @@ You also need to configure authentication to your backend by using an appropriat
 * See an [example end-to-end scenario](https://community.powerplatform.com/blogs/post/?postid=c6a609ab-3556-ef11-a317-6045bda95bf0) for integrating API Management with an SAP gateway.
 * Control access to an SAP backend by using API Management policies. For example, if the API is imported as an OData API, use the [validate OData request](validate-odata-request-policy.md) policy. There are also policy snippets for [SAP principal propagation for SAP ECC or S/4HANA](https://github.com/Azure/api-management-policy-snippets/blob/master/examples/Request%20OAuth2%20access%20token%20from%20SAP%20using%20AAD%20JWT%20token.xml) or [SAP SuccessFactors](https://github.com/Azure/api-management-policy-snippets/blob/master/examples/Request%20OAuth2%20access%20token%20from%20SuccessFactors%20using%20AAD%20JWT%20token.xml) and [fetching an X-CSRF token](https://github.com/Azure/api-management-policy-snippets/blob/master/examples/Get%20X-CSRF%20token%20from%20SAP%20gateway%20using%20send%20request.policy.xml).
 * For guidance on deploying, managing, and migrating APIs at scale, see:
-    * [Automated API deployments with APIOps](/azure/architecture/example-scenario/devops/automated-api-deployments-apiops).
-    * [CI/CD for API Management using Azure Resource Manager templates](devops-api-development-templates.md).
+    * [Automated API deployments with APIOps](/azure/architecture/example-scenario/devops/automated-api-deployments-apiops)
+    * [Use DevOps and CI/CD to publish APIs](devops-api-development-templates.md)
 
 [!INCLUDE [api-management-define-api-topics.md](../../includes/api-management-define-api-topics.md)]

articles/api-management/media/websocket-api/query-gateway-logs.png

@@ -1,11 +1,11 @@
 ---
-title: Tutorial - Import and manage APIs - Azure API Management and VS Code
+title: "Tutorial: Use VS Code to Import and Manage APIs in Azure API Management"
 description: Learn how to use the Azure API Management extension for Visual Studio Code to import, test, and manage APIs.
 ms.service: azure-api-management
 author: dlepow
 ms.author: danlep
 ms.topic: tutorial
-ms.date: 02/20/2025
+ms.date: 03/16/2026
 ms.custom:
   - devdivchpfy22
   - sfi-image-nochange
@@ -15,40 +15,43 @@ ms.custom:
 
 [!INCLUDE [api-management-availability-premium-dev-standard-basic-consumption](../../includes/api-management-availability-premium-dev-standard-basic-consumption.md)]
 
-In this tutorial, you learn how to use the API Management extension for Visual Studio Code for common operations in API Management. Use the familiar Visual Studio Code environment to import, update, test, and manage APIs.
+In this tutorial, you learn how to use the Azure API Management extension for Visual Studio Code for common operations in API Management. You can use the familiar Visual Studio Code environment to import, update, test, and manage APIs.
 
 [!INCLUDE [api-management-workspace-availability](../../includes/api-management-workspace-availability.md)]
 
-You learn how to:
+In this article, you learn how to: 
 
 > [!div class="checklist"]
 > * Import an API into API Management
 > * Edit the API
 > * Apply API Management policies
 > * Test the API
 
-:::image type="content" source="media/visual-studio-code-tutorial/tutorial-api-result.png" alt-text="Screenshot of API in API Management extension.":::
+:::image type="content" source="media/visual-studio-code-tutorial/tutorial-api-result.png" alt-text="Screenshot of API in API Management extension." lightbox="media/visual-studio-code-tutorial/tutorial-api-result.png":::
 
-For an introduction to more API Management features, see the API Management tutorials using the [Azure portal](import-and-publish.md).
+For an introduction to more API Management features, see [Import and publish your first API](import-and-publish.md).
 
 ## Prerequisites
 
 * Understand [Azure API Management terminology](api-management-terminology.md).
-* Ensure you've installed [Visual Studio Code](https://code.visualstudio.com/) and the latest [Azure API Management extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-apimanagement&ssr=false#overview).
-* [Create an API Management instance](vscode-create-service-instance.md).
+* Install [Visual Studio Code](https://code.visualstudio.com) and the latest [Azure API Management extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-apimanagement&ssr=false#overview).
+* Create an [API Management instance](vscode-create-service-instance.md).
 
 ## Import an API
 
-The following example imports an OpenAPI Specification in JSON format into API Management. For this example, you import the open source [Petstore API](https://petstore.swagger.io/).
+The following example imports an OpenAPI Specification in JSON format into API Management. For this example, you import the open source [Petstore API](https://petstore.swagger.io).
 
 1. In Visual Studio Code, select the Azure icon from the Activity Bar.
+
 1. In the Explorer pane, expand the API Management instance you created.
+
 1. Right-click **APIs**, and select **Import from OpenAPI Link**.
+
 1. When prompted, enter the following values:
     1. An **OpenAPI link** for content in JSON format. For this example: `https://petstore.swagger.io/v2/swagger.json`.
 
         This file specifies the backend service that implements the example API and the operations it supports.
-    1. An **API name**, such as *petstore*, that is unique in the API Management instance. This name can contain only letters, number, and hyphens. The first and last characters must be alphanumeric. This name is used in the path to call the API.
+    1. An **API name**, such as *petstore*, that's unique in the API Management instance. This name can contain only letters, number, and hyphens. The first and last characters must be alphanumeric. This name is used in the path to call the API.
 
 After the API is imported successfully, it appears in the Explorer pane, and available API operations appear under the **Operations** node.
 
@@ -58,10 +61,10 @@ After the API is imported successfully, it appears in the Explorer pane, and ava
 
 You can edit the API in Visual Studio Code. For example, edit the Resource Manager JSON description of the API in the editor window to remove the **http** protocol used to access the API, which is highlighted in the following snip:
 
-:::image type="content" source="media/visual-studio-code-tutorial/import-demo-api.png" alt-text="Screenshot of editing JSON description in Visual Studio Code.":::
-
 To edit the OpenAPI format, right-click the API name in the Explorer pane and select **Edit OpenAPI**. Make your changes, and then select **File** > **Save**.
 
+:::image type="content" source="media/visual-studio-code-tutorial/import-demo-api.png" alt-text="Screenshot of editing JSON description in Visual Studio Code.":::
+
 ## Apply policies to the API
 
 API Management provides [policies](api-management-policies.md) that you can configure for your APIs. Policies are a collection of statements. These statements are run sequentially on the request or response of an API. Policies can be global, which apply to all APIs in your API Management instance, or specific to a product, an API, or an API operation.
@@ -89,7 +92,7 @@ This section shows how to apply common inbound and outbound policies to your API
     </policies>
     ```
 
-    * The `rate-limit` policy in the `inbound` section limits the number of calls to the API to 3 every 15 seconds.
+    * The `rate-limit` policy in the `inbound` section limits the number of calls to the API to 3 calls every 15 seconds.
     * The `set-header` policy in the `outbound` section adds a custom response header for demonstration purposes.
 
 1. Save the file. If you're prompted, select **Upload** to upload the file to the cloud.
@@ -103,6 +106,7 @@ To test the API, get a subscription key and then make a request to the API Manag
 You need a subscription key for your API Management instance to test the imported API and the policies that are applied.
 
 1. In the Explorer pane, right-click the name of your API Management instance.
+
 1. Select **Copy Subscription Key**. This key is for the built-in all access subscription that is created when you create an API Management instance.
 
     :::image type="content" source="media/visual-studio-code-tutorial/copy-subscription-key-1.png" alt-text="Screenshot of Copy subscription Key command in Visual Studio Code.":::
@@ -113,12 +117,16 @@ You need a subscription key for your API Management instance to test the importe
 ### Test an API operation
 
 1. In the Explorer pane, expand the **Operations** node under the *petstore* API that you imported.
+
 1. Select an operation such as *[GET] Find pet by ID*, and then right-click the operation and select **Test Operation**.
+
 1. In the editor window, substitute `5` for the `petId` parameter in the request URL.
+
 1. In the editor window, next to **Ocp-Apim-Subscription-Key**, paste the subscription key that you copied.
+
 1. Select **Send request**.
 
-:::image type="content" source="media/visual-studio-code-tutorial/test-api.png" alt-text="Screenshot of sending API request from Visual Studio Code.":::
+    :::image type="content" source="media/visual-studio-code-tutorial/test-api.png" alt-text="Screenshot of sending API request from Visual Studio Code.":::
 
 When the request succeeds, the backend responds with **200 OK** and some data.
 
@@ -140,18 +148,13 @@ For steps to enable tracing for an API, see [Enable tracing for an API](api-mana
 
 When no longer needed, remove the API Management instance by right-clicking and selecting **Open in Portal** to [delete the API Management service](get-started-create-service-instance.md#clean-up-resources) and its resource group.
 
-Alternately, you can select **Delete API Management** to only delete the API Management instance (this operation doesn't delete its resource group).
+Alternately, you can select **Delete API Management** to only delete the API Management instance. This operation doesn't delete its resource group.
 
 :::image type="content" source="media/visual-studio-code-tutorial/vscode-apim-delete-1.png" alt-text="Screenshot of deleting API Management instance from Visual Studio Code.":::
 
 ## Related content
 
-This tutorial introduced several features of the API Management extension for Visual Studio Code. You can use these features to import and manage APIs. You learned how to:
-
-> [!div class="checklist"]
-> * Import an API into API Management
-> * Edit the API
-> * Apply API Management policies
-> * Test the API
+The API Management extension provides more features to work with your APIs, such as:
 
-The API Management extension provides more features to work with your APIs. For example, [debug polices](api-management-debug-policies.md) (available in the Developer service tier), or create and manage [named values](api-management-howto-properties.md).
+- [Create, understand, and debug Azure API Management policies](api-management-debug-policies.md) (available in the Developer service tier)
+- [Use named values in Azure API Management policies](api-management-howto-properties.md)