Hello @szymon_dybczak ,

Looking at the driver logs, it appears to be an issue connecting to consolidated-eastusc3-prod-metastore-0.mysql.database.azure.com.

In researching this endpoint, I found the following document outlining access points for Azure Databricks with that being the endpoint for the Metastore. IP addresses and domains for Azure Databricks services and assets - Azure Databricks | Microsoft Lea...
I understand that to resolve the issue, I need to open access to that endpoint, but I first have a question of why it needs to connect to a MySQL endpoint and what is stored there?  We implemented VNET injection because we want to keep our instance private, but if data is being stored outside of our tenant, that is a potential risk.