@thesqlpro, please do add a DoD and fill in the metadata.

So far these notebooks function as expected with Unity Catalog as the mounts are created properly in the setup.py

For explore.py no changes are needed. The mount points work fine as long as the ADF pipeline runs and stages the data in the proper paths.
For the other two notebooks, just a simple fix of adding USE CATALOG sensordata at the beginning of the notebook. Additionally to that, there needs to be some user permissions changes.

These are the permissions needed:

Because the SPN from ADF is going to be generated it will be difficult to put together the permissions needed. This is because the Data Control Language (DCL) is SQL based in the notebook and has some difficulties with dynamic SQL (having to inject the SPN somehow into the GRANT syntax for granting privileges). The APIs for setting permissions currently not supporting Unity Catalog actions (must be done through UI or SQL).

My solution is to grant these permissions to All account users since this catalog is only for testing purposes. This can be added to the setup.py (Sql) or the readme (via UI).

Currently available APIs for permissions and Unity Catalog.
https://docs.databricks.com/api/azure/workspace/permissions
https://docs.databricks.com/api/azure/workspace/catalogs