Forum Discussion
Protecting API keys and Credentials
- 18 days ago
Hi asosman,
Key Vaults are the intended solution here. Anything you put in a workspace can be read by others with access to the workspace.
Depending on the credential type, if Fabric has a native connector for it you may be able to create a fabric connection for it, but connections are not useable in all workloads.
Hi asosman, to add a few habits that help whichever option you choose. Keep notebooks that touch credentials in a separate workspace with a small set of members, and have the shared workspace consume only the outputs. When you create a connection, share it only with the specific users or groups who need it and do not give everyone in the workspace use permission. Never print or log a key in a cell, since notebook outputs are stored with the item and can be committed to Git. Finally, plan for rotation by keeping the key in one place so replacing it later does not mean editing every item.