Skip to main content

Migrating Azure API Management to STv2: A Practical Guide

If you're using Azure API Management (APIM) services, you've likely seen this message: "Support for the single-tenant v1 (STv1) platform ends on 8/31/24. Migrate instances before that date to the new platform version (STv2) for continued support and access to new features."

This announcement highlights the urgency of migrating to STv2. To ensure a smooth transition, it's crucial to analyze our architecture, understand technical constraints, explore possible approaches, and assess risks. Here’s a summarized guide on how I managed the migration using the VNET-injection method.

My Case: APIM with Dedicated Public IP and Subnet


  • APIM with a dedicated public IP and a dedicated subnet.
  • Assigned private IP with NAT in a controlled VNET.
  • Need to maintain IP addresses and DNS.


  1. APIM migration requires a new public IP, new subnet with private IP, new DNS, and new NSG.
  2. APIM instances acquire IP addresses randomly, complicating existing firewall rules, NSG, and NAT configurations.


  • In-Place Migration
  • Parallel Setup


  • In-Place Migration with the ability to roll back to the original subnet with NAT IP.

Migration Process

Before Migration:

  1. Take screenshots of every configuration of APIM STv1 instances.
  2. Create a new public IP, new subnet, new NSG, and new DNS for the APIM STv2 instances.

During Migration:

  1. Release and migrate the APIM STv1 instance to the new subnet.
  2. Create dummy NICs in the original subnet before the IP address of the APIM instance. For example, create 5 dummy NICs to get IPs from to if the APIM instance needs to acquire (Azure reserves to by default).
  3. Once the dummy NICs are provisioned and occupy the IP addresses in the original subnet, wait for the APIM upgrade to STv2 (this took about 45 minutes).
  4. Move the APIM STv2 instance back to the original subnet and ensure it gets the previously assigned IP address.
  5. Verify that the APIM STv2 instance has the original IP. This avoids modifying firewall rules, NAT, and NSG if all steps go well.
  6. Test all your application APIs to ensure successful migration.

In my case, the migration was completed in less than 4 hours with no issues. Remember to delete any resources created temporarily for migration to avoid unnecessary costs.

Automation and Final Thoughts

I highly recommend automating the migration using Infrastructure-as-Code, especially for provisioning dummy NICs to ensure the APIM instance retains its IP address. In my scenario, the APIM IP was assigned as the first available IP in the subnet, requiring minimal dummy NIC creation. However, if your APIM instance uses the last available IP in your subnet, automation will be crucial to save time.


The cloud environment is rapidly evolving. Migrating to STv2 ensures continued support and access to new features. This guide offers a practical approach to migrating APIM to STv2 without impacting users. Stay updated and leverage the latest cloud innovations for optimal performance.

For more details, visit the Microsoft documentation.

Thank you.

(Be knowledgeable, pass it on then)


Popular posts from this blog

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f