Checking the docs I noticed this statement under Azure storage access page:

[https://learn.microsoft.com/en-us/azure/databricks/external-data/azure-storage]

Deprecated patterns for storing and accessing data from Azure Databricks

The following are deprecated storage patterns:

• Databricks no longer recommends mounting external data locations to Databricks Filesystem. See Mounting cloud object storage on Azure Databricks.

Well, so far I used ADLS v2 mounts (at eg. dbfs:/mnt/datalake) as locations for my databases/schemas:

CREATE SCHEMA foo LOCATION '/mnt/datalake/foo';

Sounds like this is no longer recommended, is it? And remaining methods on the page describe ad-hoc connections - except for Unity catalog external locations, but even that is mentioned as a way to create primarily external tables:

Unity Catalog manages access to data in Azure Data Lake Storage Gen2 using external locations. Administrators primarily use external locations to configure Unity Catalog external tables, but can also delegate access to users or groups using the available privileges (READ FILES, WRITE FILES, and CREATE TABLE).

What about managed tables then? Any guidelines?

Last but not least, why actually are mounts not recommended in the first place?