Christopher Finlan

What to do with the feature this week?

Use it to tighten the contract around a production notebook. Do not use it as an excuse to create a beautifully organized junk drawer. Be picky about what belongs in Resources If a file materially affects how the notebook runs, how the team validates it, or how someone maintains it at 2 a.m., it is probably a candidate.

What to do now?

Keep the rollout small and brutal. Start with one supported source. Enable DeltaFlow. Pick “Analytics-ready events & auto-updated schema.” Route it to a Spark notebook destination. Then measure three things: – How much parsing code vanished – How much schema handling vanished – How stable the preview behavior is under source changes One more signal is worth noticing.

What to do with that information?

The first operational question is not “What new permission do I need?” It is “Which workspace grants exist only because the old rule forced them?” Start there. List the semantic models your data agents use. Identify users or groups with workspace access granted only for those agent scenarios. Test the new flow with a read-only user as April 6 approaches.