Azure Logic Apps — secure input and output

When you build your Logic Apps solution. There is often a situation where you deal with sensitive data. Which isn’t supposed to be shared and visible anywhere. Of course, you can put mentioned secrets inside a Key Vault service and then reference them from a Logic Apps workflow.

Here is an example:

We take two pieces of information: a database name and a container name. So far so good, data is inside a key vault, we reference it. Everything seems to be in place and secure.

Now, we can go to a Run history section and open a run.

When you go into the run details and select any step then you can look at inputs and outputs. As you see at the image below it looks like our secrets aren’t as secure as we expected.

In this place, the secure inputs/outputs come to the rescue. Switch back to the designer and go into step settings.

Here, you are able to pick if you want to secure inputs or/and outputs.

When you run the workflow with new settings applied and check the run history then you aren’t able to see any secret.