Skip to content

Commit c780a24

Browse files
Merge pull request #307295 from raboilla/patch-36
Add FAQ on migration duration to documentation
2 parents f88ff2c + b2d2fd2 commit c780a24

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

articles/vpn-gateway/basic-public-ip-migrate-about.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,16 @@ To migrate your gateway, you first need to validate whether your resource is cap
2929

3030
## FAQ
3131

32+
### How long does the end-to-end migration typically take?
33+
* The entire migration process usually takes up to 2 hours, depending on the size and configuration of your deployment.
34+
35+
### How long does each migration step take?
36+
* Migration step durations can vary based on environment complexity. On average:
37+
38+
Prepare: Typically up to 40 minutes, with a maximum of 1 hour.<br>
39+
Execute: Takes around 5–10 minutes. (This is the only step where brief downtime is expected.)<br>
40+
Commit: Typically up to 30 minutes, with a maximum of 1 hour.
41+
3242
### How will my gateway SKU be impacted after the Basic SKU public IP address migration?
3343

3444
After you upgrade from a Basic SKU public IP address to a Standard SKU public IP address, your VPN gateway SKU VPNGW1-5 will be migrated to VPNGW1AZ-5. As a result, you might see the SKU changed from a Non-AZ to an AZ-SKU. For more information about SKU impact, see the [Gateway SKU migration](gateway-sku-consolidation.md) article.

0 commit comments

Comments
 (0)