What changed
Databricks now redacts SQL text in system query history and query-listing APIs and omits SQL-definition keys from audit request parameters. Account administrators and members of a dedicated databricks_pii_access group can still retrieve unmasked text. The release is staged and may reach accounts later.
Why it matters
Prompts, generated SQL, literals, table names, and business logic can leak through observability surfaces. Default masking changes both privacy exposure and the evidence available for debugging, security review, and incident response.
What to do
Inventory dashboards, exports, alerts, and agents that consume query history. Grant unmasked access narrowly, test redaction, preserve approved incident evidence, and document how investigators request temporary access.
Caveat
Masking is not retroactive proof that every log, trace, downstream export, or third-party integration is clean. Staged rollout, privilege inheritance, historical retention, and complete field coverage require workspace testing.