Make Autopause feature compatible with Flow triggers
Power Automate Flows that begin with a SQL trigger ping the SQL database target every few minutes to see if the trigger condition has been met, which would then trigger the flow to execute. However, Azure SQL interprets these checks as a new logon attempt and so it never allows the database to pause.
Azure SQL should recognize the difference between a user logon, system scan, or other action that should legitimately resume the database, separate and distinct from a Power Automate Trigger that should not resume it. Otherwise, anyone who relies on the auto-pause feature cannot use Power Automate Flows with a SQL trigger. They are simply incompatible.