Hi Anyone tried using the new Azure Key Vault references feature? I think it was part of the Q1 2025 feature drop but looks only partially implemented to me. We now have a new tab under "Manage Connections and Gateways" called "Azure Key Vault references". Under there we can successfully create entrries to reference Azure Key Vault resources created within our tenant. How do we reference them? There appears to be no documentation on this that I can find. If we have a Cloud Connection to Azure Blob Storage - Happy Days. A neat little Key Vault icon next to the authentication credentials field.... just click on that and enter your key vault reference. Any other connections? I can't see any way of connecting. No nice little icons, and no way of entering teh key vault reference for a connection. Can anyone advise how this new feature is supposewd to be used?

Hi onerbreno If your Fabric notebook isn't fetching secrets with mssparkutils.credentials.getSecret(), here are a few troubleshooting stesps to look out for: Make sure your Fabric workspace's managed identity has both the Key Vault Reader and Key Vault Secrets User roles assigned in Azure Key Vault's "Access Control (IAM)". Verify the Key Vault name and secret name in your code — they are case-sensitive. Even minor typos can cause silent failures. Check that the secret is active — not disabled or expired. If your Key Vault uses private endpoints or has public access fully disabled, Fabric won’t be able to reach it. Fabric currently doesn’t support connecting to Key Vaults through private endpoints. This code will only work inside a Fabric notebook — it won’t function in an external IDE or local script. To confirm which identity your notebook is using to call the Key Vault, run: from notebookutils import mssparkutils print(mssparkutils.credentials.getIdentityName()Let me know if you need help checking any of these or interpreting what you find! Note:For refrence check the below link for supported connectors and authentication types.Azure Key Vault Reference overview (Preview) - Microsoft Fabric | Microsoft LearnFYI If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.Best Regards,Community Support Team _ C Srikanth.

Azure Key Vault References | Microsoft Fabric Community

19 Replies

burakkaragoz
Super User
1 year ago
Hi willparker1 ,
You’ve raised a spot-on summary of the current Azure Key Vault References feature in Microsoft Fabric. As of now, the implementation is indeed quite limited and mainly targets specific scenarios:
The native Key Vault reference integration only works seamlessly with Azure Blob Storage connections. In these cases, a Key Vault icon appears next to the authentication field, letting you select and inject a secret directly from your Azure Key Vault.
For other types of connections, the feature isn’t fully available yet. There’s no dynamic content option or Key Vault reference picker in the connection setup dialogs, which means the experience is inconsistent.
The recommended (and currently only) way to access Azure Key Vault secrets from within Fabric is using msaparkutils in Fabric notebooks, not standalone Python scripts. Example:

from notebookutils import mssparkutils secret = mssparkutils.credentials.getSecret("YourKeyVaultName", "YourSecretName")
Your Fabric workspace identity must have the "Key Vault Secrets User" role for this to work. This approach is not supported in non-notebook scripts.
For Power BI, ArcGIS, or other scenarios, the usual workflow is to preprocess or inject secrets via notebooks, then consume the output with the relevant tool.
Community feedback (including yours) is very valuable here—Microsoft often expands these features in response to real-world use cases. If you haven’t already, consider submitting your experience and requirements via the official Fabric Ideas portal.
If you need workarounds for other connection types, or want to discuss secure secret management strategies, happy to brainstorm further! You’re definitely not alone in wanting a more universal and documented solution.
Let me know if you have any follow-up questions or want more concrete examples.
- onerbreno
  Frequent Visitor
  1 year ago
  Hi burakkaragoz!
  
  I tried using this method with mssparkutils, but I couldn’t access the secret. Could you explain it a bit more or help me understand what might be missing? I’m using a notebook in Fabric and have already assigned the "Key Vault Secrets User" role to the workspace, but it still didn’t work.
  - burakkaragoz
    Super User
    1 year ago
    onerbreno ,
    Thanks for sharing your experience—this is a common stumbling block! Let’s go through a checklist and some troubleshooting steps to get mssparkutils working with Azure Key Vault in Fabric notebooks:
    Role Assignment Propagation:
    After assigning the “Key Vault Secrets User” role, it can take several minutes (sometimes up to an hour) for the permission to propagate across Azure AD and Fabric. If you assigned the role very recently, try waiting a bit and then re-running your notebook.
    Scope of Role Assignment:
    Double-check that the role is assigned to the correct security principal (e.g., the workspace-managed identity, not your personal account), and that it’s assigned at the right scope (i.e., to the Key Vault resource, not just at a resource group or subscription level).
    Key Vault Firewall/Networking:
    Ensure your Key Vault’s firewall/networking settings allow access from Fabric. If “Public access from selected networks” is enabled, make sure the Fabric service’s IP or VNet is permitted.
    Secret Name and Case Sensitivity:
    Secret names in Azure Key Vault are case-sensitive. Make sure the secret name in your code exactly matches what’s in the Key Vault, with no extra spaces.
    Notebook Identity:
    In Fabric, notebooks usually run under the workspace’s managed identity. Make sure this identity is the one with “Key Vault Secrets User” on the vault.
    Sample Working Code:
    Here’s a typical working snippet (replace placeholders with your actual values):
    Python
    
    import mssparkutils secret = mssparkutils.credentials.getSecret("YourKeyVaultName", "YourSecretName") print(secret)
    If this throws an error, please share the exact error message—sometimes the error text gives a clue (e.g., “Forbidden”, “NotFound”, or “Network” errors).
    Testing from Azure Portal:
    As a sanity check, try accessing the secret using the “Test access” feature in the Azure Key Vault portal, logged in as the same identity as your notebook uses.
    If after all this you’re still getting blocked, could you paste the exact error message you receive? That’ll help narrow down whether it’s a permissions, network, or configuration issue.
    Let me know how it goes—I’m happy to help you troubleshoot further!
    If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
