Skip to main content

TODO : A COMPLTER

Troubleshot

Migration Azure VPN Gateway​

Symtôme​

Message de Microsoft :

Migrate Azure VPN Gateway connections using SSTP to IKEv2 or OpenVPN by 31 March 2027
================================================================================

_You're receiving this notification because you're associated with one or more subscriptions that use Azure VPN Gateway configured with Secure Socket Tunneling Protocol (SSTP) for point-to-site connectivity._
On 31 March 2027, we're retiring SSTP for VPN Gateway connections. To avoid disruptions, [**migrate**](https://learn.microsoft.com/azure/vpn-gateway/ikev2-openvpn-from-sstp) **from SSTP to IKEv2 or OpenVPN before that date**. IKEv2 and OpenVPN both offer better performance, improved scalability, and superior capabilities, including support for up to 10,000 connections and 10 Gbps aggregate throughput.
Beginning on 31 March 2026, it will no longer be possible to enable SSTP for VPN Gateway connections. After 31 March 2027, you won't be able to use existing SSTP-enabled gateways to establish SSTP connections.

Required action
---------------

To avoid service disruptions, [**migrate**](https://learn.microsoft.com/azure/vpn-gateway/ikev2-openvpn-from-sstp) **to IKEv2 or OpenVPN before 31 March 2027**.

Résolution​

Investigation de Antony : Il y a un connected device en VPN Gateway mais non concerné :

image.png

image.png

image.png

MAIS :

image.png

CEPENDANT :

image.png

Les anciennes “VPN Gateway (Classic)” n’ont pas de SKU (comme VpnGw1, VpnGw2, etc.).  Elles sont affichées dans des “services (classic)” et n’apparaissent pas dans le même Resource Group que les VM ARM. Etant une VM ARM elle n'est PAS concernée par la fin de Gateway : c'est une gateway moderne (Azure Resource Manager), qui restera supportée au-delà de 2027.