| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Load balancers | Network and edge | 2% | 9 of 94 | 0% | 10 | accepted challenger | |
| Web application firewalls | Network and edge | 0% | 27 of 82 | 0% | 2 | under 10 labels · led by Cloudflare WAF at 69% | newNew since September 2026: not ranked then, 0% now. |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 2 | 0 | 0 | 2 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 2 | 0 | 0 | 2 |
| Perplexity Sonar | 0 | 1 | 0 | 0 | 1 |
| Grok 4.20 | 0 | 0 | 0 | 0 | 0 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 1 | 0 | 1 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 1 | 0 | 0 | 0 | 1 |
| Kimi K2 | 0 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 1 | 0 | 1 |
| MiniMax M2.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 2 | 0 | 0 | 2 |
| Muse Glimmer 30B | 0 | 0 | 1 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“Use the Application Gateway on Azure or Network Load Balancer (NLB) on AWS if you have strict compliance requirements” Qwen 3.7 Flash · Load balancers · direct prompt · first choice
“If everything is already in Azure and you prefer a managed service, Azure Application Gateway is a natural fit.” MiniMax M2.5 · Load balancers · paraphrase prompt · alternative
“AWS Elastic Load Balancing (ALB/NLB) or Azure's Application Gateway run directly within your cloud architecture.” Gemini 3.5 Flash · Load balancers · direct prompt · alternative
“Azure is worth considering if you're building primarily on AKS, VMSS or want close Microsoft integration” Claude Haiku 4.5 · Load balancers · comparative prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 30 of the 33 answers that named Azure Application Gateway and are not a share of its labels.
Eighty-seven of the eighty-seven domain citations in answers naming Azure Application Gateway came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Azure Application Gateway's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Azure Application Gateway, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Azure Application Gateway by email, built from the raw record of the edition. It shows: