Mounting error in Gen 1 with adls: Secret scope does not exist

KEERTHANA JAYADEVAN 66 Reputation points

I am constantly getting the below error:"Secret does not exist with scope: kvmigrn and key: clientid". Tried creating an app two times from scratch. I already have a vault like this and a key. Attaching screenshot

adb error.jpg


Azure Data Lake Storage
Azure Data Lake Storage
An Azure service that provides an enterprise-wide hyper-scale repository for big data analytic workloads and is integrated with Azure Blob Storage.
1,129 questions
Azure Databricks
Azure Databricks
An Apache Spark-based analytics platform optimized for Azure.
1,605 questions
0 comments No comments
{count} votes

Accepted answer
  1. Amira Bedhiafi 4,631 Reputation points

    The error is clear there is a missing secret in the specified Databricks secret scope.

    Ensure that the secret scope kvmigrn has been correctly created in Databricks. If you are using Azure Key Vault-backed secret scopes, you need to ensure that the Databricks workspace has permission to list and read secrets from the Key Vault.

    Double-check that the secrets with the keys clientid, clientsecret, and tenantid exist in the kvmigrn scope. Typos and casing can sometimes be a cause of these types of issues.

    Check this link to have an idea :

    Also try this and tell us the result :

    Navigate to your Azure Key Vault in the Azure Portal. Check to see if the secret with the key clientid is indeed present in the vault.

    Each secret in AKV can have multiple versions. Ensure you're referencing the right version, or you're set to retrieve the latest version.

    Ensure that the secret hasn’t expired or hasn’t been disabled in the Key Vault.

0 additional answers

Sort by: Most helpful