Skip to main content

Deployment Issues

Hint

Most of the errors on this page are prevented by the checks described in the System Requirements.

The subscription is not registered to use namespace Microsoft.KeyVault (Code: MissingSubscriptionRegistration)​

Cause

One of the required resource providers is not registered in the target subscription. The same error appears for the other providers used by the deployment.

Solution

  1. Register all required resource providers as described in the System Requirements.
  2. Wait until every provider shows the status Registered.
  3. Start the deployment again.

Operation cannot be completed without additional quota (Code: SubscriptionIsOverQuotaForSku)​

Cause

The subscription has no compute quota for the selected App Service Plan size in the deployment region. New and trial subscriptions often have a limit of 0 for the required family.

Solution

  1. Request a quota increase for the required family in the deployment region, or select a size whose quota is available.
  2. Start the deployment again after the quota increase has been approved.

The deployment fails with InsufficientQuota​

Cause

The requested model capacity is higher than the tokens per minute still available for this model family in the selected Cognitive Services region. Capacity is shared with all other deployments of that model family in the same subscription and region.

Solution

  1. Check the available quota under Azure AI Foundry -> Quotas, or with az cognitiveservices usage list --location <region> --output table.
  2. Reduce the capacity, select a region with free quota, or request a quota increase.
  3. Start the deployment again.

The deployment fails with an authorization error on a role assignment​

Cause

The deploying user does not have permission to create role assignments. The deployment needs them so that AI Analyst can read its secrets from Key Vault with its managed identity.

Solution

Have an Owner of the subscription assign you the Owner role, or Contributor plus User Access Administrator, on the target scope, then start the deployment again.


The deployment fails with FlagMustBeSetForRestore​

Cause

An earlier deployment in the same resource group was deleted. Key Vault and Azure AI Foundry accounts are kept in a soft-deleted state, and the names are still reserved.

Solution

Purge the soft-deleted resources, then start the deployment again:

az cognitiveservices account purge --location <region> --resource-group <resource-group> --name <name>
az keyvault purge --name <vault-name>

Cannot modify resource ... provisioning state is not terminal (Code: RequestConflict)​

Cause

A previous deployment of the same resource is still running. This typically happens when a deployment is started again immediately after a failure.

Solution

Wait until the resource shows a completed provisioning state in the Azure Portal, then start the deployment again.