Forum Discussion

Eddykleinjan's avatar
Eddykleinjan
Frequent Visitor
1 year ago
Solved

Secure Key Vault access without Workspace Identity

Hi, I'm ready to dive into the first real Fabric project getting data from a specific app's API. This requires using secrets to access the soure data app's API. I don't want to store these secrets i...
data engineering
notebook
Eddykleinjan's avatar
Eddykleinjan
Frequent Visitor
1 year ago

That's good news! Should then work ask hoped for/expected. I'll give it a try.

  • Jaimini's avatar
    Jaimini
    Frequent Visitor
    1 year ago

    Hi Eddykleinjan 

    1. The F64+ requirement is no longer valid. You can now create up to 1,000 workspace identities.

    2. Important: Currently, authentication with workspace identities, specifically for Key Vault, is not available.

    3. Interestingly, if you have access to Key Vault with your domain account and run the notebook using the same account, you will be able to access the Key Vault secrets. You can use mssparkutils for this.

    4. Additionally, you can create a Spark job definition using the same code (as mentioned in point 3). If you schedule and run it, it will work, using your account for authentication.

    For now, managed/workspace identity authentication for Key Vault is not functioning.

     

    Anonymous 

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    Hi Eddykleinjan 

    I haven't tested whether the workspace identity can access the Azure Key Vault. Could you please share your results with us later? Thank you in advance.

     

    Best Regards,
    Jing

    • Eddykleinjan's avatar
      Eddykleinjan
      Frequent Visitor
      1 year ago

      Hi Jing,
      Will do! For now creating a workspace identity gives an error (status: Failed). Will start a support incident on this error occurs both under a Fabric Trial capacity and a real Fabric F2 capacity.
      Best regard, Eddy

      • Eddykleinjan's avatar
        Eddykleinjan
        Frequent Visitor
        1 year ago

        Hi Jing,

        Creating the workspace identity didn't work because the workspace name had special characters in the name, a space in my case. Microsoft had identified this as a problem and will fix this.

        Jaimini reported that accessing the Key Vault is not possible using the workspace identity, I chose to use the notebookutils way that frithjof_v adviced. That worked; see my reply to his message.