Skip to content

Update Application Gateway FAQ on SKU family clarification #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jagan103 wants to merge 1 commit into
base: patch-4
Choose a base branch
from
Open

Update Application Gateway FAQ on SKU family clarification #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions articles/application-gateway/application-gateway-faq.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,16 +149,17 @@ sections:
answer: |
An active listener is a listener that's associated to a rule *and* sending traffic to a backend pool. Any listener that *only* redirects traffic isn't an active listener. Listeners associated with redirect rules aren't considered active. If the redirect rule is a path-based rule, all the paths in that redirect rule must be redirecting traffic or else the listener is considered active. For individual component limit details, see [Azure subscription and service limits, quotas, and constraints](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-application-gateway-limits).

- question: "Why does my Application Gateway show 'SKU family: Generation_1' even though I am using a V2 SKU (WAF_v2 or Standard_v2)?"
- question: Why does my Application Gateway show "SKU family Generation_1" even though I'm using a v2 SKU (WAF_v2 or Standard_v2)?
answer: |
The SKU family (Generation_1 vs Generation_2) is an internal Azure platform classification and is not related to the Application Gateway V2 SKU version.
* The SKU family value is not configurable via the Azure portal, ARM templates, or CLI.
* It is automatically assigned by Azure based on underlying platform infrastructure.
* When you select a V2 SKU (Standard_v2 or WAF_v2), you are already using the latest Application Gateway capabilities, regardless of the family value displayed.

Important:
* The SKU name (Standard_v2 / WAF_v2) determines the feature set and behavior—not the SKU family.
* The SKU family property is informational only and has no impact on functionality, performance, or features of Application Gateway v2.
This is expected and doesn't mean your gateway is running on v1. The "SKU family" and "SKU name" are two separate properties:

| Property | What it means | Example |
|---|---|---|
| SKU name | The product tier you selected. Determines features, performance, and behavior. | `Standard_v2`, `WAF_v2` |
| SKU family | An internal Azure platform label for the underlying hardware generation. Informational only. | `Generation_1` |

- If your SKU name is `Standard_v2` or `WAF_v2`, you're running Application Gateway v2 with all v2 capabilities — regardless of what **SKU family** shows.
- **SKU family** is assigned automatically by Azure. You can't change it in the portal, ARM, Bicep, or CLI, and you don't need to. It has no impact on functionality, performance, features, or billing.

- name: Performance
questions:
Expand Down