Forum Discussion

TomasGazsi's avatar
TomasGazsi
Advocate I
1 year ago
Solved

How to connect GraphApi with PBi to get complete data?

Hi,  can anybody give me advice how to use MS GraphApi as datasource in PowerBi?  What is the purpose of my report? - I need get all tasks of Planner. Plan ID is SbuxRYX9cUuekCEIBEiv05gAAlg8. Wh...
Need Help
  • v-csrikanth's avatar
    v-csrikanth
    1 year ago

    Hi TomasGazsi 
    You're absolutely right in identifying the current limitations when connecting Power BI directly to Microsoft Graph API.

    1. Power BI doesn’t have a native Graph API connector, so an intermediate storage layer (like Dataverse, SharePoint, or Azure Data Lake) is required, depending on the tool (Power Automate, Logic Apps, etc.).
    2. Microsoft Graph Data Connect (MGDC) needs a Microsoft Fabric or ADF license—Power BI Premium alone isn’t enough. MGDC is built for large-scale, governed data extraction into Azure storage, not direct Power BI use.
    3. If upgrading licenses isn’t an option, the best workaround is automation: use Power Automate or Logic Apps to pull Graph data and store it where Power BI can access it.
    4. For small, non-real-time needs, exporting to CSV in SharePoint or OneDrive works well with scheduled refresh.


    If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
    Best Regards,
    Community Support Team _ C Srikanth.



v-csrikanth's avatar
v-csrikanth
Community Support
1 year ago

Hi TomasGazsi 

Direct connection from Power BI to Microsoft Graph API is not officially supported or recommended by Microsoft, mainly due to authentication challenges and limited OData compatibility. While it is possible to use OData.Feed or Web.Contents in Power BI to access some data from Graph API endpoints, this approach often leads to missing fields-such as the assignments{} property for Planner tasks-or inconsistent results, especially when working with nested or complex objects.

The reason certain fields like assignments{} are missing is that Power BI’s handling of OData and JSON expansion interprets each assignment’s unique user ID as a separate column, which complicates the process of expanding and normalizing the data for reporting purposes.

To extract and work with nested objects like assignments{} in Power Query, advanced M scripting is required. This typically involves transforming the assignments record into a list of key-value pairs and then expanding and normalizing these into rows for easier analysis in Power BI.

Best Regards,
Cheri Srikanth