fbcideas_migusr's avatar
fbcideas_migusr
New Member
2 years ago
Status:
New

Web.Contents method should support authentication for HTTP POSTs or more Azure-specific connectors should be added

Multiple Azure services uses HTTP POST as HTTP query endpoints.


Current examples:


Azure resource graph queries:

  • https://learn.microsoft.com/en-us/rest/api/azureresourcegraph/resourcegraph(2021-03-01)/resources/resources?tabs=HTTP
  • HTTP POST only
  • looks like this is on planned state somewhere: https://feedback.azure.com/d365community/idea/e9bb947d-f424-ec11-b6e6-000d3a4f0da0
  • Third-party connector: https://github.com/viktorradu/powerbi-azure-resource-graph-connector


As a result it is really hard or impossible to ingest data from resource graph to Power BI



Log Analytics workspace queries:

  • https://learn.microsoft.com/en-us/rest/api/loganalytics/dataaccess/query/get?tabs=HTTP
  • HTTP GET. Limited[^1]
  • https://learn.microsoft.com/en-us/rest/api/loganalytics/dataaccess/query/execute?tabs=HTTP
  • HTTP POST



Log Analytics workspace HTTP GET query does not support passing multiple workspace Ids or resource Ids in query parameters.

To workaround this limitation KQL queries must be extended with use-case specific `workspace` keywords or with user-defined functions to get all required data when using HTTP GET


As a result Power BI and KQL query endpoint limitations makes really hard to ingest Log Analytics data to Power BI.


-----------------------------------------------------------------------------------------------


Would it be possible to enable authentication for HTTP POSTs or add more Azure-specific connecters?

Recent ideas