3. Triage the issues

Check the failures, fix the problems and rerun azd up to continue the automation steps.

Visit deployment details

From the command output, find the hint: You can view detailed progress in the Azure Portal: And visit the link to see the details of your deployment.

In your deployment page, you may click each Resource link, and check the Inputs/Output variables for better triage.

Failed to provision java component ‘configserver’

ERROR: error deploying infrastructure: deploying to subscription:

Deployment Error Details:
JavaComponentOperationError: Failed to provision java component 'configserver'. Error details: Failed to create config map external-auth-config-map for JavaComponent configserver in k8se-system namespace. There will be no re-tries..

This is a temporary error in service, just ignore and retry.

Failed to deploy open AI instance
```
InvalidTemplateDeployment: The template deployment 'openai' is not valid according to the validation procedure. The tracking id is 'xxx'. See inner errors for details.
SpecialFeatureOrQuotaIdRequired: The subscription does not have QuotaId/Feature required by SKU 'S0' from kind 'OpenAI' or contains blocked QuotaId/Feature.
```
Azure OpenAI is not enabled in your subscription + region settings, please check the feature status. You may edit the configurations in ./infra/bicep/main.parameters.json
- Disable openAI by set enableOpenAi = false and run azd up.
- Find a subcription + region combination and set the values openAiSubscription, openAiLocation, and run azd up.
- Use an existed openAI instance. See guide in page Reuse existing resource
Provisioning in requested region is not supported.
```
Provisioning in requested region is not supported. (Code: ProvisionNotSupportedForRegion)
```
Goto the portal deployment portal page, locate the failed resource, and check the feature support status of that features.
Resource or SKU is not supported in target subscription + region settings, please check the feature status.
- Use an existed resource instance. See guide in page Reuse existing resource
Run post-provision script failed

Resource not found
```
 ERROR: error executing step command 'provision': failed running post hooks: 'postprovision' hook failed with exit code: '1', Path: './infra/bicep/hooks/postprovision.sh'. : exit code: 1, stdout: 
 ...
 Message: Resource group 'xxx' could not be found.
```
This happens if you have default group in your az default config but the target group is not exist. Follow these steps to fix this
- Check the config with command az config get defaults, find the default group name ‘xxx’
- Unset the default group config with command az config unset defaults.group
- Run azd up again
Check your az login status:

Run az account show -o table to see if you are already login to your target subscription. If not, run these commands:

az login --use-device-code

az account set -s <subscription>