> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/data-exporters/exporter-for-azure-data-lake/exporter-to-microsoft-power-bi.md).

# Exporter to Microsoft Power BI

{% hint style="warning" %}
This documentation references external sources. Nexthink does not have control over the accuracy of third-party documentation, nor any external updates or changes that might create inconsistencies with the information presented on this page. Please report any errors or inconsistencies to [Nexthink Support](https://support.nexthink.com/).
{% endhint %}

This document describes how to export Nexthink data into Azure Data Lake Gen2 in CSV format to be used in Microsoft Power BI.

## Prerequisites <a href="#exportertomicrosoftpowerbi-prerequisites" id="exportertomicrosoftpowerbi-prerequisites"></a>

* An Azure subscription.
* A storage account that has a hierarchical namespace. This article assumes that you've already created a storage account.
* One of the following roles for the storage account: **Blob Data Reader**, **Blob Data Contributor** or **Blob Data Owner**.
* One or multiple Nexthink Data Exporters configured in the Nexthink web interface that are exporting files into the Azure Data Lake Gen2 `mercuryteam` container.
* One or multiple CSV files containing Nexthink data that is located in your storage account.
* A **Power BI Desktop** instance.

## Connecting to Azure Data Lake Storage Gen2 from Power Query Desktop <a href="#exportertomicrosoftpowerbi-connectingtoazuredatalakestoragegen2frompowerquerydesktop" id="exportertomicrosoftpowerbi-connectingtoazuredatalakestoragegen2frompowerquerydesktop"></a>

Follow [the steps listed in the Microsoft Documentation](https://learn.microsoft.com/en-us/power-query/connectors/data-lake-storage#connect-to-azure-data-lake-storage-gen2-from-power-query-desktop).

If you happen to choose **CDM (Common Data Model)** view instead of **File System** view, the following option appears:

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-1b5c80e4c96cda064d99b3eb2dfea6abfb449cd7%2Fscreenshot-2022-11-23-at-09-24-27.png?alt=media" alt="" width="292"><figcaption></figcaption></figure>

In the fourth step of the [Microsoft Documentation](https://learn.microsoft.com/en-us/power-query/connectors/data-lake-storage#connect-to-azure-data-lake-storage-gen2-from-power-query-desktop), the **Navigator** dialog box shows all files under the URL you provided. Verify the information, then select **Transform Data** to transform the data in Power Query or **Load** to load the data.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-ff58ec08cf5095f461da2f0a4c6e8f7e83813a66%2Fscreenshot-2022-11-23-at-09-05-35.png?alt=media" alt=""><figcaption></figcaption></figure>

## Connecting to Azure Data Lake Storage Gen2 from Power Query Online <a href="#exportertomicrosoftpowerbi-connectingtoazuredatalakestoragegen2frompowerqueryonline" id="exportertomicrosoftpowerbi-connectingtoazuredatalakestoragegen2frompowerqueryonline"></a>

Follow [the steps listed in the Microsoft Documentation](https://learn.microsoft.com/en-us/power-query/connectors/data-lake-storage#connect-to-azure-data-lake-storage-gen2-from-power-query-online).

## Limitations <a href="#exportertomicrosoftpowerbi-limitations" id="exportertomicrosoftpowerbi-limitations"></a>

Refer to the [Microsoft Documentation](https://learn.microsoft.com/en-us/power-query/connectors/data-lake-storage#limitations) to learn more about the limitations of connecting Power BI Desktop to an Azure Data Lake Storage Gen2.

## Analyzing data in Azure Data Lake Storage Gen2 with Microsoft Power BI <a href="#exportertomicrosoftpowerbi-analyzingdatainazuredatalakestoragegen2withmicrosoftpowerbi" id="exportertomicrosoftpowerbi-analyzingdatainazuredatalakestoragegen2withmicrosoftpowerbi"></a>

We strongly recommend you leverage the online [Microsoft documentation](https://learn.microsoft.com/en-us/power-query/connectors/analyze-data-in-adls-gen2) to analyze and visualize data stored in a storage account that has a hierarchical namespace (Azure Data Lake Storage Gen2) using Power BI Desktop.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexthink.com/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/data-exporters/exporter-for-azure-data-lake/exporter-to-microsoft-power-bi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.