Skip to content

Fix API version for databricks-workspace-with-vnet-injection to support existing workspace VNet updates#14547

Closed
Copilot wants to merge 2 commits intomasterfrom
copilot/fix-14515
Closed

Fix API version for databricks-workspace-with-vnet-injection to support existing workspace VNet updates#14547
Copilot wants to merge 2 commits intomasterfrom
copilot/fix-14515

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Jul 3, 2025

Updates the Azure Databricks workspace template API version to support VNet injection on existing workspaces.

Problem

The current template fails when trying to apply VNet injection to existing Databricks workspaces with the following error:

VirtualNetworkIdChangeNotAllowed: Updating required Virtual Network from  to /subscriptions/.../providers/Microsoft.Network/virtualNetworks/vnet_for_injection is allowed only in api-version 2025-02-01-preview or beyond

Solution

Updated the Microsoft.Databricks/workspaces API version from 2024-05-01 to 2025-02-01-preview to support VNet updates on existing workspaces.

Changes Made

  • Updated API version in main.bicep from 2024-05-01 to 2025-02-01-preview
  • Rebuilt azuredeploy.json from the updated Bicep template
  • Updated metadata.json with current date

Testing

  • ✅ Template syntax validation passes
  • ✅ JSON structure validation passes
  • ✅ Deployment file validation passes

This change maintains backward compatibility for new workspace creation while enabling the VNet injection scenario described in the Azure Databricks VNet injection documentation.

Fixes #14515.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

  • aka.ms
    • Triggering command: bicep build main.bicep --outfile azuredeploy.json (dns block)
    • Triggering command: bicep build main.bicep --outfile /tmp/test-output.json (dns block)
    • Triggering command: pwsh -NoProfile -Command try { & './test/ci-scripts/Validate-Metadata.ps1' './quickstarts/microsoft.databricks/databricks-workspace-with-vnet-injection/metadata.json'; Write-Host 'Metadata validation passed' } catch { Write-Host 'Metadata validation failed:' /home/REDACTED/work/azure-quickstart-templates/azure-quickstart-templates.Exception.Message } (dns block)

If you need me to access, download, or install something from one of these locations, you can either:


💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

…rt existing workspace VNet updates

Co-authored-by: anthony-c-martin <38542602+anthony-c-martin@users.noreply.github.com>
Copilot AI changed the title [WIP] quickstarts/microsoft.databricks/databricks-workspace-with-vnet-injection not working with API version error Fix API version for databricks-workspace-with-vnet-injection to support existing workspace VNet updates Jul 3, 2025
Copilot AI requested a review from anthony-c-martin July 3, 2025 16:26
@alex-frankel
Copy link
Copy Markdown
Contributor

Thanks for getting started on this. We're closing stale drafts (no updates in 90+ days) as we transition to the new CI process — see #14715 for the new submission requirements. If you'd like to continue, please rebase against master, ensure the new testResult block is populated in metadata.json (contribution guide), and reopen this PR or submit a fresh one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

quickstarts/microsoft.databricks/databricks-workspace-with-vnet-injection not working with API version error

4 participants