Today, I noticed a new security feature in Power Automate. It is now possible to secure your data in flows. When you secure your input and output in flows you will not be able to see data in your actions as you hide information in your flow runs.
What does that look like?
When you secure your data you will now see in your Flow runs.
Content not shown due to security configuration
The security settings can be configured at the action/step level using the settings option for each of the actions in your flow.
You can both secure the input and the output.
Note that you may see
The secureData configuration of workflow action ' ' of type ' ' ... There values are not supported in properties
You will find that in some actions it is not possible to secure the input and or output or both.
In my example I reduced the security settings just to the input
This now added a lock to my action in edit mode so that I can easily recognise the locked actions.
Also in the Dynamic content you can recognise the locked data
In the above example the input sand the output of the Compose contains the same data hence the problem locking both at the same time.
When we take a SharePoint action to get items from my SharePoint site, I can lock the output only as shown below:
When using the Preview feature be careful as it makes it extremely hard to debug any mistakes. However if you have any data that needs securing then you might want to implement this features once your process is all working.
This post is all about error handling and parallel branches. General error handling in Power…
Recently the Get changes for an item or file action was added to SharePoint. Here…
When you create private channels in Microsoft Teams there are some limitations that you need…
When you add dynamic content to actions you will get those unwanted apply to each…
Yesterday Jon Levesque asked me if I had any posts helping to compare two SharePoint…