Networking Setup in Standard Tier – VNet Integration and Proxy Issues

[martkev]

Hi everyone,

We are working on an order forecasting model using azure databricks and an ml model from Hugging Face and are running into an issue where the connection over SSL (port 443) fails during the handshake (EOF Error SSL 992). We suspect that a corporate proxy or firewall might be interrupting the connection.

Here’s the situation:

• We are using Databricks Standard Tier, where VNet integration is supposedly not available, but our Databricks workspace is connected to a VNet which in theory should have a corporate proxy attached.
• The cluster has no Public IP, and we’re unsure how the traffic is routed internally.
• We’re considering upgrading to Premium Tier to take advantage of VNet and other features, but for now, we’d like to understand the networking in Standard Tier.

Can anyone explain how networking works in the Standard Tier, especially around VNet usage? Could the lack of Public IP and the corporate proxy be causing our SSL connection issues? Ideally, we'd want to configure public IPs or allow the cluster to use our organization's IP range through the proxy / firewall.

Thanks for any guidance! Also if you have a good bicep or ARM template feel free to share. 

[arjun_kr]

It may depend on your UDR setup. If you have a UDR rule routing the traffic to any firewall appliance, it may possibly be related to traffic not being allowed in the firewall. If there is no UDR or UDR rule routes this traffic to the Internet, it would be using default outbound access provided by Azure as explained in the below link.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access#when-is...

It would be recommended to disable public IP. If there is a firewall in place, you may need to reach out to the admin team to look into the connectivity from your Databricks vnet being blocked.