Description

OneLake Shortcuts: Virtual Pointers, Real Tradeoffs

Episode 2 • 2026-01-09
Duration: 9:21

Matthias and Fabia break down OneLake shortcuts — virtual pointers that unify multi-cloud data without copies. They cover the read-write boundary, the shared credential security model, caching economics, and when a good old copy is actually the better architecture call.

What we discuss

• A real-world mistake from a pre-Fabric era
• The one question that reframes the architectural debate
• How we got here — predecessor products and evolution
• Why the "obvious" answer is often wrong
• A real Reddit/Microsoft Q&A question unpacked
• The concrete recommended architecture
• F-SKU realism — what this actually costs
• When the rejected approach is actually right
• Risks of the recommended path
• What Microsoft is shipping that changes the calculus
• The architectural principle to take home

Key takeaways

• That's it. Don't shortcut the architecture thinking just because the feature is called Shortcut.
• Completely fair. And in plenty of cases, that IS the right answer. I mean, architecture is not religion — if a nightly copy gives you better performance, lower cost, and simpler security? Do that. Shortcuts shine when data governance says...
• Security model. External shortcuts use stored credentials — one credential, shared by everyone who accesses that shortcut. That's a fundamentally different security posture than internal shortcuts, where your own identity passes through....

Resources

• OneLake Shortcuts
• Shortcut types
• Where to create shortcuts
• Shortcut authorization
• Shortcut caching
• Limitations
• Shortcut security
• Create OneLake Shortcut
• Create ADLS Gen2 Shortcut
• Create S3 Shortcut
• Create GCS Shortcut
• Shortcuts REST API
• On-premises Shortcuts
• Dataverse Shortcuts
• OneLake Overview

About the show

Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.

Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.

Submit your case

Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.

Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.