"Azure Container Does Not Exist" when cloning repositories in Azure Databricks

[ptco]

Good Morning, I need some help with the following issue:

I created a new Azure Databricks resource using the vnet-injection procedure. (here)

I then proceeded to link my Azure Devops account using a personal account token. 

If I try to clone a repository I get an error message saying:

The Azure container does not exist

From other occurrences of the same error message in the community I seem to understand that this is something associated with the Unity Catalog, however even when I remove the workspace from the Unity Catalog I get the same error.

Many Thanks

[Kaniz_Fatma]

Hi @ptco, 

• Let’s check a few things:
  • Ensure that your Azure DevOps account token is correctly configured in your Databricks workspace.
  • Verify that the repository you’re trying to clone exists and is accessible.
  • Double-check the Unity Catalog settings to ensure there are no lingering references causing the issue.

[ptco]

Hi @Kaniz_Fatma many thanks for your reply.

I have verified that repository works in another (older) databricks workspace. When I try to clone into a new databricks instance, it creates subfolders but won't copy the files. I have attached a screencap of the error message for your convenience.

How do I check the Unity Catalog settings for lingering references? The account admin removed this workspace from the Unity Catalog, is there anywhere else where we should be looking at?