One logical lake for analytics, RAG knowledge, and agentic AI.
AI Agentic Practice
Microsoft OneLake
Microsoft OneLake is the unified data lake for Fabric: a single logical lake with shortcuts to ADLS, Amazon S3, and more. Gensten designs OneLake layouts for analytics and AI - bronze/silver/gold zones, document corpora for RAG, ACL strategies, and secure paths into Azure AI Foundry and Fabric IQ - so your agentic stack reads from governed storage, not shadow copies.
Domain-oriented OneLake architecture
Shortcuts instead of duplicate copies
Document + table coexistence for RAG + BI
Security and lineage for agent retrieval
Cost-aware storage tiers and retention
Architecture Layers
How OneLake fits into a production agentic stack.
1
Landing / Bronze
Raw files, CDC, and partner drops via shortcuts.
2
Curated / Silver
Cleaned tables and normalized document stores.
3
Product / Gold
Business-ready datasets and RAG collections.
4
AI Consumption
Embedding pipelines, Fabric IQ, Foundry tools.
OneLake for RAG corpora
We store source documents and derived chunks with lineage so every agent citation maps back to an authoritative object in OneLake - essential for audits and content refresh.
Versioned document folders
Derived chunk/embedding datasets
Purge and legal-hold workflows
Cross-workspace shortcuts for shared knowledge
Avoiding data sprawl
Shortcuts let Fabric IQ and agents use data where it already lives. We inventories sources, choose shortcut vs. copy patterns, and prevent “RAG islands” that drift from the lakehouse.
Use Cases
Enterprise knowledge lake for copilots
Unified analytics + AI storage strategy
Multi-cloud data via OneLake shortcuts
Regulated data residencies with clear zones
Technologies & Platforms
Microsoft OneLakeMicrosoft FabricADLS Gen2Azure AI SearchAzure AI FoundryPurview
Frequently Asked Questions
Is OneLake only for Fabric analytics?
OneLake is Fabric’s lake, but it is also the right foundation for AI: document corpora, feature tables, and agent retrieval can all live (or shortcut) there under one governance model.
What is Microsoft OneLake?
OneLake is the unified logical data lake for Microsoft Fabric - one lake for files and tables, with shortcuts to ADLS, S3, and other sources without endless copy sprawl.
How does OneLake support RAG?
Store authoritative documents and derived chunk/embedding datasets with lineage, then index into Azure AI Search or vector stores so agents cite lake-backed sources.
What are OneLake shortcuts?
Shortcuts reference data in place (e.g., ADLS Gen2 or S3) inside OneLake so Fabric IQ and AI workloads can use existing lakes without duplicating every byte.
How should we zone OneLake for AI?
Bronze (raw), Silver (cleaned), Gold (business-ready / RAG collections), plus clear AI consumption paths. Sensitive domains get stricter workspaces and ACLs.
Can OneLake hold both tables and unstructured docs?
Yes. That coexistence is a major advantage: BI tables and RAG document corpora share governance, lineage, and domain ownership.
How do you prevent RAG data islands?
We inventory sources, prefer shortcuts over copies, version derived chunks, and require citations back to OneLake objects so shadow vector-only stores do not diverge.
Does OneLake replace our data warehouse?
Not necessarily. OneLake is the lake foundation; warehouses/lakehouses in Fabric still provide compute and serving. We design the right mix for analytics and agents.
How is security handled in OneLake for agents?
Workspace RBAC, sensitivity labels, and retrieval-time ACL filters ensure Foundry agents only access authorized domains and documents.
How does Gensten start a OneLake + AI engagement?
Map domains and sources, define bronze/silver/gold and RAG collections, implement shortcuts, then connect embedding/index pipelines and Foundry retrieval tools.