How to deploy SQL databases within an elastic pool to different resource groups?

Question

The title pretty much says it all. There seems to be no way to deploy individual databases into their own resource groups. But rather they are - by necessity - deployed into the same group along with the pool. Is this understanding correct and if so, why? After all, they are modelled, at least visually within Azure Portal as a top-level resource.

Answer 1

I don't think this is supported. Even with Azure SQL single databases you have to move the SQL server parent resource along with the database, it is not possible to move databases without also moving the server resource.

They do exist as individual resources and you can apply resource level permissions etc but there is a parent-child relationship between the server and database resources that means they must exist in the same resource group.