Hello @Alexandre Santos ,
Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
I understand that you would like to know if it is possible to move Application gateway v1 to a new subscription.
To start with, moving application gateways to another resource group/region/subscription is not supported.
The only allowed move is between subnets within the same Vnet:
- You can move an Application Gateway across subnets within the same virtual network only. It's supported with V1 with public and private frontend, and V2 with public frontend only.
As you cannot move existing Application gateways to another subscription, your only option is to create/deploy a new Application gateway in the new subscription using the existing app gateway's template.
Now, coming to Application Gateway v1 SKU retirement, the timeline says:
No new subscriptions for V1 deployments: July 1,2023 onwards - Application Gateway V1 is no longer available for deployment on subscriptions without V1 gateways (Refer to FAQ for details) from July 1, 2023, onwards.
If you check the FAQ, you can find the below:
What is the definition of a new customer on Application Gateway V1 SKU? Customers who didn't have Application Gateway V1 SKU in their subscriptions as of 4 July 2023 are considered as new customers. These customers won’t be able to create new V1 gateways in subscriptions which didn't have an existing V1 gateway as of 4 July 2023 going forward.
Meaning, if the new subscription didn't already have an application gateway v1 as of 4 July 2023, then you cannot create a new v1 App gateway in this subscription.
So, your only options are to keep using the Application gateway in the existing subscription till the retirement date or to create a new Application gateway v2 in the new subscription.
Kindly let us know if the above helps or you need further assistance on this issue.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.