Announcements
At the moment, Power Platform doesn’t provide a built-in way to stop makers from selecting “Anyone” in the When an HTTP request is received trigger.
What most organizations do instead is put governance controls around it. For example:
* Use DLP policies to restrict where HTTP connectors can be used
* Limit who is allowed to create flows with premium/custom connectors
* Use the CoE toolkit or admin reporting to monitor flows using HTTP trigger
For monitoring, you can scan flows through the Power Platform Admin connectors or CoE data and identify flows where the trigger authentication is set to “Anyone”. From there, you can create alerts or governance reports for review.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Vish WR 1,027
Valantis 815
Haque 630