Enable Item-Level and Block-Level Security in Microsoft Fabric

[toabdullaji]

Microsoft Fabric currently provides item permissions at the workspace level, meaning anyone with workspace access can see all objects, such as notebooks, pipelines, dataflows, lakehouses, etc.

However, there is no way to secure specific Item/blocks inside items, such as notebook/cells or pipeline/activities, dataflows/tables because Fabric does not support Item/block-level security. Notebook “freeze/lock” options do not provide real security. 

Requested Features

1. Item-Level Security Enhancement

• Allow specific Fabric items (notebooks, pipelines, dataflows, tables, etc.) to be fully hidden from other workspace users unless explicitly granted access.
• Workspace users should not see secured items in the workspace item list unless they have permissions.
• The item owner should always retain access.

2. Block-Level Security (New Capability)

• Add ability to secure blocks inside items, such as:
  • Notebook cells
  • Pipeline activities
  • Dataflow steps
• These blocks should be hidden from users who are allowed to run the item but are not allowed to view sensitive logic.

Why This Is Needed

• Prevent exposure of sensitive business logic, rules, credentials, and proprietary algorithms.
• Support proper separation of duties inside shared workspaces.
• Avoid creating unnecessary extra workspaces solely for security isolation.