Power BI Dataflow Using AKV

[chito]

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. 

[chito]

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.

[chito]

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.  

[chito]

I mean is NOT resolved

[v-aatheeque]

Hi @chito 

Thanks for the update and for clarifying that the issue, even though the suggested workaround (recreating dataflows from scratch) is extremely inconvenient and not practical at scale.

Given the impact you mentioned (dozens of dataflows with complex schemas) and the fact that export/import is failing, this looks like a product limitation or bug rather than an expected workflow.

Have you already raised a Microsoft support ticket for this issue?

[chito]

Yes, we have an outstanding severity 1 ticket for over 2 weeks now.  As I mentioned MS suggestion is to recreate the dataflow from scratch, which we did before the suggeston came in, as we don't have any other option.  No actual resolution to the root cause of the problem.

[v-aatheeque]

Hi @chito 

Thanks for the update and for sharing the details.

Since you already have an active Severity 1 Microsoft support ticket open, the best next step is to continue working with the support team, as this appears to be a service issue or product limitation that requires backend investigation.

Unfortunately from the community side, we don’t have additional visibility or tools to diagnose the root cause further. Please keep engaging with Microsoft Support for RCA and any permanent fix or guidance they can provide.

If you receive any updates or a resolution from the support team, sharing them here would be helpful for others who might face a similar issue in the future.

[chito]

I will certainly share my experience and any resolution Microsoft provides once available.

In the meantime, I strongly suggest that community members who are using Power BI Key Vault references in their setup review their configurations as soon as practical and consider alternative approaches if possible.

The current workaround is cumbersome, fragile, and not realistically scalable, especially for environments with hundreds of complex dataflows. Implementing and maintaining this workaround at scale is extremely time-consuming and operationally risky.

Hopefully, Microsoft can provide a proper fix soon, as this issue has significant impact on production workloads.

[v-aatheeque]

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?

[tharunkumarRTK]

@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!