OneLake security
Product
OneLake security lets organizations define role-based access, including row-level and object-level restrictions, once on data in OneLake so it applies across Fabric engines and endpoints.
مواضيع تُناقش أيضًا
في الحلقة التي تتناول OneLake security تُناقش أيضًا: Delta table، Ontology in Microsoft Fabric، Data mesh، Fabric Mirroring، Microsoft Fabric Apps وDataflow Gen2.
Description
OneLake security is a role-based access control model for data stored in OneLake, the unified storage layer of Microsoft Fabric. It lets administrators define access rules once, directly on the data, so the same rules apply across Fabric engines and endpoints instead of being rebuilt separately in each tool. Row-level and object-level restrictions are part of the model, which allows access to be narrowed to specific folders, tables, rows or columns.
In practice, an administrator creates security roles that grant access to specific folders or tables inside a Fabric item and then assigns those roles to users or groups. Row-level and column-level security can narrow table access further. A ReadWrite permission, available only for lakehouses, allows writing through Spark notebooks, the OneLake file explorer or OneLake APIs without granting rights to manage Fabric items. Creating roles requires write and reshare permission, which workspace admins and members usually hold. According to the Microsoft Learn documentation, lakehouses and mirrored items are listed as supported.
New items come with a DefaultReader role. Its membership is virtualized, so anyone who holds the needed permission, such as ReadAll, is automatically a member. Because this role grants full access, the documentation notes that users should be removed from it once they are placed in a more restrictive role; otherwise the broader access remains in effect. Users who have no data access role at all see no data in the item.
SQL analytics endpoints need specific attention. New endpoints start in delegated identity mode and are not protected by OneLake security until the access mode is switched to the user's identity mode. This is a typical decision point when rolling out OneLake security, since the protection only reaches that endpoint once the mode is changed.
OneLake security is one layer in a wider security picture. The episode "Microsoft Fabric End-to-End: From Raw Data to Business Decisions with Amit Chandak [MVP]" describes security across multiple layers, starting with Fabric workspace roles and continuing through item-level access, OneLake security and semantic-model security. In that discussion, Amit Chandak recommends using security groups rather than managing individual users wherever possible. Microsoft Entra provides the identity and group foundation, while Fabric applies those identities and groups to workspaces, items and data access. Assigning OneLake security roles to groups fits this approach.
The episode "Microsoft Fabric 2025 Updates Explained" mentions OneLake Security improvements alongside new governance tools, describing them together as part of an enterprise-grade foundation for secure data operations. The episode frames these changes in the context of real-time intelligence and the wider set of Fabric updates it covers.
Taken together, the sources present OneLake security as a way to centralize data-level access control in Fabric: roles are defined on the data in OneLake, assigned to Entra identities and groups, and enforced consistently by the engines that read the data, provided the endpoint is configured to use the user's identity.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Product |
|---|
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: