Azure Logic App - disable input output logging at a global level rather than at each action level

Question

Not sure if this has been asked before, but is there a way to disable the input output data logging in the actions at a global level?

This will prevent logging sensitive data to the Log Analytics if the input outputs are not secured at each action inadvertently.

Answer 1

Hi @Integration User Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

As @hossein jalilian mentioned, the current implementation does not support a global way of securing the inputs and outputs. If you secure an output of a trigger or action and use refer in any downstream actions, the value will be hidden automatically. However, the output generated from these actions need to be secured again as they are not by default.

Instead of having to edit each item from the designer, you can make the changes in a relatively simpler way by making changes through the Logic App code view. You can add or update the runtimeConfiguration.secureData.properties array at each action to secure the inputs and outputs in the code view as follows

"<trigger-or-action-name>": {
   "type": "<trigger-or-action-type>",
   "inputs": {
      <trigger-or-action-inputs>
   },
   "runtimeConfiguration": {
      "secureData": {
         "properties": [
            "inputs",
            "outputs"
         ]
      }
   },
   <other-attributes>
}

Please refer the document Secure inputs and outputs in code view for reference. Hope this helps!

---

If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.

Answer 2

Thanks for posting your question in the Microsoft Q&A forum.

Unfortunately, there is no global setting to disable input and output logging for all actions in an Azure Logic App workflow.

You can manually enable the Secure Inputs and Secure Outputs settings for individual actions that handle sensitive data. When enabled, these settings hide the input and output values in the run history

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful