I'm working a report which is to source most of its data from Azure Log Analytics Workspaces (looking at potentially replacing an Azure workbook).
This seems to be going relatively as expected from the log analytics Kusto queries perspective, and it appears I can use direct query to attach to those workspaces, run the Kusto queries using the Azure Data Explorer connector, and do all that live as each individual user (not using import mode, service accounts, scheduled refreshes, etc).
My issue is that within the Azure workbook I'm looking at replacing, I drive the rest of the query activity (the Log analytics workspaces those Kusto queries are run against) off of a parameter in the Azure workbook that queries the Azure Resource Graph as the consuming user to see if they can view the various log analytics workspaces involved. If they can't see the log analytics workspaces involved, it hides certain parameter settings from them so that they cannot attempt to run queries against log analytics worspaces they themselves don't have Azure access to and return errors as a result.
I do not have a problem crafting the Azure resource graph query itself, rather when I do so there appears to be no option to make this "direct query" as far as the Azure resource graph connector is concerned. This trashes the whole approach of using a graph query to tell if the consuming user should see certain options, as that imported data table wouldn't be run as them each time the workbook is accessed to be able to tell what further actions should even be presented to the user.
Basically am I just missing a direct query option for the Azure resource graph connector? Or does that just not exist?
