Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into freshness

Author: batamig

articles/api-management/api-management-gateways-overview.md

@@ -54,8 +54,6 @@ API Management offers both managed and self-hosted gateways:
 
     * Each self-hosted gateway is associated with a **Gateway** resource in a cloud-based API Management instance from which it receives configuration updates and communicates status. 
 
-[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.md)]
-
 ## Feature comparison: Managed versus self-hosted gateways
 
 The following tables compare features available in the following API Management gateways:

articles/api-management/breaking-changes/self-hosted-gateway-v0-v1-retirement-oct-2023.md

@@ -5,15 +5,15 @@ services: api-management
 author: dlepow
 ms.service: azure-api-management
 ms.topic: reference
-ms.date: 09/06/2022
+ms.date: 09/25/2024
 ms.author: danlep
 ---
 
 # Support ending for Azure API Management self-hosted gateway version 0 and version 1 container images (October 2023)
 
 [!INCLUDE [api-management-availability-premium-dev](../../../includes/api-management-availability-premium-dev.md)]
 
-The [self-hosted gateway](../self-hosted-gateway-overview.md) is an optional, containerized version of the default managed gateway included in every API Management service. On 1 October 2023 we're removing support for the v0 and v1 versions of the self-hosted gateway container image. If you've deployed the self-hosted gateway using either of these container images, you need to take the steps below to continue using the self-hosted gateway by migrating to the v2 container image and configuration API.
+The [self-hosted gateway](../self-hosted-gateway-overview.md) is an optional, containerized version of the default managed gateway included in every API Management service. On 1 October 2023 we removed support for the v0 and v1 versions of the self-hosted gateway container image. If you've deployed the self-hosted gateway using either of these container images, you need to take the steps below to continue using the self-hosted gateway by migrating to the v2 container image and configuration API.
 
 ## Is my service affected by this?
 
@@ -33,7 +33,7 @@ We highly recommend customers to use ["All Recommendations" overview in Azure Ad
 
 ## What is the deadline for the change?
 
-**Support for the v1 configuration API and for the v0 and v1 container images of the self-hosted gateway will retire on 1 October 2023.**   
+**Support for the v1 configuration API and for the v0 and v1 container images of the self-hosted gateway retired on 1 October 2023.**   
 
 Version 2 of the configuration API and container image is already available, and includes the following improvements:  
 
@@ -45,7 +45,7 @@ If you are using version 0 or version 1 of the self-hosted gateway, you will nee
 
 ## What do I need to do?
 
-Migrate all your existing deployments of the self-hosted gateway using version 0 or version 1 to the newest v2 container image and v2 configuration API by 1 October 2023.
+Migrate all your existing deployments of the self-hosted gateway using version 0 or version 1 to the newest v2 container image and v2 configuration API.
 
 Follow the [migration guide](../self-hosted-gateway-migration-guide.md) for a successful migration.
 

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

@@ -15,8 +15,6 @@ ms.author: danlep
 
 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).
 
-[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.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).
 

articles/api-management/how-to-deploy-self-hosted-gateway-docker.md

@@ -15,8 +15,6 @@ ms.author: danlep
 
 This article provides the steps for deploying self-hosted gateway component of Azure API Management to a Docker environment.
 
-[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.md)]
-
 > [!NOTE]
 > Hosting self-hosted gateway in Docker is best suited for evaluation and development use cases. Kubernetes is recommended for production use. Learn how to [deploy with Helm](how-to-deploy-self-hosted-gateway-kubernetes-helm.md) or using [deployment YAML file](how-to-deploy-self-hosted-gateway-kubernetes.md) to learn how to deploy self-hosted gateway to Kubernetes.
 

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

@@ -17,8 +17,6 @@ ms.author: tomkerkhove
 
 This article provides the steps for deploying self-hosted gateway component of Azure API Management to a Kubernetes cluster by using Helm.
 
-[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.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).
 

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

@@ -14,8 +14,6 @@ ms.date: 05/22/2023
 
 This article describes the steps for deploying the self-hosted gateway component of Azure API Management to a Kubernetes cluster.
 
-[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.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).
 

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

@@ -17,8 +17,6 @@ In order to run the self-hosted gateway in production, there are various aspects
 
 This article provides guidance on how to run [self-hosted gateway](./self-hosted-gateway-overview.md) on Kubernetes for production workloads to ensure that it will run smoothly and reliably.
 
-[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.md)]
-
 ## Access token
 Without a valid access token, a self-hosted gateway can't access and download configuration data from the endpoint of the associated API Management service. The access token can be valid for a maximum of 30 days. It must be regenerated, and the cluster configured with a fresh token, either manually or via automation before it expires.
 

articles/api-management/includes/preview/preview-callout-self-hosted-gateway-deprecation.md

@@ -91,8 +91,6 @@ Self-hosted gateways require outbound TCP/IP connectivity to Azure on port 443.
 -   Sending metrics to Azure Monitor, if configured to do so
 -   Sending events to Application Insights, if set to do so
 
-[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.md)]
-
 ### FQDN dependencies
 
 To operate properly, each self-hosted gateway needs outbound connectivity on port 443 to the following endpoints associated with its cloud-based API Management instance:

articles/api-management/self-hosted-gateway-overview.md

@@ -5,7 +5,7 @@ author: dlepow
 ms.service: azure-api-management
 ms.topic: article
 ms.author: danlep
-ms.date: 05/12/2023
+ms.date: 09/25/2024
 ---
 
 # Support policies for self-hosted gateway
@@ -14,8 +14,6 @@ ms.date: 05/12/2023
 
 The Azure API Management service, in the Developer and Premium tiers, allows the deployment of the API Management gateway as a container running in on-premises infrastructure, other clouds, and Azure infrastructure options that support containers. This article provides details about technical support policies and limitations for the API Management [self-hosted gateway](self-hosted-gateway-overview.md).  
 
-[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.md)]
-
 ## Differences between managed gateway and self-hosted gateway
 
 When deploying an instance of the API Management service, you'll always get a managed API gateway as part of the service. This gateway runs in infrastructure managed by Azure, and the software is also managed, updated, and managed by Azure.