Cannot find the credential "https/datalake/file.parquet" because it does not exist or you do not have permission

Silvano P 101 Reputation points
2021-05-26T22:35:40.54+00:00

Hello,

I'm using Synapse Serverless Pool and created a view with a query that access a parquet file stored in our data lake.

I'm the owner and I can run the view without issues using the On SQL on demand endpoint.

I would like now to create a user that can access the the SQL Endpoint and access the view?

Create a Sql Login gave reader permission, but maybe this is not enough since it cannot access the Azure Data Lake Storage.

Any idea?

Thanks

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,357 questions
{count} vote

3 answers

Sort by: Most helpful
  1. Samara Soucy - MSFT 5,051 Reputation points
    2021-05-27T15:54:46.82+00:00

    The most common reason for this error is the user does not have the Storage Blob Data Contributor on the Storage account. This is required even if you have owner permissions on the account.

    Please let me know if this solves the issue or if we need to go through some more troubleshooting.

    0 comments No comments

  2. Axel B Andersen 106 Reputation points
    2022-01-23T08:05:32.35+00:00

    I have the exact same issue. I have added my MSI to the Storage Blob Data Contributor on the storage account and to the db_datareader role on the SQL endpoint resulting in: ERROR: Cannot find the CREDENTIAL 'msi_cred', because it does not exist or you do not have permission.Msg 15151

    If I add the MSI to the db_owner role on the SQL endpoint it works - even if I remove Storage Blob Data Contributor access on the storage account.

    0 comments No comments

  3. Ricardo Neves 1 Reputation point
    2022-06-24T18:40:19.02+00:00

    I'm having the same issue when i try to connect to a datasource in power bi, "Erro do OLE DB ou do ODBC : [DataSource.Error] Microsoft SQL: Cannot find the CREDENTIAL". Did anyone fix this ?

    0 comments No comments