Seems like an networking issue. In a notebook attached to the custom cluster, try dbutils.fs.ls("abfss://<container>@<account>.dfs.core.windows.net/<path>") to confirm reachability before running CREATE EXTERNAL TABLE. (If this hangs or errors, itโs a network/permission issue, not UC SQL.)
Custom cluster runs uns in your VNet. If your ADLS firewall only allows particular VNets/subnets or private endpoints and your NCUS VNet isnโt allowed to reach EUS ADLS, UCโs validation calls from the custom cluster will stall or fail. You must open the network path from that custom cluster to the storage (firewall allowlist, Private Endpoint, DNS, outbound rules).