|
| 1 | +--- |
| 2 | +title: Troubleshoot ApplicationGatewaySkuNotSpecified error |
| 3 | +description: This article discusses how to resolve the ApplicationGatewaySkuNotSpecified error when you try to create or modify an application gateway. |
| 4 | +ms.date: 01/22/2026 |
| 5 | +ms.editor: v-gsitser |
| 6 | +ms.reviewer: rimayber, giverm, v-ryanberg |
| 7 | +ms.service: azure-application-gateway |
| 8 | +ms.custom: sap:Issues with Create, Update and Delete (CRUD) |
| 9 | +#Customer intent: As an Azure Application Gateway user, I want to troubleshoot an Application Gateway create or modify operation that failed because of ApplicationGatewaySkuNotSpecified error so that I can perform the operation successfully. |
| 10 | +--- |
| 11 | + |
| 12 | +# Troubleshoot the ApplicationGatewaySkuNotSpecified error |
| 13 | + |
| 14 | +## Summary |
| 15 | + |
| 16 | +This article discusses how to resolve the `ApplicationGatewaySkuNotSpecified` error that occurs when you try to create or modify an application gateway in Microsoft Azure Application Gateway. An application gateway can't be created or updated because the SKU size isn't specified. |
| 17 | + |
| 18 | +## Symptoms |
| 19 | + |
| 20 | +When you try to create or modify an application gateway, you encounter an `ApplicationGatewaySkuNotSpecified` error that prevents you from proceeding. |
| 21 | + |
| 22 | +## Cause |
| 23 | + |
| 24 | +This error occurs if the SKU (Standard or Web Application Firewall (WAF)) for the application gateway isn't specified during the creation or configuration process. |
| 25 | + |
| 26 | +## Resolution |
| 27 | + |
| 28 | +To resolve this problem, follow these steps: |
| 29 | + |
| 30 | +1. **Verify the SKU settings** |
| 31 | + |
| 32 | +Make sure that the correct SKU is specified when you create or configure the application gateway. For example, use `Standard_v2` or `WAF_v2` for newer SKU types. The following code shows an example configuration: |
| 33 | + |
| 34 | +```json |
| 35 | + |
| 36 | +"sku": { |
| 37 | +"name": "Standard_v2", |
| 38 | +"tier": "Standard" |
| 39 | +} |
| 40 | + |
| 41 | +``` |
| 42 | + |
| 43 | +2. **Update the application gateway configuration** |
| 44 | + |
| 45 | +If you're modifying an existing application gateway, update the SKU settings by using [the Azure portal](https://portal.azure.com), Azure CLI, or an Azure Rights Management (Azure RMS) template. |
| 46 | + |
| 47 | +3. **Check Azure RMS or Azure CLI command** |
| 48 | + |
| 49 | +If you're using an Azure RMS template or Azure CLI, make sure that the `sku` segment is included correctly. For Azure CLI: |
| 50 | + |
| 51 | +```azurecli |
| 52 | +
|
| 53 | +az network application-gateway create --name <gateway_name> --resource-group <resource_group> --sku Standard_v2 --public-ip-address <public_ip> |
| 54 | +
|
| 55 | +``` |
| 56 | + |
| 57 | +4. **Redeploy or re-create** |
| 58 | + |
| 59 | +After you specify the SKU, try again to deploy or create the application gateway. |
| 60 | + |
| 61 | +### Resources |
| 62 | + |
| 63 | +[What is Azure Application Gateway v2?](/azure/application-gateway/overview-v2) |
0 commit comments