Sometimes the things holding you back aren't things you realize can hold you back. In my case, the issue was that we are using private endpoints on our applications and services, and the queue private endpoint of storageAccountA was not exposed. Something I didn't understand in the documentation was that the AzureWebJobsStorage account uses a queue for any/all storage accounts the function app is connecting to, so even though I am monitoring storageAccountB, the issue was that the app could not create a queue in storageAccountA to manage the invocations of monitoring storageAccountB. The issue was that storageAccountA was unable to generate a queue to manage blob trigger log monitors to other storage accounts (i.e. storageAccountB) because there was no storage account private endpoint exposed in storageAccountA.