Use OAuth support for HTTP request triggers
Important
This content is archived and is not being updated. For the latest documentation, go to Microsoft Power Automate documentation. For the latest release plans, go to Dynamics 365, Power Platform, and Cloud for Industry release plans.
| Enabled for | Public preview | Early access | General availability |
|---|---|---|---|
| Admins, makers, marketers, or analysts, automatically | - | - | 
Oct 8, 2023 |
Business value
Makers can use enhanced security measures for HTTP request triggers. For example, makers can restrict what users can trigger in this workflow by ensuring that only authenticated users can trigger this workflow. They can further define the security scope by choosing among three modes for the authentication parameter.
Feature details
Prior to this feature, when makers created a flow that had an HTTP request trigger, the flow generated a shared access signature (SAS) URL. This URL was typically used by developers to trigger workflows from within their own applications or services. This feature provides added security to this trigger by enabling developers to limit who can trigger this workflow.