Merge pull request #306609 from v-thpra/ff-488533-azure-apimgmt-005b

Freshness - Azure API Management Center - 005

Author: AnnaMHuff

articles/api-management/enable-cors-power-platform.md

@@ -1,12 +1,12 @@
 ---
-title: Enable CORS policies for Azure API Management custom connector 
+title: Enable CORS Policies for Azure API Management Custom Connector 
 description: How to enable CORS policies in Azure API Management and Power Platform to test and use a custom connector from Power Platform applications.
 services: api-management
 author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 03/24/2023
+ms.date: 10/07/2025
 ms.author: danlep
 
 ---
@@ -16,16 +16,15 @@ ms.author: danlep
 
 Cross-origin resource sharing (CORS) is an HTTP-header based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources. Customers can add a [CORS policy](cors-policy.md) to their web APIs in Azure API Management, which adds cross-origin resource sharing support to an operation or an API to allow cross-domain calls from browser-based clients.
 
-If you've exported an API from API Management as a [custom connector](export-api-power-platform.md) in the Power Platform and want to use browser-based clients including Power Apps or Power Automate to call the API, you need to configure your API to explicitly enable cross-origin requests from Power Platform applications. This article shows you how to configure the following two necessary policy settings:
+If you export an API from API Management as a [custom connector](export-api-power-platform.md) in the Power Platform and want to use browser-based clients including Power Apps or Power Automate to call the API, you need to configure your API to explicitly enable cross-origin requests from Power Platform applications. This article shows you how to configure the following two necessary policy settings:
 
-* Add a CORS policy to your API
-
-* Add a policy to your custom connector that sets an Origin header on HTTP requests
+- Add a CORS policy to your API
+- Add a policy to your custom connector that sets an Origin header on HTTP requests
 
 ## Prerequisites 
 
-+ Complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md)
-+ Export an API from your API Management instance to a Power Platform environment as a [custom connector](export-api-power-platform.md)
+- Complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md)
+- Export an API from your API Management instance to a Power Platform environment as a [custom connector](export-api-power-platform.md)
 
 ## Add CORS policy to API in API Management
 
@@ -38,14 +37,14 @@ Follow these steps to configure the CORS policy in API Management.
     1. Add the following **Allowed origin**: `https://make.powerapps.com`.
     1. Select **Save**.
 
-* For more information about configuring a policy, see [Set or edit policies](set-edit-policies.md).
-* For details about the CORS policy, see the [cors](cors-policy.md) policy reference.
+- For more information about configuring a policy, see [Set or edit policies](set-edit-policies.md).
+- For details about the CORS policy, see the [cors](cors-policy.md) policy reference.
 
 > [!NOTE]
 > If you already have an existing CORS policy at the service (all APIs) level to enable the test console of the developer portal, you can add the `https://make.powerapps.com` origin to that policy instead of configuring a separate policy for the API or operation. 
 
 > [!NOTE]
-> Depending on how the custom connector gets used in Power Platform applications, you might need to configure additional origins in the CORS policy. If you experience CORS problems when running Power Platform applications, use developer tools in your browser, tracing in API Management, or Application Insights to investigate the issues.
+> Depending on how the custom connector gets used in Power Platform applications, you might need to configure more origins in the CORS policy. If you experience CORS problems when running Power Platform applications, use developer tools in your browser, tracing in API Management, or Application Insights to investigate the issues.
 
 
 ## Add policy to custom connector to set Origin header
