az network lb --frontend-ip-zone not working when multiple zones are included #30502
Description
Describe the bug
Customer is unable to deploy Azure Load Balancer when the frontend-ip-zone is set to multiple zones. They are able to deploy with no issues when frontend-ip-zone 1. It doesn't seem to be an issue from networking side since the same deployment can be completed in Portal.
Related command
az network lb --frontend-ip-zone
Errors
...which uses zone Zone-redundant since subscription xxxxxxx does not support zone Zone-redundant in location canadacentral."
Issue script & Debug output
az network lb create
--resource-group $resourcegroup
--name $lb_name
--sku Standard
--vnet-name $vnet_name
--subnet $subnet_name
--frontend-ip-name $lb_frontendip_name
--frontend-ip-zone 1,2,3 \ <--
--backend-pool-name $lb_backend_pool_name
Expected behavior
Deployment should not have an error when using --frontend-ip-zone 1,2 or --frontend-ip-zone 1,2,3 since these zones exist and the same zone deployments work in Portal.
Environment Summary
to be included by the SE
Additional context
No response