[BUG]: wasbs:// and dbfs:// mount external tables are not listing in principal-prefix-access command

[heydil]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Currently, external tables mounted using the wasbs:// and dbfs:// are not being listed when using the principal-prefix-access command, azure_storage_account_info.csv file is not getting generated.

Expected Behavior

External tables mounted using the wasbs:// and dbfs:// protocol should be listed when using the principal-prefix-access command and successful creation of azure_storage_account_info.csv file.

Steps To Reproduce

1. I have external table , mount point and external locations listed in the inventory database after the assessment run.
   
   

2. When running the principal-prefix-access command, receive the below warning message:
   

Cloud

Azure

Operating System

Windows

Version

latest via Databricks CLI

Relevant log output

WARN [d.l.u.assessment.crawlers] There are no external table present with azure storage account. Please check if assessment job is run

[HariGS-DB]

principal-prefix-access cmd creates a list of storage account used by tables along with its permission. This list is then used to create storage credentials. for table referring to wasb:// and adl:// , we shouldn't be creating its service principal as credential. The ideal solution would be to migrate the data from wasb:// ad adl:// to abfss storage and use its storage credential and location.
refer #1065 for more details.
we should update the documentation to make this clear