I want to secure my flows by restrict IP address, tenant, group, users for HTTP - Request trigger.
1. Restrict in my company ipaddress to use my flows which trigger by HTTP - Request.
2. Restrict in my users of our Office 365 group to use my flows which the trigger by HTTP - Request and use from SharePoint - Flow menu.
Current, Anyone who know HTTP POST URL of the trigger, can use our Flows.
At SharePoint, When create Flow by template 'Complete a custom action for the selected item', the new flow by trigger HTTP - Request, and can use anyone who know HTTP POST URL.
Thank you for the idea, we will evaulate this.
Thank you for your vote to this idea - Security - restrict HTTP - Request trigger by IP address, tenant, group, users .
Please comments your think, and your scenarios.
We also have a similar requirement in which we want to enforce security on the HTTP POST URL to restrict access to this url.
Any ideas would be appreciated.
@Stephen Are there any updates here? It is very difficult to build flows, especially those realted to personal data, without the option of restricting who can make calls to our HTTP endpoints.
Adding this feature would massivly increase the types of flows we can create. Today we are restricted due to this security vunerability.
The Security is a mandatory requirement to use the personal data.
Has there been any update on this item? as security is the key to start using this action actively
Almost a year under review?! What's going on here?
@Stephen: When will this continue? Are there any news here?
We really need to have a secure solution for using HTTP requests within Flow...