Not able to setup external location via Catalog

[nithin_1991]

Hi All,

I’m setting up an external location via Unity Catalog and I’m running into an issue when creating the location.

Context:

• ADLS Gen2 account with Hierarchical Namespace is enabled.
• A Databricks Access Connector has been created and assigned Contributor at both the subscription/resource and storage scopes.
• As a sanity check, I tested legacy access using storage access keys and was able to connect successfully.

Given that the legacy method works but the UC path fails, I suspect the problem may be with the Unity Catalog configuration (e.g., storage credential/external location permissions).  I'm new to databricks so any advice would be great.

Thanks in advance for your guidance.

[nithin_1991 · Accepted solution]

Hi All, Found the issue

It was related to path being called in url instead of using 

dfs.core.windows.net/ , I was using 

blob.core.windows.net/ which was throwing error

[joelramirezai · Accepted solution]

Hello @nithin_1991 
When you create a Databricks Azure Storage Account for Databricks, you always need to make sure that the hierarchical namespace is enabled.

Important considerations whren you create an external locations before you begin

[nithin_1991 · Accepted solution]

Hi Joel ,

I had created with hierarchical namespace enabled only , issue was with url used which is now resolved but thanks for your input

[joelramirezai]

I have the following YouTube video that can guide you on how to properly create external locations: https://www.youtube.com/watch?v=cAXLFgcVMn0

[saurabh18cs · Accepted solution]

Hi @nithin_1991 can you make sure it is storage blob data contributor granted to managed identity (dbac)

then create storage credential first for this dbac

then create external location using this credential

[nithin_1991]

Yes, I did that and also provide storage blob owner access but issue was with url provided while setting up external location which is resolved now