Skip to content

Managed_vnet_to_vnet_injection automation#42

Closed
josecisneros04 wants to merge 9 commits into
databricks-solutions:mainfrom
josecisneros04:main
Closed

Managed_vnet_to_vnet_injection automation#42
josecisneros04 wants to merge 9 commits into
databricks-solutions:mainfrom
josecisneros04:main

Conversation

@josecisneros04
Copy link
Copy Markdown

@josecisneros04 josecisneros04 commented Apr 28, 2026

Pull Request

Description

Brief description of what this PR does and why.

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:
Managed_vnet_to_vnet_injection automation
Purpose:
Updates Managed VNET for customization of networking
Technologies Used:
Powershell

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.

@haleyyyblue
Copy link
Copy Markdown
Collaborator

Hi @josecisneros04
Could you move this project folder under a new powershell-examples folder inside the workspace-setup directory?

Copy link
Copy Markdown
Contributor

@simranvanjani simranvanjani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @josecisneros04
Please add prerequisites such as :

Permissions: The customer (Cx) must possess sufficient privileges to deploy the required Azure resources. (Object Owner for current workspace as well as new VNET)
Downtime: This conversion requires planned downtime. Due to the complexity of a potential rollback, allocate ample time for the activity.
Private Link (PL) Endpoints: Private Link endpoints cannot be hosted on the subnets delegated to the Databricks workspace. A separate subnet must be used for hosting PL endpoints.
Subnet Usage: Use subnets that are not currently in use by other Databricks workspaces to avoid potential deployment errors.

Please also add post deployment test :

Upon successful deployment, you will observe that the Networking settings in your workspace are no longer grayed out.
Spin up a compute resource (cluster).
Locate the corresponding Virtual Machine (VM) in Azure using the cluster name in its tags.
Confirm that the VM is running within the VNet and subnets specified during the VNet injection process.

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.

3 participants