@@ -57,7 +56,7 @@ For details about editing settings of a custom connector, see [Create a custom c
 1. Sign in to Power Apps or Power Automate.
 1. On the left pane, select **Data** > **Custom Connectors**. 
 1. Select your connector from the list of custom connectors.
-1. Select the pencil (Edit) icon to edit the custom connector. 
+1. To edit the custom connector, select the pencil (Edit) icon. 
 1. Select **3. Definition**.
 1. In **Policies**, select **+ New policy**. Select or enter the following policy details.
 
@@ -79,5 +78,5 @@ For details about editing settings of a custom connector, see [Create a custom c
 
 ## Related content
 
-* [Learn more about the Power Platform](https://powerplatform.microsoft.com/)
-* [Learn more about creating and using custom connectors](/connectors/custom-connectors/)
+- [Learn more about the Power Platform](https://powerplatform.microsoft.com/)
+- [Learn more about creating and using custom connectors](/connectors/custom-connectors/)

articles/api-management/export-api-power-platform.md

@@ -1,12 +1,12 @@
 ---
 title: Export APIs from Azure API Management to Microsoft Power Platform | Microsoft Docs
-description: Learn how to export an API from API Management as a custom connector to Power Apps and Power Automate in the Microsoft Power Platform.
+description: Learn how to export an API from API Management to the Microsoft Power Platform Copilot Studio, Power Apps, and Power Automate as a custom connector.
 services: api-management
 author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 03/24/2023
+ms.date: 10/07/2025
 ms.author: danlep
 ms.custom: engagement-fy23
 ---
@@ -15,14 +15,15 @@ ms.custom: engagement-fy23
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-Citizen developers using the Microsoft [Power Platform](https://powerplatform.microsoft.com) often need to reach the business capabilities that are developed by professional developers and deployed in Azure. [Azure API Management](https://aka.ms/apimrocks) enables professional developers to publish their backend service as APIs, and easily export these APIs to the Power Platform ([Copilot Studio](/microsoft-copilot-studio/fundamentals-what-is-copilot-studio), [Power Apps](/powerapps/powerapps-overview) and [Power Automate](/power-automate/getting-started)) as custom connectors for discovery and consumption by citizen developers. 
+Citizen developers using the Microsoft [Power Platform](https://powerplatform.microsoft.com) often need to reach the business capabilities developed and deployed by professional developers in Azure. [Azure API Management](https://aka.ms/apimrocks) enables professional developers to publish their backend service as APIs, and easily export these APIs to the Power Platform ([Copilot Studio](/microsoft-copilot-studio/fundamentals-what-is-copilot-studio), [Power Apps](/powerapps/powerapps-overview), and [Power Automate](/power-automate/getting-started)) as custom connectors for discovery and consumption by citizen developers. 
 
 This article walks through the steps in the Azure portal to create a Power Platform [custom connector](/connectors/custom-connectors/) to an API in API Management. With this capability, citizen developers can use the Power Platform to create and distribute apps that are based on internal and external APIs managed by API Management.
+
 ## Prerequisites
 
-+ Complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md)
-+ Make sure there's an API in your API Management instance that you'd like to export to the Power Platform
-+ Make sure you have a Power Apps or Power Automate [environment](/powerapps/powerapps-overview#power-apps-for-admins) 
+- Complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md)
+- Make sure there's an API in your API Management instance that you'd like to export to the Power Platform
+- Make sure you have a Power Apps or Power Automate [environment](/powerapps/powerapps-overview#power-apps-for-admins) 
 
 ## Create a custom connector to an API
 
@@ -32,14 +33,14 @@ This article walks through the steps in the Azure portal to create a Power Platf
 1. In the **Create a connector** window, do the following:
     1. Select an API to publish to the Power Platform.
     1. Select a Power Platform environment to publish the API to. 
-    1. Enter a display name, which will be used as the name of the custom connector.  
+    1. Enter a display name, which is used as the name of the custom connector.  
     1. Optionally, if the API doesn't already require a subscription, select **Create subscription key connection parameter**.
     1. Optionally, if the API is [protected by an OAuth 2.0 server](api-management-howto-protect-backend-with-aad.md), provide details including **Client ID**, **Client secret**, **Authorization URL**, **Token URL**, and **Refresh URL**.  
 1. Select **Create**. 
 
     :::image type="content" source="media/export-api-power-platform/create-custom-connector.png" alt-text="Create custom connector to API in API Management":::
 
-Once the connector is created, navigate to your [Power Apps](https://make.powerapps.com) or [Power Automate](https://make.powerautomate.com) environment. You'll see the API listed under **Data > Custom Connectors**.
+Once the connector is created, navigate to your [Power Apps](https://make.powerapps.com) or [Power Automate](https://make.powerautomate.com) environment. Your API is listed under **Data > Custom connectors**.
 
 :::image type="content" source="media/export-api-power-platform/custom-connector-power-app.png" alt-text="Custom connector in Power Platform":::
 
@@ -63,11 +64,10 @@ From API Management, you can update a connector to target a different API or Pow
 1. Select **Update a connector**.
 1. Select the API you want to update the connector for, update settings as needed, and select **Update**.
 
-
 ## Related content
 
-* [Learn more about the Power Platform](https://powerplatform.microsoft.com/) and [licensing](/power-platform/admin/pricing-billing-skus)
-* [Learn more about creating and using custom connectors](/connectors/custom-connectors/)
-* [Learn common tasks in API Management by following the tutorials](./import-and-publish.md)
+- [Learn more about the Power Platform](https://powerplatform.microsoft.com/) and [licensing](/power-platform/admin/pricing-billing-skus)
+- [Learn more about creating and using custom connectors](/connectors/custom-connectors/)
+- [Learn common tasks in API Management by following the tutorials](./import-and-publish.md)
 
 

articles/api-management/how-to-deploy-self-hosted-gateway-azure-kubernetes-service.md

@@ -1,18 +1,18 @@
 ---
-title: Deploy a self-hosted gateway to Azure Kubernetes Service
-description: Learn how to deploy self-hosted gateway component of Azure API Management to Azure Kubernetes Service
+title: Deploy a Self-Hosted Gateway to Azure Kubernetes Service
+description: Learn how to deploy self-hosted gateway component of Azure API Management to Azure Kubernetes Service.
 author: dlepow
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 06/11/2021
+ms.date: 10/07/2025
 ms.author: danlep
 ---
 
 # Deploy an Azure API Management self-hosted gateway to Azure Kubernetes Service
 
 [!INCLUDE [api-management-availability-premium-dev](../../includes/api-management-availability-premium-dev.md)]
 
-This article provides the steps for deploying self-hosted gateway component of Azure API Management to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/). For deploying self-hosted gateway to a Kubernetes cluster, see the how-to article for deployment by using a [deployment YAML file](how-to-deploy-self-hosted-gateway-kubernetes.md) or [with Helm](how-to-deploy-self-hosted-gateway-kubernetes-helm.md).
+This article provides the steps for deploying self-hosted gateway component of Azure API Management to [Azure Kubernetes Service (AKS)](https://azure.microsoft.com/services/kubernetes-service/). For deploying self-hosted gateway to a Kubernetes cluster, see the how-to article for deployment by using a [deployment YAML file](how-to-deploy-self-hosted-gateway-kubernetes.md) or with [Helm](how-to-deploy-self-hosted-gateway-kubernetes-helm.md).
 
 > [!NOTE]
 > You can also deploy self-hosted gateway to an [Azure Arc-enabled Kubernetes cluster](how-to-deploy-self-hosted-gateway-azure-arc.md) as a [cluster extension](/azure/azure-arc/kubernetes/extensions).
@@ -26,16 +26,16 @@ This article provides the steps for deploying self-hosted gateway component of A
 ## Deploy the self-hosted gateway to AKS
 
 1. Select **Gateways** from under **Deployment and infrastructure**.
-2. Select the self-hosted gateway resource you intend to deploy.
-3. Select **Deployment**.
-4. A new token in the **Token** text box was autogenerated for you using the default **Expiry** and **Secret Key** values. Adjust either or both if desired and select **Generate** to create a new token.
-5. Make sure **Kubernetes** is selected under **Deployment scripts**.
-6. Select **\<gateway-name\>.yml** file link next to **Deployment** to download the file.
-7. Adjust the `config.service.endpoint`, port mappings, and container name in the .yml file as needed.
-8. Depending on your scenario, you might need to change the [service type](/azure/aks/concepts-network-services). 
-    * The default value is `LoadBalancer`, which is the external load balancer. 
-    * You can use the [internal load balancer](/azure/aks/internal-lb) to restrict the access to the self-hosted gateway to only internal users. 
-    * The sample below uses `NodePort`.
+1. Select the self-hosted gateway resource you intend to deploy.
+1. Select **Deployment**.
+1. A new token in the **Token** text box was autogenerated for you using the default **Expiry** and **Secret Key** values. Adjust either or both if desired and select **Generate** to create a new token.
+1. Make sure **Kubernetes** is selected under **Deployment scripts**.
+1. Select the **\<gateway-name\>.yml** file link next to **Deployment** to download the file.
+1. Adjust the `config.service.endpoint`, port mappings, and container name in the .yml file as needed.
+1. Depending on your scenario, you might need to change the [service type](/azure/aks/concepts-network-services). 
+    - The default value is `LoadBalancer`, which is the external load balancer. 
+    - You can use the [internal load balancer](/azure/aks/internal-lb) to restrict the access to the self-hosted gateway to only internal users. 
+    - The following sample uses `NodePort`.
 1. Select the **copy** icon located at the right end of the **Deploy** text box to save the `kubectl` command to clipboard.
 1. Paste the command to the terminal (or command) window. The command expects the downloaded environment file to be present in the current directory.
 
@@ -44,31 +44,33 @@ This article provides the steps for deploying self-hosted gateway component of A
    ```
 
 1. Execute the command. The command instructs your AKS cluster to:
-    * Run the container, using self-hosted gateway's image downloaded from the Microsoft Container Registry. 
-    * Configure the container to expose HTTP (8080) and HTTPS (443) ports.
-1. Run the below command to check the gateway pod is running. Your pod name will be different.
+    - Run the container, using self-hosted gateway's image downloaded from the Microsoft Container Registry. 
+    - Configure the container to expose HTTP (8080) and HTTPS (443) ports.
+1. Run the following command to check that your gateway pod is running. This pod name is an example.
 
    ```console
    kubectl get pods
    NAME                                   READY     STATUS    RESTARTS   AGE
    contoso-apim-gateway-59f5fb94c-s9stz   1/1       Running   0          1m
    ```
 
-1. Run the below command to check the gateway service is running. Your service name and IP addresses will be different.
+1. Run the following command to check that your gateway service is running. The service name and IP addresses are examples.
+
     ```console
     kubectl get services
     NAME             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
     contosogateway   NodePort    10.110.230.87   <none>        80:32504/TCP,443:30043/TCP   1m
     ```
-1. Return to the Azure portal and confirm that gateway node you deployed is reporting healthy status.
+
+1. Return to the Azure portal and confirm that the gateway node you deployed is reporting healthy status.
 
 > [!TIP]
-> Use `kubectl logs <gateway-pod-name>` command to view a snapshot of self-hosted gateway log.
+> Use the `kubectl logs <gateway-pod-name>` command to view a snapshot of the self-hosted gateway log.
 
 ## Related content
 
-* To learn more about the self-hosted gateway, see [Azure API Management self-hosted gateway overview](self-hosted-gateway-overview.md).
-* Learn [how to deploy API Management self-hosted gateway to Azure Arc-enabled Kubernetes clusters](how-to-deploy-self-hosted-gateway-azure-arc.md).
-* Learn more about the [observability capabilities of the Azure API Management gateways](observability.md).
-* Learn more about guidance to [run the self-hosted gateway on Kubernetes in production](how-to-self-hosted-gateway-on-kubernetes-in-production.md).
-* Learn more about [Azure Kubernetes Service](/azure/aks/intro-kubernetes).
+- To learn more about the self-hosted gateway, see [Azure API Management self-hosted gateway overview](self-hosted-gateway-overview.md).
+- Learn [how to deploy API Management self-hosted gateway to Azure Arc-enabled Kubernetes clusters](how-to-deploy-self-hosted-gateway-azure-arc.md).
+- Learn more about the [observability capabilities of the Azure API Management gateways](observability.md).
+- Learn more about guidance to [run the self-hosted gateway on Kubernetes in production](how-to-self-hosted-gateway-on-kubernetes-in-production.md).
+- Learn more about [Azure Kubernetes Service](/azure/aks/intro-kubernetes).