search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.28k stars 21.47k forks source link

unable to retrieve secret from KV using RBAC #98233

Closed soferreira closed 5 months ago

soferreira commented 2 years ago

Documentation link: https://docs.microsoft.com/en-us/azure/synapse-analytics/spark/microsoft-spark-utilities?pivots=programming-language-python#configure-access-to-azure-key-vault

I am using RBAC and not Access policies.

I tested the connection to KV and it's working fine, see Image 1. However, I am unable to retrieve the secret from my KV with "Key Vault Secrets User" or "Key Vault Reader", see Image 2.

Shouldn't these roles give enough permission to the workspace to retrieve the secret from KV?

notebook code:

source_cs = mssparkutils.credentials.getSecretWithLS('medallion_kv_ls', 'medallion-acc-cs')

Image 1:

image

Image 2:

image

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

YashikaTyagii commented 2 years ago

@soferreira Thanks for your feedback! We will investigate and update as appropriate.

RamanathanChinnappan-MSFT commented 2 years ago

Hi @soferreira , We have investigated issue from our side. you can change the authentication method and try once. for your reference I have shared previous similar case below. please go through this. https://github.com/MicrosoftDocs/azure-docs/issues/93812

soferreira commented 2 years ago

Hi @RamanathanChinnappan-MSFT

I am using System Assigned Managed identity and I am running the notebook from pipeline. The pipeline works well if I use access policies. However, it does not work if I use RBAC.

Does that mean that RBAC not supported by the library at the moment?

RamanathanChinnappan-MSFT commented 2 years ago

Hi @soferreira,

Thanks for your feedback! We have assigned the issue to author and will provide further updates.

jbradwin commented 1 year ago

@ruixinxu Were you able to confirm this defect with the product team? I am experiencing this undesired behavior as well.

abdullah-p commented 1 year ago

@RamanathanChinnappan-MSFT @ruixinxu hi, do you have any updates on resolving this bug?

bandersmsft commented 5 months ago

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close