In Databricks, views are read-only objects composed from one or more tables and views in a metastore. They reside in the third layer of Unity Catalog’s three-level namespace. A view can be created from tables and other views in multiple schemas and catalogs. However, views might have different execution semantics if they’re backed by data sources other than Delta tables. Databricks recommends that you always define views by referencing data sources using a table or view name.

When it comes to Azure Storage, views are not stored as separate objects in the storage account. Instead, they are metadata constructs within Databricks that reference the underlying tables. This is why you can't see them in the Azure Storage account container. They exist within the Databricks environment and are used to provide a specific view or representation of the underlying data.