The Problem

I recently was debugging an Execute PowerShell Code Logic App action, so wanted to see it’s output. However, when I reviewed the run history, the output for my code action was empty.

The Cause (and Solution)

The problem turned out to be that the Logic App’s Inbound traffic configuration. You can replicate this issue easily

1. Create a new Logic App Workflow, use any trigger and then add an Execute PowerShell Code action, you don’t need to edit the default code sample.
2. Save the new Action and then run it.
3. Review the run history and you’ll see that the output as expected.
4. Next, change the Logic App’s ‘Inbound traffic configuration > Public Network Access’ to ‘Disabled’ and run the Logic App again, and the output now cannot be seen, as shown above.

You are actually warned about this in the Azure Portal the first time you view a run history the settings that block it

But it is easy to miss, or as I did, just forget about the limitation.

For the original version of this post see Richard Fennell's personal blog at Why cannot I see my Logic App action output?