- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2026 12:56 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2026 04:29 PM
Hi All, Found the issue
It was related to path being called in url instead of using
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2026 06:10 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2026 07:45 AM
Hi Joel ,
I had created with hierarchical namespace enabled only , issue was with url used which is now resolved but thanks for your input
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2026 07:58 AM
I have the following YouTube video that can guide you on how to properly create external locations: https://www.youtube.com/watch?v=cAXLFgcVMn0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2026 07:38 AM - edited 02-12-2026 07:40 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2026 07:46 AM
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