Problem

You are trying to create a managed table in a location outside the default metastore (root storage) in your workspace when you get an error that says the resource does not exist.

[RequestId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ErrorClass=RESOURCE_DOES_NOT_EXIST] Status code: -1 error code: null error message: Cannot resolve hostname: xxxxxx.dfs.core.windows.net

This is not specific to any particular configuration or setting but rather an unexpected error related to the storage account.

Cause

An incorrect storage account is being used as the root storage for your metastore. The storage account xxxxx.dfs.core.windows.net is not recognized and does not exist in your cloud environment. This causes an error when you try to create managed tables, as they are stored in a different location that you previously specified.

The storage root bucket is not shown in the Catalog Explorer and the external location added in the metastore is not the root storage for this metastore.

Solution

Change the default root storage for your metastore to a valid storage account.

Use the update a metastore API to update the metastore.

To prevent similar issues in the future, ensure that the root storage account for your metastore is valid and accessible. 

Use the get a metastore summary API to review the current metastore details.

Additionally, you should consider explicitly changing the storage root location for catalogs and schemas to a desired location, either at the catalog level or at the schema level.