
I don’t believe there is currently a tenant-level setting that enforces the authentication mode for HTTP/webhook triggers in Power Automate.
Right now, the maker chooses the authentication option for each flow trigger individually (“Anyone”, “Any user in my tenant”, or “Specific users in my tenant”). DLP policies can control if the connector is allowed, but not which authentication option is selected.
One possible workaround is to run a recurring PowerShell script that checks flows across environments and identifies flows using anonymous access (“Anyone”). The results could then be reviewed by the platform or security team.
This would not block the configuration, but it would help monitor and clean up insecure webhook endpoints.
Hope it helps!