The bad thing about sensitive variables is , you can still use display message and see the values, does it not against the usage of azure key vault.
@chaitanyasravanthi5822
2 жыл бұрын
One query: Is there anyway to avoid hardcoding the client id and secret of Azure Key Vault directly on the action?
@KentWeare
2 жыл бұрын
I assume you are talking about this part: kzitem.info/news/bejne/yKadyXxmoap6dJg This is required when establishing your connection. There is no way you can dynamically inject values into creating a connection at runtime.
@calvindale
2 жыл бұрын
Is there an effective way to debug a Desktop flow that is dependent upon secrets provided by a Cloud flow? Whereas it is possible to stop at a breakpoint in the Desktop flow when the flow is invoked from within a Power Automate Desktop development session, it doesn’t seem possible to stop at a breakpoint in the Desktop flow when the flow is invoked by a Cloud flow. One could provide the required secret(s) manually to the Desktop flow during development. But that is cumbersome and not ideal. So, I am curious if there might be a better approach.
@KentWeare
2 жыл бұрын
There is no way to 'live-debug' a desktop flow that was initiated by a cloud flow. Probably best you can do is set your secrets as default value and run locally. After you are done with your tests, remove secret. Either that or from your Desktop flow, add a subflow at the top of your script that calls keyvault directly using HTTP and retrieves secrets.
@calvindale
3 жыл бұрын
When I click on the "Connect with service principal" link, the dialog appears and about a second later disappears reverting back to the previous dialog. The Get secret action is flagged as a Premium feature. However, as I have the "Power Automate per user with attended RPA plan" license, I suspect that should be adequate (i.e., premium). Hence, it's unclear why the dialog is auto-dismissing itself.
@KentWeare
3 жыл бұрын
Hi Calvin - I have seen this before. Your license will be sufficient. What I would try to do is create the connection from outside the flow editor. In the left navigation pane, expand the "Data" tab and then click on Connections. Try to create the connection from there and then select it in your flow. Otherwise you can also try to do the previous steps in an "Incognito" or "Private Mode" browser
@calvindale
3 жыл бұрын
@@KentWeare Thanks Kent. It's good to know that it's not a licensing issue. Subsequent to your commenting here, I haven't had yet a chance to to try the technique you suggest. However, I am pretty sure that I did try it at the time I posted the question and unfortunately it wasn't working for me then. When I come up for air, I'll give it another shot.
@arcelperdomo7542
3 жыл бұрын
Hi Kent. Does it require an specific license ?
@KentWeare
3 жыл бұрын
You will need to have access to Azure Key Vault which does cost although it is quite nominal the fees.
@arcelperdomo7542
3 жыл бұрын
@@KentWeare Thanks!
@sempaxbolong6259
3 жыл бұрын
and now they add new action (cyberark) inside power automate desktop instead azure key vault. smh
@KentWeare
3 жыл бұрын
In part this is related to WinAutomation - Power Automate Desktop symmetry. WinAutomation previously had Cyberark so some of those customers were looking for this support. Cyberark is quite popular in the enterprise as well.
Пікірлер: 13