Lakebase Now Enabled by Default in Databricks Compliance Security Profile Workspaces
Databricks has enabled Lakebase by default for all workspaces configured with a compliance security profile, including those adhering to HIPAA, C5, or TISAX standards, or using the profile without a specific standard. This change eliminates the need for manual Lakebase enablement in these environments. It streamlines data protection setup for users managing sensitive workloads under strict regulatory requirements. The update simplifies configuration and reduces administrative overhead.
Features (1) ›
- Lakebase Enabled by Default in Compliance Security Profile Workspaces
Lakebase is now enabled by default in all Databricks workspaces utilizing the compliance security profile. This includes workspaces that meet HIPAA, C5, or TISAX standards, as well as those with the profile enabled without a specific compliance standard. Users no longer need to manually enable Lakebase in these environments.
https://docs.databricks.com/aws/en/release-notes/lakebase#lakebase-is-enabled-by-default-in-compliance-security-profile-workspaces
Related releases
- Southern Company Enhances Storm Response with Databricks-Powered SCOUT Databricks Blog ·
- Databricks AI Search Enhances Querying with Struct/Map Column Support and Filter-Only Queries Databricks Release Notes ·
- Databricks Unity Gateway API now supports programmatic resource management Databricks Release Notes ·
- Schema-level HTTP connections in Databricks Unity Catalog are now GA Databricks Release Notes ·
- Databricks-managed MCP Connectors Integrate with Unity Gateway in Beta Databricks Release Notes ·
- Databricks-managed MCP Connectors Integrated with Unity Gateway (Beta) Databricks Release Notes ·