Skip to content

Commit 4418f1c

Browse files
committed
edited table.
1 parent 5fece08 commit 4418f1c

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

articles/vpn-gateway/vpn-gateway-vpn-faq.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -221,13 +221,14 @@ The expected customer impact includes new [pricing](https://azure.microsoft.com/
221221

222222
These timelines may be subject to change. Please revisit this for the most updated timeline. Here's the anticipated timeline for the migration tool availability.
223223

224-
| Date | Event |
225-
|---------------------|------------------------------------------------------------|
226-
| Apr/May 2025 | Migration tooling availability for Active-Passive Gateways. |
227-
| Jul/Aug 2025 | Migration tooling availability for Active-Active Gateways. |
228-
| May 2025 to Sep 2025| Customer-controlled migration can be initiated after tool availability. |
229-
| Sep 2025 | Basic SKU IP addresses are deprecated. |
230-
224+
| Date | Event |
225+
|---------------------|------------------------------------------------------------|
226+
| Apr/May 2025 | Migration tooling availability for Active-Passive Gateways. |
227+
| Jul/Aug 2025 | Migration tooling availability for Active-Active Gateways. |
228+
| May 2025 to Sep 2025| Customer-controlled migration can be initiated after tool availability. |
229+
| Sep 2025 | Basic SKU IP addresses are deprecated. |
230+
231+
231232
### What are the required customer actions?
232233

233234
Ensure you have the correct IP address space and subnet size to support the migration. If your gateway is using a Basic IP, you need to migrate it to a Standard IP to avoid service disruption. This migration is necessary because Basic IP addresses will be deprecated by September 2025. If your gateway is already using a Standard IP, no action is required.

0 commit comments

Comments
 (0)