Thanks for pointing me in the right direction! That was indeed the issue.

For anyone else who runs into the same problem, here's what worked for me using the Databricks Account CLI.

1. Install Databricks CLI

winget install Databricks.DatabricksCLI

2. Login to the workspace

databricks auth login --host https://adb-<workspace-id>.<region>.azuredatabricks.net

3. Login to the Databricks Account

databricks auth login --host https://accounts.azuredatabricks.net --account-id <account-id> --profile AccountAdmin

4. Verify the profiles

databricks auth profiles

5. Get the Metastore ID

databricks account metastores list --profile AccountAdmin

6. Create the Storage Credential

databricks account storage-credentials create <metastore-id> --json @credential.json --profile AccountAdmin

credential.json

{
  "credential_info": {
    "name": "poc-storage-credential",
    "azure_managed_identity": {
      "access_connector_id": "<access-connector-resource-id>"
    }
  }
}

7. Verify the Storage Credential

databricks account storage-credentials list <metastore-id> --profile AccountAdmin

Copy the Storage Credential ID.

8. Update the Metastore

databricks account metastores update <metastore-id> --json @update-metastore.json --profile AccountAdmin

update-metastore.json

{
  "metastore_info": {
    "storage_root_credential_id": "<storage-credential-id>"
  }
}

9. Verify the Metastore

databricks account metastores get <metastore-id> --profile AccountAdmin

Verify that these fields are present:

• storage_root_credential_id

• storage_root_credential_name

• default_data_access_config_id

After that, I was able to create catalogs, schemas, and managed Delta tables successfully.

Hopefully this helps anyone else who runs into the same issue. Thanks again for identifying the UI bug and suggesting the CLI workaround! @iyashk-DB