v-csrikanth
Community Support
1 year ago
Hi willparker1
Please check the below points that might resolve your issue:

Azure Key Vault references currently work directly only with Blob Storage connections in Fabric; other connectors like Power BI or ArcGIS don’t support this yet.

In the “Manage Connections and Gateways” section, you can define a Key Vault reference, but only compatible connectors will expose it during credential entry.

For other use cases, use Fabric notebooks to securely fetch secrets with this code:

from notebookutils import mssparkutils

secret = mssparkutils.credentials.getSecret("YourKeyVaultName", "YourSecretName")

Ensure the Fabric workspace managed identity has the "Key Vault Secrets User" role assigned to the Key Vault.

After fetching the secret in the notebook, you can use it to connect to APIs, databases, or secured storage, and then store the processed data in a Lakehouse or Warehouse.

Connect Power BI, ArcGIS, or other services to that processed data rather than trying to inject secrets directly into unsupported connectors.

This method maintains security while enabling integration across Fabric workloads.

Azure Key Vault support in Fabric is still evolving—wider connector support is expected in future updates, so keep an eye on the roadmap.

Best Regards,
Cheri Srikanth
- onerbreno
  Frequent Visitor
  1 year ago
  Hi, v-csrikanth!
  
  I tested these steps but wasn’t successful. Could you help me understand what might be missing?
  
  For other use cases, use Fabric notebooks to securely fetch secrets with this code:
  from notebookutils import mssparkutils
  secret = mssparkutils.credentials.getSecret("YourKeyVaultName", "YourSecretName")
  Ensure the Fabric workspace managed identity has the "Key Vault Secrets User" role assigned to the Key Vault.
DianaGeyer
Frequent Visitor
1 year ago
Hi willparker1,

