* Update 2022-11-16: Updating scripts / procedures to use MSI, instead of Automation Run As Account
https://learn.microsoft.com/en-us/azure/automation/manage-run-as-account
Azure Automation Run A...
JordanJohnson Thanks. I'm not sure if that will work in my scenario. I have a dedicated SQL pool in addition to the default built in (serverless) sql pool.
1. The BuiltinSqlPoolLoginAttempts metric appears to point to that built in pool. and the other pool is what i need auto-pause and auto-resume for.
2. The metric counts successful login attempts as well. On the console, it comes off as simply "Login Attempts" with the description "count of login attempts that succeeded or failed".
I know the old mode (sql dw) can resume on failed connection based on https://github.com/microsoft/sql-data-warehouse-samples/blob/3a3ab5e3320b5d9d36120c1aa642ebe38d548c8c/arm-templates/sqlDwLogicAppAutoPause/EventbasedAutoPauseResumeDW.json#L464 configuration, but it is probably not doable anymore in the new mode. Instead, I am evaluating an alternative (add webhook to runbooks and fire a REST request from web activity within Synapse pipeline)