Skip to content

Add azure-vnet-injection-multi: deploy multiple Azure workspaces sharing a single VNet#37

Open
hanluzhang-db wants to merge 1 commit intodatabricks-solutions:mainfrom
hanluzhang-db:hzhang-new-feature/add-azure-vnet-injection-multi-workspace
Open

Add azure-vnet-injection-multi: deploy multiple Azure workspaces sharing a single VNet#37
hanluzhang-db wants to merge 1 commit intodatabricks-solutions:mainfrom
hanluzhang-db:hzhang-new-feature/add-azure-vnet-injection-multi-workspace

Conversation

@hanluzhang-db
Copy link
Copy Markdown

@hanluzhang-db hanluzhang-db commented Apr 20, 2026

Pull Request

Description

Adds a new azure-vnet-injection-multi example under workspace-setup/terraform-examples/azure/. It provisions multiple Azure Databricks workspaces into a single newly-created VNet in one Terraform run. Each workspace gets its own subnets (public/private), NSG, NAT Gateway, and Public IP while sharing the VNet.

Per the original Automation-with-IaC ticket, the implementation is intentionally minimal: it only supports creating a new VNet. For single-workspace deployments or existing-VNet injection, users should use the sibling azure-vnet-injection example.

Ref: Automation with IaC — azure-vnet-injection-multi (deploy multiple workspaces at once). Original contributor: Yotaro Enomoto.

Note: Only terraform validate and terraform fmt were run locally. End-to-end terraform apply on Azure has not been executed — validation only confirms syntax and provider schema correctness, not that the deployment succeeds in practice.

Category

  • core-platform
  • data-engineering
  • data-governance
  • data-warehousing
  • genai-ml
  • launch-accelerator
  • workspace-setup

Type of Change

  • New project
  • Bug fix
  • Enhancement
  • Documentation

Project Details

Project Name: azure-vnet-injection-multi
Purpose: Deploy multiple Azure Databricks workspaces sharing a single VNet in one Terraform run
Technologies Used: Terraform, Azure, Databricks

Testing

  • Code runs without errors
  • Documentation is complete
  • Used only synthetic data

Security Compliance ✅

  • No customer data, PII, or proprietary information
  • No credentials or access tokens
  • Only synthetic data used
  • Third-party licenses acknowledged

By submitting this PR, I confirm I have followed the CONTRIBUTING.md guidelines and security requirements.

…ing a single VNet

New example under workspace-setup/terraform-examples/azure/ that provisions
multiple Azure Databricks workspaces into a single newly-created VNet in one
Terraform run. Each workspace gets its own subnets, NSG, NAT Gateway, and
Public IP while sharing the VNet.

Intentionally minimal — only supports creating a new VNet. For single-workspace
deployments or existing-VNet injection, use the sibling azure-vnet-injection
example.

Co-authored-by: Isaac
@yotaenom
Copy link
Copy Markdown

Hi @hanluzhang-db

Creating the Workspace currently fails with the error: Status: "RequestDisallowedByPolicy".
This appears to be caused by an Azure policy requiring an owner tag on all resources. Some resources in this PR are missing that tag.
Could you please add an owner tag to every resource to comply with the policy?

Screenshot 2026-04-22 at 14 55 30

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants