Working with GraphAPI & PowerBI the easy way!

I’m sure lots of us out there in the IT world have spent some time with PowerBI with varying degrees of headache-inducing successes. I know myself that working with fairly flat data sources, you can very easily create some incredible reports that will make you look like a data wizard to even the most jaded manager out there, however once you want to start working with complex data sets or start veering into the world of custom visualisations, pain is sure to be just around the corner.

This is where I found myself just last year – I was tasked with capturing some data from Intune, AAD & SCCM to present a reporting solution to a prospective client. “Sure, no problem at all” I cluelessly said, as I rapidly pulled in data from SCCM like it was no problem…
Unfortunately, when it came time to access data from Azure via the fantastic GraphAPI, I ran into some roadblocks. Lets drill into what those roadblocks were.

Firstly, let’s try and gather some very basic info – User details & their managers. Pretty simple process.
Open up PowerBI and get some data from a web source

Web Data

Type in your perfectly formed Graph query – in this case, it would be “$expand=manager” and hit OK.

Graph URL

Oh, we were never given an option to authenticate… so let’s go and do that – go to organizational account and sign in with your details that totally have the right access for what you want (we are all IT professionals after all, are we not?).


After hitting connect, finally, we are greeted with a very underwhelming result – a single list row.

Lame List

No worries… just click on the list value and it’ll expand into the results. Very arduous and there are many more steps (that can all be automated and if there is any demand, I’ll write about them) but once you have formatted the results, you’ll get this data.

Underwhelming Results Abound

*very exciting stuff*

So cool, that’s simple, we’ve got our generic data for each user in our tenant, lets try and get some data on the devices we manage – it should be the same process, so lets do that, follow the exact steps above but this time, our graph query is going to look like this.


Again, yeah, we aren’t authenticated, so go through that process – again, the account we are using definitely has access – we are all professionals here… so alright, authenticate and we should get our data like last time.

Sad Trombone

“cool”. Now at this point, you might be going back and thinking you don’t have access to that level of data – hey, even as the prestigious IT professionals that we all definitely are, we all make mistakes.

Here’s the kicker – that’s not the issue. The problem seems to stem from the simple fact that whatever application Id PowerBI is using to authenticate against, it just doesn’t have the access required to traverse most of your tenant data.

The solution seemed so obvious – if PowerBI doesn’t give me the control to authenticate exactly how I want, then why not make my own middleware data gateway?!

All that is required is a function to non-interactively authenticate into Graph, some fairly basic code to form the GraphAPI URL for each request, and a place to store the code that can expose the code via an HTTP endpoint. (I promise it really is easy).

The simplest way to do this is to create a function app inside your Azure tenant and throw the code into it. I will not go into detail on how to create a function app in this post as I expect it is relatively common knowledge at this point, but if anyone has any questions around it, please feel free to contact me directly.

Alright – we all have our function app created? we’ve given it some cool name? I’ve already taken GraphConnector (which I’m very happy about). No, let’s add a function to our app.

New Function

Create a custom function, enable experimental language support, filter the language to PowerShell and select HTTP trigger

PowerShell HTTP Trigger

Give the function a name and create it. You will now be greeted with a hello world sample function. Here’s where we will place our connector code. For now, delete everything in the code window and save the file.

The most interesting parts of the code we will use are how we extract data from JSON objects as well as how to capture request data that is sent to the code. We will only be using this connector with the Get method, thus all incoming data is given its own variable name. Below we see that we want to be able to receive tenant details, a query string, and a version string (V1.0 or Beta)

As this is a completely non-interactive solution, we need to store relevant credentials somewhere, there are *many* ways to do this securely in Azure, one being using a key-vault, another being to store the credentials as strings in the function application settings, but the way I’ve grown accustomed to is to create an application config file and store it in the directory with the rest of the function code – yes, before you mention anything, there is obviously a security risk storing credentials unencrypted anywhere and I strongly recommend that anyone looking at implementing this solution be aware of these implications and proceed with care.

With that warning out of the way, let’s add some other required files.

On the right, click on View Files to expand the file list out, select upload and import the Azure AD *.dlls used by the AzureAD module (these will be provided in the final GitHub Repo). Your folder structure should now look like this.

File Structure

Next, select add and give the new file the name appConfig.json. Below is the json structure to follow for this solution. You can have as many tenant credentials as you want.

Now save the contents of your appConfig.json file and go back to the main function code – run.ps1. The next step is to import the contents of the appConfig.json so that we can use the credentials to authenticate into Graph.

As you can see above, the variable $EXECUTION_CONTEXT_FUNCTIONDIRECTORY is the default variable that gives us the same end result as $PSScriptRoot would do in a normal PowerShell environment.
We are also defining the location of the AzureAD *.dlls for the functions to use each time they are called.

We will now extract the credentials based on the tenant details sent to the function by the requestor.

Now that we have our credentials in the session, we can throw them at our functions along with the other relevant variables. Below is the function to create an authentication header.

The only thing I will mention about the above code is that I am specifying what “space” I want to authenticate with – for each token request you need to authenticate against an appropriate Application Id. This can be a custom application that you have created in your Azure tenant that has all access you could ever need, or in this example, multiple generic Application Ids – So if I want to access Intune, I switch programmatically to use the generic Intune Application Id, and similarly, if I want to query AAD, I use the AAD Application Id.

Next is the function to form the correct GraphAPI URL, attach the authentication token to the header of the request and send us the results back as an object to work with.

Again, nothing revolutionary here – the function just creates the GraphAPI URL and stores the results for us like with the AuthHeader function, there are hundreds of ways to do this and you should simply study my example to understand the basics.

Finally, we will send the results back to the requestor.

Here we are simply converting the GraphRequest object into a properly formed JSON object, storing it in a temporary file that is then sent to the requestor – the default variable for the temp file is $res.

Congratulations for sticking with me so far – we are on the home stretch, I promise.

Once you’ve saved all that code (you have saved it haven’t you?), capture the function URL, by clicking Get Function URL above the code editing window – save this to your clipboard and let’s move back to PowerBI.
Create a new web request as we did initially. This time instead of accessing the GraphAPI directly, we will go through our newly created data gateway – paste the Function URL from the previous step and now we will build out the URL to include the content to send to the function.

The basic Get Method URL for a GraphAPI call is quite simple – after the URL, you append each variable and value along with an ampersand. So to form the URL to get the data we want, it would look like this (I’ve broken each URL part into its own row to make it easier to read).

URL forming is easy

Once you’ve formed your URL, hit OK and if all goes to plan – you should have a beautiful list of records waiting for you to convert to a table!

Final results

As always, all of today’s code and files will be available on my GitHub (right here) for your review and use.

Hopefully, this has been helpful to you and always, if you have any improvements/complaints or just wish to discuss the solution provided above, leave a comment below or reach me on twitter @powers_hell


I am planning a series of posts that all revolve around what you can do once you start using Azure Functions to work as data-gateways – stay tuned for my next post which will focus on leveraging Azure Functions to monitor Intune for unapproved modifications!

1 comment

  1. […] In my last post, I showed you how to move a very common task – authenticating into the GraphAPI, up into an Azure Function App. […]

Comments are closed.