Powershell 7+ with AZ module are not installed (Windows only)
Symptoms:
ERROR: failed running pre/post hooks: 'prepackage' hook failed with exit code: '1', Path: 'scripts\fetchComponents.ps1'. : exit code: 1, stdout: , stderr: 'pwsh' is not recognized as an internal or external command,
operable program or batch file.
Cause:
You do not have the correct Powershell version. You need to install the appropriate version of PowerShell on the machine that azd up is running on.
You do not have AZ PowerShell module installed. You need to install AZ PowerShell module on the machine Install-Module -Name Az -Repository PSGallery -Force that azd up is running on.
Azure OpenAI model is not available in the selected region.
Symptoms:
ERROR: deployment failed: failing invoking action 'provision', error deploying infrastructure: deploying to subscription:
Deployment Error Details:
RetryableError: A retryable error occurred.
Cause:
The error message indicates that the deployment failed to provision an infrastructure resource. It may have occurred with another resource that is not Azure OpenAI, but this is a common cause. Therefore, in this case, check if the gpt model selected in the deployment is available in the selected region. You can check the gpt model selected in the deployment looking at the chatGptModelName and chatGptModelVersion parameters of the main.parameters.json file.
The subscription's home tenant differs from the tenant of the identity executing the 'azd' command
Symptoms:
While running post-provisioning scripts, you encounter the following error:
ERROR: No subscription found. Run 'az account set' to select a subscription.
or
ERROR: Get-AzAccessToken: Run Connect-AzAccount to login.
Cause:
This issue can occur if you have subscriptions whose home tenant is not the same as the tenant where your user is registered and authenticated.
In this case, using azd auth login may not sufficient to enable your subscription for the Azure CLI commands we run in the azd hooks.
You will need to log in using az login --tenant TENANT_ID or Connect-AzAccount -Tenant 'TENANT_ID' -SubscriptionId 'SUBSCRIPTION_ID' (PowerShell) to run the post-provisioning scripts.
Your user account does not have permissions to run az or azd CLI commands due to a policy in Entra ID.
Symptoms:
When running post-provisioning scripts, you encounter errors like this one (external users are not allowed to access resources):
ERROR: AADSTS530004: AcceptCompliantDevice setting isn't configured for this organization. The admin needs to configure this setting to allow external users access to protected resources. Trace ID: c6d5b92a-0559-4477-a7e7-e42ae19d3200 Correlation ID: b95cc6b5-4bef-4c35-9261-688c481f8dbc Timestamp: 2024-06-03 20:25:56Z
Cause:
In this case, you can choose to create a service principal, grant it contributor permission on the subscription, and log in with the service principal using the AZD CLI, AZ CLI and Connect-AzAccount if using powershell (windows).
Zero-trust deployment from a machine outside its vnet
Symptoms:
Deploying services (azd deploy)
(x) Failed: Deploying service dataIngest
ERROR: failed deploying service 'dataIngest': failing invoking action 'deploy', POST https://...scm.azurewebsites.net/api/zipdeploy
--------------------------------------------------------------------------------
RESPONSE 403: 403 Ip Forbidden
ERROR CODE UNAVAILABLE
Cause:
For deployment of the zero trust components, it is necessary to perform it from the VM created during the process.