Forum Discussion

chito's avatar
chito
New Member
6 months ago

Power BI Dataflow Using AKV

We have our dataflow configured connections with Service Principal.  We are using private Key Vault (AKV) to get the secret of the SP.  The connections are using gateways to get to the private datasource.  This setup has been working for us for 2 months.  On 24th Jan 2026, all our dataflow connections started failing.  The error code is coming out as - DMTS_UserIsNotAllowedToAccessAzureKeyVaultConnectionErrorCode, which clearly showing error in AKV.  We therefore created another connection without the AKV so we can change the dataflows.  We got stuck, because now you cannot even edit the dataflows to change the datasource.  And you know what, MS is blaming the gateway, what a shock!!!  

 

Lesson here, DO NOT use Key vault reference in your PBI dataflows.  Only work around here is to recreate your dataflow from scratch. 

Dataflow
General Comment

10 Replies

  • tharunkumarRTK's avatar
    tharunkumarRTK
    Super User
    6 months ago

    chito 

    Thank you for sharing your experience.

     

    DMTS_UserIsNotAllowedToAccessAzureKeyVaultConnectionErrorCode

    This error message sounds like, the person who created this data source connection by retrieving the credentials from AKV lost access. Is it so? if yes, then have you tried granting the permissions again?

     

    Also, just out of curiosity what is the error that is stopping you from editing the existing dataflows to map them to the new datasource connections you created? Any error message that you can share would be helpful.

     

     

     

     

    Connect on LinkedIn

     

     

     








    Did I answer your question? Mark my post as a solution!
    If I helped you, click on the Thumbs Up to give Kudos.

    Proud to be a Super User!
  • chito's avatar
    chito
    New Member
    6 months ago

    Thanks tharunkumarRTK 

    The account that accessing the AKV have the Key Vault Secrets User RBAC assignment.  This is the first thing I checked.

     

    The error is the generic - Please try later and contact support.

    • v-aatheeque's avatar
      v-aatheeque
      Community Support
      6 months ago

      Hi chito 

      Thanks for the update. Since RBAC is already correctly configured and the error appears to be a generic service side message, could you please confirm whether the issue is now resolved on your end?

       

    • chito's avatar
      chito
      New Member
      6 months ago

      No.  The issue is NOT unresolved.  Micrsoft suggestion is to recreate our dataflows from scratch because exporting and reimporing the dataflow fails.  This is very bad and incovenient, as we have dozens of of dataflows that have dozens of tables with very specific columns.