The HTTP POST URL of the ‘When an HTTP request is received’ trigger in Power Automate Flows is a public endpoint, so you need to secure it.
There are several options to secure the receiving Flow for Actionable Messages requests:
- Enable Schema validation in the settings of the trigger
- Add Trigger conditions based on Headers keys
- Compare correlationId from Headers with the original one
The…
Continue Reading StefanS365’s Article on their blog
Secure the receiving Flow for Actionable Messages requests – There’s Something About Dynamics 365
Posted by The HTTP POST URL of the ‘When an HTTP request is received’ trigger in Power Automate Flows is a public endpoint, so you need to secure it.There are several options to secure the receiving Flow for Actionable Messages requests: Enable Schema validation in the settings of the trigger Add Trigger conditions based on Headers keys Compare correlationId from Headers with the original one The first option is easy to set and will validate the request body against the schema provided.
Blog Syndicated with StefanS365’s Permission
More About This Author
Array
Dyn365CE2 February 2024Validate file input of manually triggered flow with trigger conditions
Dyn365CE25 October 2023Bulk Delete assets in Microsoft Purview via the user interface
Dyn365CE24 October 2023Bulk Delete assets in Microsoft Purview with Power Automate flow
Dyn365CE26 March 2023Populate a dynamic Microsoft Word template in Power Automate flow
