-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Azure CLI: az webapp deploy fails in Azure Government (usgovarizona) due to unsupported API version 2024-11-01 #31916
Copy link
Copy link
Open
Labels
Accountaz login/accountaz login/accountAuto-AssignAuto assign by botAuto assign by botAuto-ResolveAuto resolve by botAuto resolve by botPossible-SolutionService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.Similar-IssueWeb Appsaz webappaz webappact-identity-squadact-observability-squadapp-service-generalcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Metadata
Metadata
Assignees
Labels
Accountaz login/accountaz login/accountAuto-AssignAuto assign by botAuto assign by botAuto-ResolveAuto resolve by botAuto resolve by botPossible-SolutionService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.Similar-IssueWeb Appsaz webappaz webappact-identity-squadact-observability-squadapp-service-generalcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Type
Fields
Give feedbackNo fields configured for issues without a type.
Describe the bug
The latest Azure CLI (as of Aug 2025) uses API version 2024-11-01 for Microsoft.Web/sites by default, which is not supported in the usgovarizona region.
This causes az webapp deploy to fail with NoRegisteredProviderFound, breaking our deployment pipelines.
Please update the CLI to detect supported API versions per region (especially for Azure Government) or provide a way to override it in CLI commands.
Related command
az webapp deploy
Errors
YML pipeline extract:
script:
- curl -sL https://aka.ms/InstallAzureCLIDeb | bash
- az cloud set --name AzureUSGovernment
- az login --service-principal -u "$AZURE_TEST_APP_ID" -p "$AZURE_TEST_SECRET" --tenant "$AZURE_TENANT_ID"
- az webapp deploy --resource-group "$AZURE_TEST_RG" --name "$AZURE_TEST_WEBAPP_BE" --src-path $ZIP_FILE --type zip
rules:
- if: '$CI_COMMIT_BRANCH == "main"'
ERROR: Job failed: exit code 1
Issue script & Debug output
Code: NoRegisteredProviderFound
Message: No registered resource provider found for location 'usgovarizona' and API version '2024-11-01' for type 'sites'. The supported api-versions are '2024-04-01, 2023-12-01, 2023-01-01, 2022-09-01, 2022-03-01, 2021-03-01, 2021-02-01, 2021-01-15, 2021-01-01, 2020-12-01, 2020-10-01, 2020-09-01, 2020-06-01, 2019-08-01, 2018-11-01, 2018-02-01, 2016-08-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01, 2014-04-01-preview'. The supported locations are 'usdodeast, usgovvirginia, usdodcentral, usgovarizona, usgovtexas'.
Expected behavior
I should have been able to deploy with the az webapp deploy to my app living in usgovarizona
Environment Summary
attempting to deploy barebones .NET 8 API using Code publishing model on Windows host via GitLab v18.2.1-ee pipeline.
azure-cli_2.76.0-1~bookworm_amd64.deb
Additional context
I noticed a few weeks ago I tried this to another web app in the same rg and did not get this problem; it was the same tenant and app service.