Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Greetings, all. I work in an industry that deals with highly sensitive data and am wondering if notebooks that run PySpark (and evnetually T-SQL notebooks) are, well, secure. Beyond the native Microsoft protections, are there particular steps that need to be taken to harden notebook security so that data flowing through and being printed is protected?
Solved! Go to Solution.
Hi @arpost,
Current it seems not include additional options(except notebook permissions) to increase the security about the notebook usage.
How to use notebooks - Microsoft Fabric | Microsoft Learn
Perhaps you can try to use current notebook to invoke target notebook to prevent the code leak.
Microsoft Spark Utilities (MSSparkUtils) for Fabric - Microsoft Fabric | Microsoft Learn
In addition, if you mean data security about the notebook usages. You can try to storage the data into the data warehouse which include lots of level of security options and use shortcut to reference the data to security the data usages:
Security for data warehousing - Microsoft Fabric | Microsoft Learn
Regards,
Xiaoxin Sheng
Hi @arpost,
Current it seems not include additional options(except notebook permissions) to increase the security about the notebook usage.
How to use notebooks - Microsoft Fabric | Microsoft Learn
Perhaps you can try to use current notebook to invoke target notebook to prevent the code leak.
Microsoft Spark Utilities (MSSparkUtils) for Fabric - Microsoft Fabric | Microsoft Learn
In addition, if you mean data security about the notebook usages. You can try to storage the data into the data warehouse which include lots of level of security options and use shortcut to reference the data to security the data usages:
Security for data warehousing - Microsoft Fabric | Microsoft Learn
Regards,
Xiaoxin Sheng