This article explains how to handle errors when attempting to deploy a Fortinet-VM product, such as a FortiGate cluster, in different Azure Availability zones.
Error:
‘The requested VM size for the resource Following SKUs have failed for Capacity Restrictions: Standard_F4s is currently not available in the location westeurope. Use a different size or deploy to another location or zone. See https://aka.ms/azureskunotavailable for details. (Code: SkuNotAvailable)’
Scope
This issue pertains to Azure deployments involving products like FortiGate, FortiManager, FortiProxy, and FortiWeb.
Solution
Open the Azure Cloud Shell and check if there are deployment restrictions.
For example, to check in the ‘westeurope’ region and filter anything that has ‘f4’, use the following command:
Get-AzureRmComputeResourceSku | where { $_.Locations -icontains "westeurope" } | where { $_.Name -ilike "*f4*" }
For the full list of resources available in the region, use:
Get-AzureRmComputeResourceSku | where { $_.Locations -icontains "westeurope" }
Find the full region names with the following command or use this external website
Get-AzLocation | Select-Object DisplayName, Location
Example on Azure account with no restrictions:
| ResourceType | Name | Location | Zones |
|---|---|---|---|
| virtualMachines | Standard_F4 | westeurope | {1, 3, 2} |
| virtualMachines | Standard_F48s_v2 | westeurope | {3, 2, 1} |
| virtualMachines | Standard_F4s | westeurope | {1, 3, 2} |
| virtualMachines | Standard_F4s_v2 | westeurope | {3, 2, 1} |
Example on Azure account with restrictions:
| ResourceType | Name | Location | Zones | RestrictionInfo |
|---|---|---|---|---|
| virtualMachines | Standard_F4 | westeurope | {2, 1, 3} | type: Zone, locations: westeurope, zones: 2, 3 |
| virtualMachines | Standard_F48s_v2 | westeurope | {1, 3, 2} | type: Zone, locations: westeurope, zones: 2, 3 |
| virtualMachines | Standard_F4s | westeurope | {2, 1, 3} | type: Zone, locations: westeurope, zones: 2, 3 |
| virtualMachines | Standard_F4s_v2 | westeurope | {1, 3, 2} | type: Zone, locations: westeurope, zones: 2, 3 |
This means it will only be possible to deploy those instances in the 1st availability zone. It will not be possible to implement a cluster across multiple availability zones.
This issue is not related to Fortinet. Azure administrators or Azure support should be contacted to lift those restrictions if required.
If other ResourceTypes are allowed, they can be compared against the Fortinet-supported list of the desired product.