microsoft / microsoft/azurechat

`azd provision` fails with an avoidable error

Open
#533 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.4k
Forks
1.3k
Avg merge
1d 11h
Merged PRs (30d)
1

Description

  1. Created a brand new Azure account.
  2. Upgraded my subscription from "Free Trial" to "Pay-as-you-go".
  3. azd init - created the environment
  4. azd provision - supplied inputs as requested.
  5. Deployment failed with this error -
ERROR: deployment failed: error deploying infrastructure: validating deployment to subscription:

Validation Error Details:
InvalidTemplateDeployment: The template deployment 'azurechat-lab-1759362343' is not valid according to the validation procedure. The tracking id is 'b64d1897-199c-4a71-abbb-0277f9e05e65'. See inner errors for details.
ValidationForResourceFailed: Validation failed for a resource. Check 'Error.Details[0]' for more information.
SubscriptionIsOverQuotaForSku: Quota exceeded for : 0 VMs allowed, 1 VMs requested.. Try selecting different region or SKU.

Request for change to the provision script here - Why allow me to pick a region that it knows is invalid for a resource it knows this deployment will provision?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the azd provision flow and the infrastructure deployment validation that selects a region and SKU. Reproduce the failure with the reported subscription and deployment error, then verify that an invalid region is rejected or avoided before deployment and that the resulting guidance is clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.