Hello,

my understanding is that some unspecified error happens in the managed resource group that DB creates when you deploy a new instance. Depending on your admin right you might not even be able to see such group in Azure (as in my case).

What has worked for me was to delete the instance and redeploy from scratch. I have deployed several new instances of DB in different resource groups since my original post and the problem has occasionally surfaced again, but deleting and redeploying has always done the trick.

Hope it helps!