Unity Catalog Data Masking Propagation
AnnouncedLast seen at this status: 2026-05-15·May 2026
Automatic propagation of Unity Catalog masking policies to each new Lakebase database branch when it is created, so development, CI and test branches copied from production data are masked the same way as production.
Status history
- Announced
Sources (1)
- 2026-05-15Databricks Blog Announced
Recent coverage
- 2026-11-18Migrate Databricks classic workloads to serverless with Genie Migrate | Databricks Demo video
- 2026-11-18Multi-Statement Transactions in Unity Catalog: Atomic Writes on Delta and Iceberg video
- 2026-11-17Advancing Catalog Interoperability with Unity Catalog and Google Cloud’s Borderless Lakehouse news
- 2026-11-17Azure Databricks sessions at Microsoft Ignite 2026 news
- 2026-11-17The new Azure Databricks on Azure Government is now in Beta news
- 2026-11-17How to Reduce AI Agent Costs | Unity Gateway Insights video
Get Tuesday's version of this
What shipped in Databricks and why it matters, once a week. Free, one-click unsubscribe.
Read past issues first
Statuses and dates come from public Databricks sources only. We do not see the private roadmap Databricks shares with customers. If something looks wrong, report a correction.