Automatic pause all Synapse Pools and keeping your subscription costs under control

Hi FonsecaSergio ,

I was trying to configure automation such that a failed connection attempt to dedicated SQL pool will trigger a auto-resume script. It appears that the resource in old mode and new mode have some difference that impacts my ability to implement this.

The old mode (type Microsoft.Sql/servers/databases) has a https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/metrics-supported#microsoftsqlserversdatabases named "connection_failed", and it can be used to trigger an action to execute the runbook to resume the pool. The new mode (type Microsoft.Synapse/workspaces/sqlPools) however, is missing an equivalent https://docs.microsoft.com/en-us/azure/azure-monitor/essentials/metrics-supported#microsoftsynapseworkspacessqlpools. With this difference, I will not be able to automatically resume pool triggered by failed connect, with a straightforward configuration. 

Can you advise if there's a way to alert on failed connection attempt for the new resource type? I assume switching back to old mode is not an elegant option.