If a signed-in Lakehouse Monitor Optimizer (LHMLHO) user does not have access to any Azure Subscription and/or Databricks Workspace, but the LHM LHO admin still wants to provide read rights to that particular user (or group), the admin can use publicSubscriptionMetadata LHM LHO config file to make subscriptions and workspaces accessible in LHMLHO.

As an application-wide setting, use publicSubscriptionMetadata.csv file to provide read-only access to Subscriptions and Workspaces to any user that is able to login to LHM LHO App.

Public Subscriptions and Workspaces

LHM LHO configuration file publicSubscriptionMetadata.csvis used in order to expose subscriptions and workspaces to all users who use LHM LHO app regardless of the access rights of that user that are set in Azure or Databricks.

This file must be manually generated in storage account under a directory with the name as the subscription id, in a file named publicSubscriptionMetadata.csv. Public file is only read by LHM LHO app.

This file is used to allow signed-in users to list workspaces and see reports in LHM LHO even if that particular user does not have rights configured on that tenant.

For example, the user signs in to LHM LHO with an external AD account registered with a tenant from another Microsoft AD subscription, thus the signed-in user doesn’t have the sufficient rights to read workspaces from the subscription that also manages the Databricks workspaces. In order to allow this user to read workspaces that the admin deemed “public”, LHM LHO uses the publicSubscriptionMetadata.csv to expose these workspaces to this external user.

...

• use cloud storage path from LHM LHO Settings page

  • 

• define in blob storage a file named

...