Hi Lou,

Thank you so much for your detailed reply, and I apologize for leaving this open for so long.  I got wrapped up in another project and am just getting back to this.

I was able to resolve it, at least in my situation, last night, so I wanted to add what I found to this thread in case it helps someone else.

It used to be the case that you had to create the Access Connector for Databricks manually, then give it Storage Blob Data Contributor in the Storage Account (Azure).  Now, when you create a Databricks Workspace, it automatically creates the Access Connector (I have a related gripe with the way it names them - if you have multiple workspaces, theres no easy way to tell which is for which without hovering over it to see the full description).  We assumed this could be used and was attached to the Databricks workspace.  We made sure that this auto-generate Access Connector had Storage Blob Data Contributor to the new Storage Account.  

When I tried to create the table with a defined EXTERNAL LOCATION, I got an error message that said "The credential <credential_name> is a workspace default credential that is only allowed to access data in the following paths <default_path>."

This made me realize that the Access Connectors that Databricks is creating are not allowed to be used on other Storage Accounts.  This is pretty odd to me, but it seems to be the case.

When I created a new Access Connector, tied to this same Databricks Workspace, then gave it Storage Blob Data Contributor, everything works as expected.

Thanks!
Seth Parker