Fabric Security Issues

Hi Anonymous ,

Thanks for reaching out to the Microsoft fabric community forum.
suparnababu8  Thanks for your prompt response

Anonymous ,

Potential Workarounds
Given the current limitations, here are some strategies you might consider:

Separate Workspaces for Different Layers:

Maintain separate workspaces for ingestion (bronze) and curated (silver/gold) layers.

Restrict access to the ingestion workspace to only service principals or specific users responsible for data ingestion.

Grant the curated team access only to the curated workspace, ensuring they cannot modify raw data .

Use of Viewer Role with SQL Endpoint:

Assign the Viewer role to users in the curated workspace.

Instruct users to access data exclusively through the SQL analytics endpoint, which enforces read-only access.

Note that this approach limits users from using notebooks or the Lakehouse UI for data exploration.

Implement Row-Level and Column-Level Security:

Within the curated workspace, apply Row-Level Security (RLS) and Column-Level Security (CLS) to control data access at a more granular level.

This ensures that even if users have broader access, they can only view data they're authorized to see.

Monitor and Audit Activities:

Implement monitoring and auditing to track data access and modifications.

While this doesn't prevent unauthorized changes, it can help in identifying and addressing them promptly.

Lakehouse sharing and permission management - Microsoft Fabric | Microsoft Learn
Give users access to workspaces - Microsoft Fabric | Microsoft Learn
Implement medallion lakehouse architecture in Fabric - Microsoft Fabric | Microsoft Learn

If this post helped resolve your issue, please consider giving it Kudos and marking it as the Accepted Solution. This not only acknowledges the support provided but also helps other community members find relevant solutions more easily.

We appreciate your engagement and thank you for being an active part of the community.

Best regards,
LakshmiNarayana.