Session

Architecting secure Microsoft Fabric solutions

Answering our analytical questions using Microsoft Fabric becomes a breeze, no matter if we have to wade through vast amounts of data, leveraging the power of the lakehouse or the warehouse, or need to analyze events in real time. Finally, we are creating impactful data visualizations. Architecting solutions harvesting from the concepts of the Data Mesh is simple by shortcutting to the data needed for creating data products without the need to copy the data again and again.

But architecting powerful solutions also means keeping our data assets safe. Keeping our data safe does not only mean preventing items from accidental harm, or protecting access to the Fabric tenant using conditional access policies. Keeping our data safe also means providing the least required access permissions to users of this data throughout our organization. No matter if these users are utilizing data from remote workspaces when developing data pipelines, building AI applications, or consuming data using Power BI apps (yes, I'm referring to you, my new friend, the org app).

After briefly introducing some Azure Security features, this session focuses on OneLake Security, which was publicly showcased during FabCon 2025 Vegas in March 2025. OneLake Security must be considered the lingua franca for security in Microsoft Fabric, as it builds on top of OneLake. With OneLake security, we can define security on the delta tables we own, which are at the foundation of every Fabric solution. All compute engines in all downstream solutions will honor this security layer. Even if this session focuses on OneLake security, some security features of items like the warehouse or Power BI's semantic model will be explained as they help refine security aspects for downstream development.

This session addresses the needs of solutions architects to understand how to secure our data assets when architecting Fabric solutions. However, a workspace admin or developer will also benefit from this session because sometimes, there is no dedicated security officer on the solution team.

Tom Martens

Solution Architect @ Munich Re

Hamburg, Germany

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top