Application Gateway SKU Family Defaults to Generation_1 Instead of Generation_2

Hi Kanifnath Deshmukh (Infosys Ltd),

Welcome to Microsoft Q&A and thank you for posting your query here!

The SKU family (Generation_1 vs Generation_2) for Azure Application Gateway is an internal platform classification that cannot be explicitly set via portal, ARM templates, or CLI. It is automatically determined by Azure based on backend infrastructure. When you choose the WAF_v2 SKU, you get the latest Application Gateway features irrespective of the family value shown.

Consider the following points:

• Region Support: Generation_2 infrastructure is available in certain regions; deploying in these regions is necessary for backend migration to Generation_2.
• Public IP SKU: The Application Gateway must be associated with a Standard SKU, static public IP for full V2 features, but this does not explicitly control the family property.
• SKU Specification: Always specify "name": "WAF_v2", "tier": "WAF_v2" in your ARM templates or CLI commands to ensure use of the V2 SKU.
• Deployment Tools: Use the latest Azure CLI or API versions for best compatibility.
• Resource Cleanup: After deleting a Generation_2 Gateway, it may take some time before a new one with Generation_2 backend can be provisioned in the same region.
• Family Property: The family field is informational and reflects backend state; it does not affect SKU capabilities or features.

Currently, there is no user-configurable way or workaround to force the Generation_2 family setting during deployment. Azure is migrating Application Gateways automatically in the background to Generation_2 where supported.

please do let me know if you have any question on this.

Thanks,

Harish.