Skip to content
Azure Function that acts as a Proxy to the Microsoft Graph, for the purpose of allowing Power BI to connect to the Microsoft Graph
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
MicrosoftGraphProxyFunction Make sure that there is no impact whether or not the KeyVaultUri is s… Mar 12, 2019
.gitignore Make sure that there is no impact whether or not the KeyVaultUri is s… Mar 12, 2019
MicrosoftGraphProxy.sln Code checkin Nov 2, 2018

Microsoft Graph Proxy Function


Microsoft Graph contains an enormous amount of information that might be useful to show in a Power BI report. Up until May 31st, 2018 this was possible out of the box, but it stopped working (issue report).

This solution is a temporary workaround until Microsoft fixes the issue or releases a dedicated Microsoft Graph connector for Power BI.

How it works

The code is an Azure Function that accepts any get request and passes the request on to the Microsoft Graph. Upon receiving the result, some transformation is done to make sure subsequent requests (eg. paging) get send through the Azure Function (instead of directly to the Microsoft Graph).


GET https://{function-app-name}
GET https://{function-app-name}$select=id,displayName
GET https://{function-app-name}{teamId}

More information

Detailed explanation coming soon in a blogpost on



Getting started


  1. Create an Azure Function App in the Azure Portal
  2. Clone the repository
  3. Deploy the code into the newly created Azure Function App
  4. In the Azure Portal, open the Function App
    1. Open Platform Features
    2. Open Managed service identity
      • Register with Azure Active Directory: 'On'
      • Save
    3. Open Authentication / Authorization
      • App Service Authentication: 'On'
      • Action to take when request is not authenticated: 'Log in with Azure Active Directory'
      • Azure Active Directory:
        • Management mode: 'Express'
        • Management mode: 'Create New AD App'
        • Create App: 'Microsoft Graph Proxy Function'
        • Grant Common Data Services Permissions: 'Off'
        • Save and close the blades
    4. Open Authentication / Authorization
      • Azure Active Directory
        • Management mode: 'Advanced'
        • Copy and store the values for:
          • Client Id
          • Client Secret
        • Allowed token audiences
          • Copy the existing url
          • Add it again, without '/.auth/login/aad/callback' (make sure there is no more ending /)
        • Save
  5. In the Azure Portal, create a KeyVault
    1. While creating
      • Open Access policies
      • Add new
      • Select principal: 'Name of your Function App'
      • Secrets permissions: 'Get'
      • Close blades, click Create
    2. Open the new Azure Key Vault
      • Copy and store the url for later
      • Secrets
      • Click Generate/Import
        • Upload options: 'Manual'
        • Name: 'ClientSecret'
        • Value: 'the secret from the Azure AD Application step'
        • Content type: 'leave empty'
        • Set activation date? 'Unchecked'
        • Set expiration date? 'Unchecked'
        • Enabled? 'Yes'
        • Click Create
  6. In the Azure Portal, open the Azure Function App
    1. Open Platform features
    2. Open Application settings, add the following keys with values:

Assign permissions to Microsoft Graph

  1. In the Azure Portal, open Azure Active Directory
  2. Open App registrations, and find Microsoft Graph Proxy Function in the list
  3. Open the Settings and go into Permissions
  4. Add Microsoft Graph as API and select the required permissions.
    • Application Permissions when UseApplicationPermissions is true, and you want the Azure Function to connect to the Microsoft Graph
    • Delegated Permissions when UseApplicationPermissions is set to false, and you want to access the Microsoft Graph on behalf of the logged in user

Using in Power BI Desktop

  1. Add a data source, select OData.
  2. Enter the url of the Azure Function and append the Microsoft Graph query
  3. When asked for authentication, select Organizational Account and enter the credentials of a user account.

Known issues

  • Access reports as JSON from the /beta endpoint results in a parsing issue in Power BI. Since the function is just passing through information, this issue is probably caused by Microsoft Graph or Power BI
  • Accessing large datasets might result in a 429 Too Many Requests response. Power BI doesn't handle this gracefully and just errors out.
You can’t perform that action at this time.