Power Platform admin center telemetry data export to Microsoft Azure Data Lake

Important

This content is archived and is not being updated. For the latest documentation, go to Administer Microsoft Power Platform. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.

Enabled for Public preview General availability
Admins, makers, marketers, or analysts, automatically Jun 25, 2021 -

Business value

Using your own Azure Data Lake allows you to slice and dice the data based on your unique requirements. You can build custom reports with Power BI, including views at the individual business unit level and detailed app-level reports at the tenant and environment level. Having the data in your own data lake also means the data can be stored for durations as required by your organization's data retention policies.

Feature details

You can opt in to export all your tenant data into your own Azure Data Lake Storage instance without having to write any code. You'll need to have the Azure Data Lake Storage set up prior to setting up a daily data export via the Power Platform admin center. Once set up, the data will be made available in a Common Data Model schema. The Common Data Model based metadata makes it possible for data and its meaning to be shared across applications and business processes, such as Microsoft Power Apps, Power BI, Dynamics 365, and Azure. The data will include the full inventory for all apps, connectors, and associated metadata that exist in the tenant as well as the usage telemetry, which will be comprised of data from the day the export starts.

After the first data export, there will be incremental daily updates. Once the data is in your data lake, you can, for example, leverage Power BI dataflow to connect to Azure Data Lake Storage and start building reports and dashboards.

Here are some sample scenarios that will light up in your own data lake:

  • Tenant-level metrics across apps for different business units
  • Environment with the most apps with app and flow names ranked in order of usage
  • Custom and standard connectors creation and usage trend with filters for location and business units
  • Business unit specific trends (for example, a report that lists all marketing department employees using a specific app and a list of all apps used by specific users)
  • Business units with the most apps along with details of the app
  • Trends and details per business unit on connector usage
  • App usage based on business units to answer questions like: How many users in Eastern Time zone marketing are using a particular app?
  • List of users per business unit with the most apps filtered by sessions or runs

See also

Preview: Set up Microsoft Power Platform self-service analytics to export Power Apps inventory and usage data (docs)