You might know about the security and privacy approaches in SQL Server and Azure SQL Database, but what about Fabric SQL and Fabric Data Warehouse? But Fabric changes the shape of the problem.

In Fabric, security is not just a list of features. It is a set of design decisions across multiple engines, access paths, and layers of control. Some of those decisions are made for you; others are not. Knowing the difference matters.

We will look at familiar security and privacy concepts, then ask a simple question for each one: What does this decision look like in Fabric SQL Database? And what does it look like in Fabric Data Warehouse?

We will focus on the dilemmas that data professionals actually face:

- Identity
- Access control
- Row-level security
- Dynamic data masking
- Encryption
- Auditing
- Monitoring
- Network security
- Data classification

Each concept will be framed as a choice, with trade-offs in cost, benefit, and risk.

The goal is not to memorize features. The goal is to build a mental model to help you make better security and privacy design decisions for Fabric databases.