Hide password in Notebook

[tan_thiamhuat]

With Fabric Notebook alone, (not in Data Pipelines, where we can use Parameters), how do we hide the password in database connection string? I remember in Databricks, we can actually hide that cell which contains the password, but in Fabric, I do not see any option to hide the cell.

Thanks.

[burakkaragoz]

Hi @tan_thiamhuat ,

If your Microsoft Fabric capacity is paused, you will not incur compute charges during the paused period. However, if you're on a reserved capacity plan, you may still be billed for the reservation regardless of usage.

To confirm your specific billing scenario, please check your Azure subscription details or contact Microsoft support.

Hope this helps!

[suparnababu8]

Hi @tan_thiamhuat 

Yes, in databricks we can hide the password by using Azure Key vault secrets. Currentlly in Fabric there is no direct option to hide the passwords. 

The same way, how we did it in databricks, first you can store your database credentails in Azure Key Vault and later you can use that Azure secrets in Fabric notebooks. 

You can go thorugh this accepeted solution https://community.fabric.microsoft.com/t5/Fabric-platform/Protect-security-information-in-Fabric-Not... It might helps you to resolve your problem.

Thank you!

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

[tan_thiamhuat]

thanks for your reply. How about for customers who do not have the Azure account?

[v-hashadapu · Accepted solution]

Hi @tan_thiamhuat , Thank you for reaching out to the Microsoft Community Forum.

As of May 2025, Fabric Notebooks don’t offer native cell-hiding or built-in secret management like Azure Key Vault. You can store your credentials in a JSON file within OneLake or a Lakehouse. You can then load the credentials in your notebook at runtime. To keep this secure, use Fabric’s role-based access control (RBAC) to restrict access to the folder containing the file. OneLake encrypts data at rest by default and RBAC ensures only authorized users can access the sensitive file. This keeps passwords out of your notebook code and lets you automate processes without exposing secrets. Just be sure not to log or print the credentials in notebook output and avoid committing this file to any version-controlled repositories.

For development or one-off interactive tasks, a simpler option is to use Python’s getpass module to prompt the user to enter the password at runtime. This way, no password is stored in code or files, reducing the risk of accidental exposure. It’s ideal when you're running a notebook manually and don’t need automation.

If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.