What causes SECRET_NOT_FOUND?

The secret key was deleted from the scope during a credential rotation. The key name in the code contains a typo or different casing. The secret was added to a different scope than the one referenced in the code. The secret scope is backed by Azure Key Vault and the Key Vault secret was disabled or expired

How do I fix SECRET_NOT_FOUND?

Step 1: List secrets in the scope to confirm the key: databricks secrets list --scope .. Step 2: Fix any typo in the scope or key name in the notebook or job configuration.. Step 3: Re-add the secret with the correct key name using the Databricks CLI or REST API.. Step 4: For Key Vault-backed scopes, verify the Key Vault secret is active and not expired in the Azure portal.. Step 5: Review access control on the scope — the running principal must have READ permission on the scope.

High severityconfiguration

Power BI Refresh Error:
SECRET_NOT_FOUND

What does this error mean?

A notebook or job called dbutils.secrets.get with a key that does not exist in the specified secret scope, usually because the key was deleted, renamed, or the scope was spelled incorrectly.

Common causes

1The secret key was deleted from the scope during a credential rotation
2The key name in the code contains a typo or different casing
3The secret was added to a different scope than the one referenced in the code
4The secret scope is backed by Azure Key Vault and the Key Vault secret was disabled or expired

How to fix it

1Step 1: List secrets in the scope to confirm the key: databricks secrets list --scope <scope-name>.
2Step 2: Fix any typo in the scope or key name in the notebook or job configuration.
3Step 3: Re-add the secret with the correct key name using the Databricks CLI or REST API.
4Step 4: For Key Vault-backed scopes, verify the Key Vault secret is active and not expired in the Azure portal.
5Step 5: Review access control on the scope — the running principal must have READ permission on the scope.

Frequently asked questions

Can I list secrets in a scope without knowing the key names?

Yes — run databricks secrets list --scope <scope-name> in the CLI. It shows key names but not values, for security. From a notebook, use dbutils.secrets.list('<scope>').

What is the difference between a Databricks-backed and Azure Key Vault-backed secret scope?

Databricks-backed scopes store secrets inside Databricks. Key Vault-backed scopes reference secrets in Azure Key Vault and sync them at read time. Key Vault-backed scopes are preferred for enterprise environments where Key Vault is the central secrets manager.