You’re offline. This is a read only version of the page.
Announcements
22
Hi all,
We’re encountering an issue with Power Automate flows that utilize certificates or secrets stored in Azure Key Vault (AKV). Specifically, when we update a certificate or secret in AKV, the changes are not reflected in the flow. The flow continues to use the previous version of the secret or certificate, even though the Key Vault has been updated.
The only workaround we’ve found so far is to create a new Azure Key Vault connector and use that in place of the existing one within the flow. While this works, it’s not ideal or sustainable.
I’m reaching out to ask:
Has anyone else experienced this issue?
Are there any alternative workarounds you’re using?
Are there any best practices for integrating AKV with Power Automate to ensure secrets stay current?
We have raised multiple support tickets with Microsoft, and the issue was acknowledged as a known bug, and few other customers are having similar issue. However, we haven’t received any further updates or timelines for a fix.
Any guidance or shared experiences would be greatly appreciated. Thanks in advance!
Share
Report
All responses (
Answers (
