Share via

Cost and Steps for Migrating Existing Application Gateway to Zone Redundant

Punathil Thekkepat, Radhika (Allianz Technology) 0 Reputation points
2025-04-25T13:21:40.9566667+00:00

A notification was received regarding "Application Gateway: New Deployments Are Now Zone Redundant by Default". The message states, "This change will not affect pricing and will not impact existing Application Gateways." What are the steps and procedures, including any cost details, to migrate the existing setup to be zone redundant?

Thanks!

Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
1,185 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sindhuja Dasari 630 Reputation points Microsoft External Staff Moderator
    2025-04-25T14:18:17.5866667+00:00

    Hello Punathil Thekkepat, Radhika (Allianz Technology)

    Azure's new default behavior for Application gateway being zone redundant means that all new deployments in supported regions will automatically be deployed across Availability Zones for better resiliency. However, existing AGW are not automatically upgraded to zone redundancy, and migration requires a redeployment.

    Steps to Migrate to Zone Redundant Application Gateway:

     You cannot upgrade an existing AGW to zone redundancy directly. Two migration options are mentioned below:

    • First, ensure that you're using the Standard V2 or WAF V2 SKU, as earlier SKUs do not support availability zones.

    There are a couple of options for migrating:

    Option 1: Create a New Application Gateway

    • Go to the Azure Portal.
    • Create a new Application Gateway with a new frontend Public IP address. c. Verify that the application gateway and WAF are working as intended.
    • Migrate your DNS configuration to the new public IP address.
    • Delete the old Application gateway and WAF resources.    

    Option 2: Delete and Redeploy Existing Gateway:   

    • Go to the Azure Portal   
    • Select All resources, and then select the resource group that contains the Application Gateway.   
    • Select the Application Gateway resource and then select Delete. Type yes to confirm deletion, and then click Delete.
    • Create a new Application Gateway using the same Virtual Network, subnets, and Public IP address that you used previously.

    Be prepared for some downtime during migration, depending on the option you choose. The first option may minimize downtime if DNS is managed effectively.

    After deploying the new setup, test thoroughly to ensure everything works as expected before switching traffic over completely.

    Refer
      Migrate Azure Application Gateway

    Costing Details:

    • While the change to zone redundancy itself doesn't affect pricing, you should evaluate costs associated with the SKU changes if moving from V1 to V2. V2 SKUs charge based on consumption.
    • If you are currently using a V1 gateway, consider consolidating multiple V1 gateways into a single V2 gateway to optimize costs.

    Refer
    Application Gateway Pricing 

    Please don’t forget to close the thread by clicking "Accept the answer" and "Yes" wherever the information provided helps you, as this can be beneficial to other community members.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.