I haven't tested it yet myself, but I would assume it's meant to work similarly to how Azure Key Vault references are used in other Azure resources. The expected format seems to follow the same structure as in, for example, App Services or Logic Apps.
You can try referencing your secret using one of the following formats:
@Microsoft.KeyVault(SecretUri=https://myvault.vault.azure.net/secrets/mysecret)
Or alternatively:
@Microsoft.KeyVault(VaultName=myvault;SecretName=mysecret)
If that works for you, feel free to mark this as the solution so others can benefit as well!
- willparker1
  New Member
  1 year ago
  Hi Diana
  
  Thanks so much for responding.
  
  Unfortunately there is no option to use dynamic content in the connection set up field.
  
  There is actually one type of connection that allows you to reference the key vault - a Blob Storage connection. In that dialog, you are given a side icon allows you to select a property from an Azure Key Vault then it replaces it with the value, (see below). However this elegant solution is unavailable on any other connection type I can find, (and no other option I can see is available to reference the Azure Key References, making them kinda useless...
  
  Thanks
  Will
dcsearle
Frequent Visitor
1 year ago
2nd the fact there is no documentation, also noticed that at the same time this feature was released all of a sudden Conditional Access policies started blocking us using our pre-existing Web2 connections to our AKV... effectively downing any pipelines which were using it.
Really poor behaviour in terms of releasing features like this - expect much more in terms of release notes and how to use.
v-csrikanth
Community Support
1 year ago
Hi willparker1
The current partial implementation and limitations, the best approach to use Azure Key Vault references in Microsoft Fabric is:

For integrating Azure Key Vault with Microsoft Fabric is to use mssparkutils in Fabric notebooks with a service account for authentication.

Use Azure Key Vault references primarily with Azure Blob Storage connections, where native UI support exists to select and inject secrets securely.

For ArcGIS and Power BI scenarios, use Fabric notebooks to preprocess data with Key Vault secrets, then connect Power BI to the processed data, ensuring the latest Power BI Desktop version for compatibility.

If the above information helps you, please give us a Kudos and marked the Accept as a solution.
Best Regards,
Community Support Team _ C Srikanth.
- Anonymous
  Not applicable
  1 year ago
  Hi Support
  
  Thanks for the response.
  
  One follow on query - you mentioned mssparkutils. I understood this was demised for Fabric in favour of notebookutils? Certainly mssaprkutils unavailable for Python scripts.
  
  Appreciate any advice.
  
  Kind Regards
  Will
v-csrikanth
Community Support
1 year ago
Hi willparker1
You're right, mssparkutils is deprecated in Microsoft Fabric. The supported way to access Azure Key Vault secrets in Fabric is by using mssparkutils inside Fabric notebooks only:

from notebookutils import mssparkutils

secret = mssparkutils.credentials.getSecret("YourKeyVaultName", "YourSecretName")

This works only inside Fabric notebooks, not in standalone Python scripts. Make sure your Fabric workspace identity has access to the Key Vault with the "Key Vault Secrets User" role. No need to store usernames or passwords manually. For external Python scripts, use Azure SDK instead.

If the above information helps you, please give us a Kudos and marked the Accept as a solution.
Best Regards,
Community Support Team _ C Srikanth.
v-csrikanth
Community Support
1 year ago
Hi willparker1
We haven't heard from you since last response and just wanted to check whether the solution provided has worked for you. If yes, please Accept as Solution to help others benefit in the community.
Thank you.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.
v-csrikanth
Community Support
1 year ago
Hi willparker1

I wanted to follow up since I haven't heard from you in a while. Have you had a chance to try the suggested solutions?
If your issue is resolved, please consider marking the post as solved. However, if you're still facing challenges, feel free to share the details, and we'll be happy to assist you further.
Looking forward to your response!

Best Regards,
Community Support Team _ C Srikanth.
v-csrikanth
Community Support
1 year ago
Hi willparker1
Following up on our last response. Was it useful? If you need more details, we’re glad to help.
If it worked for you, consider clicking Accept as Solution and adding a Kudos.

Best Regards,
Community Support Team _ C Srikanth.
v-csrikanth
Community Support
1 year ago
Hi onerbreno

If your Fabric notebook isn't fetching secrets with mssparkutils.credentials.getSecret(), here are a few troubleshooting stesps to look out for:

Make sure your Fabric workspace's managed identity has both the Key Vault Reader and Key Vault Secrets User roles assigned in Azure Key Vault's "Access Control (IAM)".

Verify the Key Vault name and secret name in your code — they are case-sensitive. Even minor typos can cause silent failures.

Check that the secret is active — not disabled or expired.

If your Key Vault uses private endpoints or has public access fully disabled, Fabric won’t be able to reach it. Fabric currently doesn’t support connecting to Key Vaults through private endpoints.

This code will only work inside a Fabric notebook — it won’t function in an external IDE or local script.

To confirm which identity your notebook is using to call the Key Vault, run:
from notebookutils import mssparkutils
print(mssparkutils.credentials.getIdentityName()
Let me know if you need help checking any of these or interpreting what you find!

Note:For refrence check the below link for supported connectors and authentication types.
Azure Key Vault Reference overview (Preview) - Microsoft Fabric | Microsoft Learn

FYI

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

Forum Discussion

Azure Key Vault References

19 Replies

Related content

API secrets without Azure Key Vault

Azure Key Vault Reference behind firewall

Key Vault Reference Configuration

Azure Key Vault Connection

Key Vault Reference - Invalid Credentials