Required some clarifications upon migration from Stv1 to Stv2 platform version(API management service). By using old subnet we can migrate the process? or definitely need to change the new subnet? In my case we are using Vnet injected(Internal) API Management instance, so is there any other possibilities ways to migrate apart from Azure portal like by using Iac? To backup the API management service as per MS doc recommended to do via PS scripts and rest API, is there any possible with Iac?

Hello @Pardeep the answer to your questions can be found in this Azure doc: Migrate an API Management instance hosted on the stv1 platform to stv2 Here are some points to bring some clarification to your questions: To answer your first question, yes migration with the existing subnet (Internal VNet) is possible. You can migrate your API Management instance from Stv1 to Stv2 while keeping the same internal VNet subnet. This option is available through both the Azure portal and Infrastructure as Code (IaC). You can definitely use IaC tools like Azure Resource Manager (ARM) templates or Bicep to automate the migration process. This approach offers greater flexibility and repeatability compared to the Azure portal. While not strictly required, enabling zone redundancy for your existing API Management service will automatically migrate it to Stv2 and place it in availability zones. This can be done through the Azure portal or IaC as well. Backing up your API Management service using IaC is currently not possible**.** Like you stated the Azure docs recommends using PowerShell scripts or the REST API for backups. However, you can leverage IaC tools to manage the deployment and configuration of your API Management instance after the migration is complete. Lastly, we highly recommend for you to migrate your Stv1 API Management instances to Stv2 before August 31, 2024, as Stv1 support will be retired after that date. Please let us know if you have further questions. -Grace

Need clarifications on API management STV1 migration

Pardeep 80

Required some clarifications upon migration from Stv1 to Stv2 platform version(API management service).

By using old subnet we can migrate the process? or definitely need to change the new subnet?
In my case we are using Vnet injected(Internal) API Management instance, so is there any other possibilities ways to migrate apart from Azure portal like by using Iac?
To backup the API management service as per MS doc recommended to do via PS scripts and rest API, is there any possible with Iac?

Pardeep 80 Reputation points

2024-03-06T13:08:24.5133333+00:00
Hi @Grmacjon-MSFT thanks for quick reply, just to clarify

yes migration with the existing subnet (Internal VNet) is possible. You can migrate your API Management instance from Stv1 to Stv2 while keeping the same internal VNet subnet. This option is available through both the Azure portal and Infrastructure as Code (IaC). - So, how the same subnet works as per below MS Doc prerequisites,

Suggested to create new subnet and new public IP address and update the both at Vnet configuration before the migration process, so how the process with use of old subnet?(just need to add only public IP instead of selecting new subnet, leaving old subnet as same while doing Vnet configuration ) and how to migrate with Iac? is there any particular process recommended or any code changes need to do to migrate it ? and how much time it takes to migrate with Iac(to plan downtime)?

You can definitely use IaC tools like Azure Resource Manager (ARM) templates or Bicep to automate the migration process. This approach offers greater flexibility and repeatability compared to the Azure portal. While not strictly required, enabling zone redundancy for your existing API Management service will automatically migrate it to Stv2 and place it in availability zones. This can be done through the Azure portal or IaC as well. - How to do the migration process with Iac?any MS recommended steps or snippet to do via Iac(using ARM or Bicep)?
Ben Gimblett 4,525 Reputation points Microsoft Employee

2024-03-06T15:13:26.95+00:00

Hey - thanks for the question
To address your additional comments -

Same subnet:
*The important point is that you cant migrate on the same subnet in "one shot". You must upgrade to a new subnet first and then update the configuration to go backward to the original subnet as per the detailed instructions in the doc. This second step, going back to the original subnet implies downtime. If that's unclear I can explain more, trying to keep the comment brief !! Note: STV2 requires a VIP (public IP)

IAC
*For a non vnet attached APIM then use the CLI (as per doc)
*For vnet attached (your scenario) then you can use a template because migration is triggered by a change in network configuration We dont supply an example in the STV2 migration doc (I'm going to raise this) and how exactly the template looks will depend on your deployment. I would recommend only using the template to trigger migration if you already deployed APIM that way - to avoid the risk you change more than you intended.
Whilst you can export a template from an existing resource my understanding is it may be incomplete under certain circumstances. So would need to be checked carefully.

This quick start would certainly give you a starting point in terms of identifying the fields related to network config https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.apimanagement/api-management-create-with-internal-vnet-publicip/main.bicep

If you didnt deploy using a template and you find recreating one risky - then you could look at either REST API or PS1 module In both cases you'd first need to do a "get" (e.g. get-azapimanagement for PS1) to get the existing resource definition followed by an update (set-azapimanagement for PS1) where you've also changed the fields relating to the networking as per doc instructions PS1 https://learn.microsoft.com/en-us/powershell/module/az.apimanagement/?view=azps-11.3.0#api-management REST https://learn.microsoft.com/en-us/rest/api/apimanagement/api-management-service?view=rest-apimanagement-2022-08-01
Grmacjon-MSFT 17,886 Reputation points

2024-03-07T19:28:53.7866667+00:00

@Pardeep hope Ben's helpful comment was able to address your additional questions. Please let us know if you have more questions.
Pardeep 80 Reputation points

2024-03-25T14:08:33.72+00:00

Hi, @Grmacjon-MSFT / @Ben Gimblett Getting here after a long time, I have a couple of questions about public IP addresses (for APIM migration) - According to Microsoft's documentation, public IP addresses should be created for the migration part, but according to our company's policy public IPs should not be created, because in our case APIMs (injected Vnet internal) should not affect other Azure resources that are available and should not ingress with other resources due to public IP. So, how can we handle this, and is there any way to ensure security on all of those addresses(if definitely the Public IP address is required for migration)?
Ben Gimblett 4,525 Reputation points Microsoft Employee

2024-03-25T14:17:28.43+00:00

Hi please could you email me - my address is on my profile and I'll take this question with you offline
Pardeep 80 Reputation points

2024-03-25T16:17:53.9566667+00:00

Hi @Ben Gimblett , sure could you please share your email here, I'm not able to find in the profile.

Accepted answer

Grmacjon-MSFT 17,886 Reputation points

2024-03-05T19:11:35.2466667+00:00
Hello @Pardeep the answer to your questions can be found in this Azure doc: Migrate an API Management instance hosted on the stv1 platform to stv2

Here are some points to bring some clarification to your questions:

To answer your first question, yes migration with the existing subnet (Internal VNet) is possible. You can migrate your API Management instance from Stv1 to Stv2 while keeping the same internal VNet subnet. This option is available through both the Azure portal and Infrastructure as Code (IaC).

You can definitely use IaC tools like Azure Resource Manager (ARM) templates or Bicep to automate the migration process. This approach offers greater flexibility and repeatability compared to the Azure portal. While not strictly required, enabling zone redundancy for your existing API Management service will automatically migrate it to Stv2 and place it in availability zones. This can be done through the Azure portal or IaC as well.

Backing up your API Management service using IaC is currently not possible**.** Like you stated the Azure docs recommends using PowerShell scripts or the REST API for backups. However, you can leverage IaC tools to manage the deployment and configuration of your API Management instance after the migration is complete.

Lastly, we highly recommend for you to migrate your Stv1 API Management instances to Stv2 before August 31, 2024, as Stv1 support will be retired after that date.

Please let us know if you have further questions.

-Grace
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Need clarifications on API management STV1 migration

0 additional answers

Your answer