A security retirement can be clearly necessary while its operational consequences remain uneven.
The pressure is to remove a known exposure without converting a controlled migration into widespread data interruption.
Who you’d be doing this for
“I agree the old auth has to go, but a surprise outage during close would be brutal.”
Smita Banerjee · Director of Data Engineering
Leads a team whose revenue and compliance pipelines use several affected external-source connectors.
What is at stake
One authentication mode has a confirmed flaw and has to be off in every managed workspace within 21 days. You have to sequence migration and enforcement so exposure closes without breaking data delivery.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- vulnerability closure vs. pipeline continuity
- automation speed vs. verified compatibility
- fixed deadline vs. limited customer windows
- uniform enforcement vs. risk-based sequencing
Why Databricks
At Databricks, this can matter because managed data connectivity often carries both sensitive access paths and time-bound analytical dependencies.
Written with these in mind
Not your kind of problem? 34 more at Databricks, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.