Skip to content

Commit e243143

Browse files
committed
add retirement note
1 parent 6680218 commit e243143

2 files changed

Lines changed: 6 additions & 3 deletions

File tree

articles/app-service/configure-gateway-required-vnet-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Configure gateway-required virtual network integration for your app
33
description: Integrate your app in Azure App Service with Azure virtual networks using gateway-required virtual network integration.
44
author: seligj95
55
ms.topic: how-to
6-
ms.date: 06/19/2025
6+
ms.date: 01/30/2026
77
ms.author: jordanselig
88
ms.custom:
99
- build-2025
@@ -12,7 +12,7 @@ ms.service: azure-app-service
1212
# Configure gateway-required virtual network integration
1313

1414
> [!IMPORTANT]
15-
> For all virtual network integrations with App Service, the recommended method uses [regional virtual network integration](./overview-vnet-integration.md). Gateway-required virtual network integration is a legacy method with limitations that regional virtual network integration mitigates.
15+
> Gateway-required virtual network integration is being retired on March 31, 2027. For more information, see the [retirement announcement](https://azure.microsoft.com/updates/?id=499923) and [Migrate from SSTP to IKEv2 or OpenVPN](../vpn-gateway/ikev2-openvpn-from-sstp.md). We recommend migrating to [regional virtual network integration](./overview-vnet-integration.md), which mitigates the limitations of gateway-required virtual network integration.
1616
1717
Gateway-required virtual network integration supports connecting to a virtual network in another region or to a classic virtual network. Gateway-required virtual network integration only works for Windows plans. We recommend using [regional virtual network integration](./overview-vnet-integration.md) to integrate with virtual networks.
1818

articles/app-service/migrate-gateway-based-vnet-integration.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,16 @@ title: Migrate from gateway-based to regional virtual network integration
33
description: Learn how to migrate your App Service virtual network integration from legacy gateway-based integration to modern regional virtual network integration for improved performance and capabilities.
44
author: seligj95
55
ms.topic: how-to
6-
ms.date: 06/20/2025
6+
ms.date: 01/30/2026
77
ms.author: jordanselig
88
ms.custom: devx-track-azurecli, devx-track-azurepowershell
99
ms.service: azure-app-service
1010
---
1111
# Migrate from gateway-based to regional virtual network integration
1212

13+
> [!IMPORTANT]
14+
> Gateway-required virtual network integration is being retired on March 31, 2027. For more information, see the [retirement announcement](https://azure.microsoft.com/updates/?id=499923) and [Migrate from SSTP to IKEv2 or OpenVPN](../vpn-gateway/ikev2-openvpn-from-sstp.md). We recommend migrating to [regional virtual network integration](./overview-vnet-integration.md), which mitigates the limitations of gateway-required virtual network integration.
15+
1316
App Service supports two types of virtual network integration: **regional virtual network integration** (recommended) and **gateway-based virtual network integration** (legacy). This article guides you through migrating from the legacy gateway-based approach to the modern regional integration method.
1417

1518
## Overview

0 commit comments

Comments
 (0)