Really good video with easy to follow instructions. I found you can't view access policies unless you toggle the Vault Access policy switch in the Access configuration settings . However, I think we are now encouraged move to the recommended role-based access control rather than the more granular access policy - so I toggled back to role based. Also, the Read role has now been replaced with the Key Vault Secrets User role. Finally, as you showed, the secret environment variable is still not available in the dynamic picker which I guess is intended .
Nice demonstration, first time I’ve seen the entire process laid out. How do we share usage of these secret environment variables when the flow is shared?
@Tomasz nice thnx for the vid!! What a anti climax that microsoft stil does not support this. If I want to apply the secret I have to add a separate dataverse unbound action to my flows and then I can retrieve secret and then I can apply secret. I expected that I could directly call envoirment varible. What a pitty this!!
Really good video with easy to follow instructions. I found you can't view access policies unless you toggle the Vault Access policy switch in the Access configuration settings . However, I think we are now encouraged move to the recommended role-based access control rather than the more granular access policy - so I toggled back to role based. Also, the Read role has now been replaced with the Key Vault Secrets User role. Finally, as you showed, the secret environment variable is still not available in the dynamic picker which I guess is intended .
You're correct in everything you wrote :)
Cool information and explanation, thank you very much!
Dziękuję bardzo 😊
You're welcome!
Nice demonstration, first time I’ve seen the entire process laid out. How do we share usage of these secret environment variables when the flow is shared?
Env. variables are a part of solution. There you are not sharing a flow, just granting permissions to let users use solutions.
@Tomasz nice thnx for the vid!!
What a anti climax that microsoft stil does not support this.
If I want to apply the secret I have to add a separate dataverse unbound action to my flows and then I can retrieve secret and then I can apply secret. I expected that I could directly call envoirment varible. What a pitty this!!
Yeah, it’s still this complex.
Did they fix the issue where you couldn't see the secret env variable in the list?
In which list? Of variables in cloud flow?
@@TomaszPoszytek at 10:17 where you can't find the secret key in the dynamic content dialogue. It looks to me like this is still not fixed?
@@snwtoy nope still not