![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 13%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 38%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
- Do you need to migrate before end of September 2025?
No, not necessarily — but only if your Basic SKU public IP is being used with a VPN Gateway. In that case, the deprecation has been pushed to end of January 2026. You’ll have time to use the migration tool when it becomes available (Sept–Oct 2025).
- Does this only affect Basic SKU IPs connected to VPN Gateways?
Yes — the extended timeline through January 2026 specifically applies to Basic SKU public IPs used in Azure VPN Gateways. Basic public IPs used for other resources (e.g., VMs, load balancers) follow the original schedule, and will be retired on September 30, 2025
- Will Basic SKU public IPs not associated with VPN Gateways continue to work until February 2026?
No — Basic IPs outside of VPN Gateways will not continue to work. They retire on September 30, 2025; any Basic IPs used by, say, VMs or other Azure services must be migrated or replaced before that date
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin