Power BI Embedded monitoring data

When you have critical applications and business processes that rely on Azure resources, you want to monitor those resources for their availability, performance, and operation. This article describes the monitoring data that Microsoft Power BI Embedded generates and how you can use the features of Azure Monitor to analyze and set alerts for this data.


You can also use the Premium metrics app to monitor your capacity.

Power BI Embedded Overview page

For each Power BI Embedded instance in the Azure portal, the Overview page includes the following information:

  • Resource group: The resource group the Power BI Embedded instance belongs to
  • Status: The status of the Power BI Embedded instance
  • Location: The location of the Power BI Embedded instance
  • Subscription: The name of the Power BI Embedded instance subscription
  • Subscription ID: The ID of the Power BI Embedded instance subscription
  • Resource name: The name of the Power BI Embedded instance
  • SKU: The SKU that the Power BI Embedded instance uses
  • Resource mode: The mode of the Power BI Embedded resource

What is Azure Monitor?

Power BI Embedded creates monitoring data by using Azure Monitor. Azure Monitor is a full-stack monitoring service in Azure that provides a complete set of features to monitor your Azure resources. It can also monitor resources in other cloud services and on-premises.

For more information, see Monitor Azure resources with Azure Monitor to learn about:

  • Azure Monitor and how it's integrated into the portal for other Azure services
  • The types of data collected by Azure Monitor for Azure resources
  • Azure Monitor tools that are used to collect and analyze data

The following sections build on this article by describing the specific data gathered for Power BI Embedded and provide examples for configuring data collection and analyzing this data with Azure tools.

Monitoring data

Resources from different Azure services all generate monitoring data in the same format so that you can use the same Azure Monitor tools to analyze them. Power BI Embedded creates monitoring data in the same format as these other Azure resources.

For information on the metrics and logs metrics that Power BI Embedded creates, see the Power BI Embedded monitoring data reference.

Collection and routing

Although platform metrics and the Azure Monitor activity log are collected and stored automatically, you can route them to other locations by using diagnostic settings. Diagnostic settings define where resource logs and metrics for a particular resource should be sent.

Resource logs aren't collected and stored until you create at least one diagnostic setting and route it to a location. When you create a diagnostic setting, you specify which categories of resource logs to collect. The categories for Power BI Embedded are listed in the Power BI Embedded monitoring data reference.

For more information about how to create and configure diagnostic settings by using the Azure portal, Azure CLI, or Azure PowerShell, see Diagnostic settings in Azure Monitor.

Use Azure PowerShell to enable diagnostics

To enable metrics and diagnostics logging with Azure PowerShell, use the following Azure PowerShell commands. For information about how to use Azure PowerShell to enable diagnostics, see Configure a Log Analytics workspace in Azure Monitor using PowerShell.

  • To enable storage of diagnostics logs in a storage account, use this command:

    Set-AzDiagnosticSetting -ResourceId [your resource id] -StorageAccountId [your storage account id] -Enabled $true

    The storage account ID is the resource ID for the storage account where you want to send the logs.

  • To enable streaming of diagnostics logs to an event hub, use this command:

    Set-AzDiagnosticSetting -ResourceId [your resource id] -ServiceBusRuleId [your service bus rule id] -Enabled $true
  • The Azure Service Bus rule ID is a string with this format:

    {service bus resource ID}/authorizationrules/{key name}
  • To enable sending diagnostics logs to a Log Analytics workspace, use this command:

        Set-AzDiagnosticSetting -ResourceId [your resource id] -WorkspaceId [resource id of the log analytics workspace] -Enabled $true
  • Get the resource ID of your Log Analytics workspace with the following command:


You can combine these parameters to enable multiple output options.

The metrics and logs you can collect are discussed in the following sections.

Analyze metrics

You can analyze metrics for Power BI Embedded with metrics from other Azure services that use Azure Monitor metrics explorer by selecting Metrics from the Azure Monitor menu. For information about this tool, see Get started with metrics explorer.

For a list of the platform metrics collected for Power BI Embedded, see the Monitoring Power BI Embedded data reference.

For a reference list, see resource metrics supported in Azure Monitor.

Analyze logs

Data in Azure Monitor Logs is stored in tables where each table has its own set of unique properties.

All resource logs available through Azure Monitor share a common top-level schema and each service has its own service-specific schema. For information about the schema for Power BI Embedded resource logs, see the Power BI Embedded Data Reference.

The Azure Monitor activity log is an Azure platform log that provides insight into subscription-level events. You can view it independently or route it to Azure Monitor Logs, where you can do much more complex queries using Log Analytics.

For a list of the types of resource logs collected for Power BI Embedded, see Resource logs.

For a list of the tables used by Azure Monitor Logs and queryable by Log Analytics, see Supported metrics with Azure Monitor

Sample Kusto query


When you select Logs from the Power BI Embedded menu, Log Analytics opens with the query scope set to the current Power BI Embedded resource. This means that log queries will only include data from that resource. If you want to run a query that includes data from another Power BI Embedded resource or data from other Azure services, select Logs from the Azure Monitor menu. For more information, see Log query scope and time range in Azure Monitor Log Analytics.

Here's an example of a query that completes in less than five minutes (300,000 milliseconds):

    search *
    | where Type == "AzureDiagnostics"
    | where ( OperationName == "QueryEnd" )
    | where toint(Duration_s) < 300000   


Azure Monitor alerts proactively notify you when important conditions are found in your monitoring data. These alerts allow you to identify and address issues in your system before your customers notice them. You can set alerts on metrics, logs, and the activity log.

Next steps

Learn more about monitoring data: