Hello , Welcome to MS Q&A
Your issue is due to Azure Databricks-managed resource groups being locked by the system, preventing users from making direct modifications. This is why you are encountering DENY permissions when trying to create a Public IP/NAT Gateway within the Databricks resource group.
✅ Recommended Approach: Attach NAT Gateway to a Custom-Managed V-Net
- Check if Your Databricks Workspace Uses a Managed or Custom VNet
- If your workspace was deployed without a custom VNet, Azure automatically manages the networking, and you cannot modify the Databricks resource group.
- You need to recreate the workspace using a VNet-injected (custom VNet) deployment.
- Deploy Databricks with a Custom VNet
- Create a new Databricks workspace with the VNet injection option.
- In this setup, Databricks deploys its cluster nodes into a custom V-Net that you control.
- Attach a NAT Gateway and Standard Public IP to the custom V-Net’s outbound subnet .
- Move Workloads to the New Workspace
- Since you cannot modify the existing Databricks-managed resource group, you must migrate your notebooks, clusters, and jobs to the new Databricks workspace.
Please let me know if any further ques
Kindly accept answer if it helps
Thanks
Deepanshu