← All updates Databricks Update One-Pager Light version
databricks Platform · Updated Jul 21, 2026

Context-Based Ingress Control

Now generally available for enhanced workspace security.

What it does

Context-based ingress control allows account admins to define allow and deny rules that combine user identities, network sources, and request types to manage access to Databricks workspaces. This feature works alongside existing IP access lists and enables granular control over who can access workspace endpoints. It supports both public and private access policies and can be configured at the account level to govern multiple workspaces simultaneously.

Why it matters

This update enhances security by ensuring that only trusted combinations of identity and network source can access sensitive workspace resources, thereby reducing the risk of unauthorized access. It benefits organizations by providing a flexible and detailed access control mechanism that can adapt to various user scenarios, improving governance and compliance while minimizing potential security breaches.

Key capabilities
Granular Access Control
Define specific rules based on user identity, network source, and request type.
Audit Logging
Capture detailed logs of denied requests for monitoring and compliance.
Flexible Policy Enforcement
Choose between enforced rules and dry run mode to evaluate policy impacts.
Support for Multiple Workspaces
Manage ingress policies at the account level to apply to multiple workspaces.
Prerequisites
Requires the Enterprise tier of Databricks.
Recommended use cases
Restrict access from untrusted networks by requiring trusted network sources.Allow SaaS clients with dynamic IPs to access Databricks resources securely.Limit access to specific APIs or UI components based on user identity.Protect sensitive automation by restricting service principals to trusted networks.
Limitations · remember
!Account-level context-based ingress policy is currently in Beta.
!Denials for account-policy are not yet logged.
Architecture
Account Level Policies → Workspace Access Control → Network Source Evaluation → Identity Management
Get started
1
Access Ingress Policies
Navigate to the context-based ingress policies management section.
2
Define Rules
Create allow and deny rules based on identities and network sources.
3
Set Enforcement Mode
Choose between enforced rules or dry run mode for testing.
4
Monitor Logs
Review logs in the system.access.inbound_network table for denied requests.
5
Apply to Workspaces
Assign the ingress policy to the desired workspaces.
Key takeaway
Context-based ingress control provides robust security for Databricks workspaces by allowing precise access management based on user identity and network context.
2026-07-21-6190a78c Generated by the Databricks Updates Agent · browse all updates