Skip to content

Commit 1207379

Browse files
authored
Update api-management-migration-compute-coexist.md
1 parent d0f6de1 commit 1207379

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed
Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,16 @@
1+
---
2+
author: dlepow
3+
ms.service: api-management
4+
ms.topic: include
5+
ms.date: 02/13/2024
6+
ms.author: danlep
7+
---
8+
19
## Confirm settings before old gateway is purged
210

311
After successful migration of a VNet-injected API Management instance, the old and the new compute created during migration coexist for a short period of time, approximately 15 mins, which is a small window of time you can use to validate the deployment and that your applications work as expected. (*This window can be extended to 48 hours by contacting Azure support in advance.*)
412

513
* During this window, the old and new gateways are both online and serving traffic. You are not billed during this time.
614
* Use this window to update any network dependencies including DNS, firewall rules, and VNets to use the new VIP address and subnet address space.
715
* Additionally, check the updated instance's network status to ensure connectivity of the instance to its dependencies. In the portal, in the left-hand menu, under **Deployment and infrastructure**, select **Network** > **Network status**. If needed, update settings such as UDRs and NSG rules.
8-
* After the window, the old gateway is decommissioned and the new gateway is the only one serving traffic.
16+
* After the window, the old gateway is decommissioned and the new gateway is the only one serving traffic.

0 commit comments

Comments
 (0)