Azure / Azure/azure-quickstart-templates
201-vm-domain-join - VM Deployment Error
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
201-vm-domain-join https://github.com/Azure/azure-quickstart-templates/tree/master/201-vm-domain-join
### Issue Details
Running into resource provisioning error during VM deployment:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"InvalidResourceReference\",\r\n \"message\": \"Resource /subscriptions/xxxxxxxxxxxxxxxxxxxxxxxxxxx/resourceGroups/IT-West/providers/Microsoft.Network/virtualNetworks/USWEST2/subnets/IT referenced by resource /subscriptions/xxxxxxxxxxxxxxxxxxxxx/resourceGroups/IT-West/providers/Microsoft.Network/networkInterfaces/testvm0001Nic was not found. Please make sure that the referenced resource exists, and that both resources are in the same region.\",\r\n \"details\": []\r\n }\r\n}"}]}
### Repro steps (*if necessary, delete otherwise*)
1. Using Deploy to Azure function via Github
2. Enter valid parameters
3. Deploy
4. Error
5.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the 201-vm-domain-join template linked in the issue and inspect the VM, network interface, virtual network, and subnet parameters involved in the reported deployment. Reproduce the Deploy to Azure flow with valid parameters and use the ARM deployment-operation details; done means the template deploys without the InvalidResourceReference error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100