Azure / Azure/azure-quickstart-templates
quickstarts/microsoft.databricks/databricks-workspace-with-vnet-injection not working with API version error
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
Hi Team
I am working on service tag on-boarding, need to enable SCC on existing workspace. As prerequisite I need to finish vnet injection on my existing workspace and existing vnet.
[Deploy Azure Databricks in your Azure virtual network (VNet injection) - Azure Databricks | Microsoft Learn](https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/vnet-inject#arm-workspace)
is refering to template in this repo https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.databricks/databricks-workspace-with-vnet-injection
But the template is not working with following error:
`{"code":"DeploymentFailed","target":"/subscriptions/69b8bad6-4fb9-4efc-b982-3bf15ccb8857/resourceGroups/servicetag_databricks/providers/Microsoft.Resources/deployments/Microsoft.Template-20250617161128","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"VirtualNetworkIdChangeNotAllowed","message":"Updating required Virtual Network from to /subscriptions/69b8bad6-4fb9-4efc-b982-3bf15ccb8857/resourceGroups/servicetag_databricks/providers/Microsoft.Network/virtualNetworks/vnet_for_injection is allowed only in api-version 2025-02-01-preview or beyond"}]}`
Meanwhile I have updated my template to use workspace api version 2025-03-01-preview, my template and deployment failure attached, can some one help on this?
[template.json](https://github.com/user-attachments/files/20771367/template.json)
[Deployment-Microsoft.Template-20250617154153.zip](https://github.com/user-attachments/files/20771369/Deployment-Microsoft.Template-20250617154153.zip)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.