Hello @HW413 

That is expected behavior because Unity Catalog fully manages and abstracts the underlying storage for these tables, handling all aspects of read, write, storage, and optimization automatically.

This design ensures centralized governance, security enforcement (e.g., preventing direct file system access that could bypass access controls), and lifecycle management—such as automatic data deletion after DROP TABLE (with a 7-day soft-delete retention for recovery) and built-in optimizations like auto-compaction—without exposing internal paths. 

You can also refer this community document for the same. 

https://community.databricks.com/t5/data-engineering/viewing-managed-delta-table-files/td-p/125741