cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Serverless outbound internet still restricted after upgrading express setup trial to Premium

Innovation1
New Contributor II

Hi all,

I started a Databricks trial with express setup on AWS and upgraded to Premium pay-as-you-go on Oct 19, 2026. Serverless compute in my workspace can only reach a short list of domains. All other public sites are refused at DNS.

Test run on serverless jobs compute:
- pypi.org: 200
- github.com: 200
- news.mit.edu: "Temporary failure in name resolution"
- www.coindesk.com: "Temporary failure in name resolution"

system.access.outbound_network shows these lookups as access_type = DROP, DNS rcode 5 (REFUSED), network_source_type = General Compute.

The account console has no network policy (egress control) settings, since that's Enterprise-tier only, so I can't change this myself. I don't have a support plan, so I can't open a ticket.

My use case is a daily job that fetches public RSS feeds and financial data APIs.

Is the trial's "limited external network access" expected to persist after upgrading to Premium? If not, how can I get it lifted? Any Databricks staff who can help would be much appreciated.

Thanks,
James

2 REPLIES 2

Satyasai
Contributor

The behavior you are observing is expected for Serverless Compute created during or converted from an Express Setup trial and upgrading to Premium pay-as-you-go does not automatically remove these serverless egress restrictions.

Root Cause

When a Databricks workspace is created via Express Setup (or during the initial trial period), Databricks provisions Serverless Compute inside a Databricks-managed AWS VPC protected by a restrictive Default Serverless Egress Policy.

Default Restricted Allowlist: By default, Express Setup serverless environments restrict egress traffic via a managed DNS firewall to a tight allowlist of standard developer infrastructure domains (e.g., PyPI, GitHub, AWS S3, Databricks control plane).

DNS Refusal (rcode 5): Unapproved destinations (like news.mit.edu or [www.coindesk.com](https://www.coindesk.com)) are dropped directly at the Databricks-managed DNS firewall layer, producing the access_type = DROP and DNS rcode 5 (REFUSED) entries in system.access.outbound_network.

Account Console Access: Custom Account-Level Network Egress Policies (which allow configuring custom allowlists or switching to unrestricted internet egress for serverless) require the Enterprise tier. Since your workspace is on the Premium tier, the Egress Control UI in the Account Console is unavailable.

Resolution Options

Option 1: Use Classic Compute (Immediate Fix)

The serverless network restrictions apply only to Serverless Compute managed inside Databricks VPCs.

If you run your daily RSS and API fetching jobs on Classic Compute (single-node or multi-node clusters running in your own AWS account VPC via Customer-Managed VPC setup, or standard non-serverless job clusters):

Create a standard Job Cluster or All-Purpose Cluster in your workspace.

Route your daily ingestion notebooks to execute on this classic compute cluster.

Outbound HTTP/DNS calls will bypass the Databricks Serverless DNS firewall and use your AWS VPC's standard Internet Gateway / NAT Gateway setup, granting unrestricted access to public news and financial APIs.

Option 2: Request Manual Policy Relaxation from Databricks Support / Account Team

Although self-service account-level egress policy management requires Enterprise tier, Databricks internal operations can manually remove or relax the default express serverless egress restriction on Premium trial/converted workspaces upon request.

Since you do not have a paid Support Plan to open a formal ticket via the Support Portal:

Post on the Databricks Community Forums:

Create a post under the Workspace Management & Infrastructure or Databricks on AWS board in the Databricks Community Forum.

Include your Workspace ID (from your URL https://adb-.azuredatabricks.net), region, and a description of your issue:

"Upgraded workspace from Express trial to Premium pay-as-you-go. Serverless compute egress is still blocked by default trial DNS firewall (access_type = DROP, rcode 5). Need default serverless egress policy lifted for arbitrary public API ingestion."

Databricks Community Managers and Developer Advocates regularly monitor these posts and can escalate your Workspace ID internally to engineering to unblock egress.

Thanks, that matches what I'm seeing. Requesting that the default Express Serverless egress restriction be lifted for this workspace:

  • Cloud: AWS
  • Workspace ID: 7474645436260685
  • Region: us-west-2
  • Upgraded from express setup trial to Premium pay-as-you-go on Oct 19, 2026
  • Serverless egress is blocked at the DNS firewall (access_type = DROP, rcode 5); pypi.org and github.com work, but other public domains don't
  • Use case: daily ingestion of public RSS feeds and financial data APIs

Could a community manager please escalate? Happy to share anything else privately.