You are currently viewing Troubleshoot your Graph API calls with Postman

Troubleshoot your Graph API calls with Postman

When you try to optimize your Graph API calls, don’t know what exactly the error is or even if you want to have a nice view for the results you get, then you definitely should use Postman!

In the next step I will describe you how to setup your Postman instance.
(Note: This is just my method – It’s not an Add for Postman)

Table of content

Get Access Token

Connect to Graph.Microsoft

Connect to Management.Azure

Token Name: What ever you want 🙂
Grant Type: If you have a Client-Secret, you should use “Client Credentials”
Access Token URL: https://login.microsoftonline.com/*Tenant Name*.onmicrosoft.com/oauth2/v2.0/token
Client ID: Application ID of App Registration
Client Secret: Client Secret
Scope: https://graph.microsoft.com/.default
Resource: https://management.azure.com

Send GET request

In this case we want to get all failed provisioning’s.
You can either enter the filter in der URL line or define it as params. 

Why use Postman to troubleshoot?

In this case I have a typo in my URL:
https://graph.microsoft.com/beta/auditLogs/provisioning?filter=statusInfo/status eq ‘failuree

Here you see the error messages in PowerShell and Postman:

PowerShell output

Postman output

Leave a Reply