Working with Azure Active Directory Graph Api from Powershell

Hello Everyone,

In this blog post I’m going to show a simple way to work with Azure Active Directory Graph Api directly from Powershell.

Basically in order to access this API we first need to be authenticated with ADAL (Active Directory Authentication Library), this authentication will is done trough a JSON formatted token that is then passed as a parameter in the header for the Invoke-RestMethod cmdlet.

This blog post assumes you already have Azure Powershell 1.0 or greater module installed in your computer, if not, you can install it from

We don’t intend here to build a full featured script but at least provide a function to get the Authentication Token and show a few examples using Graph Api calls. For a similar article but based on REST API, Azure Management and a Sample Script to identify page blob status (like if a VHD is attached or not to a VM), please refer to Working with Azure REST APIs from Powershell – Getting page and block blob information from ARM based storage account sample script blog post.

To get started, open a Powershell command prompt and type (or paste) the following code, this will create a function in your session that will be able to return the Authentication token:


function GetAuthToken
       $adal = "${env:ProgramFiles(x86)}\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure\Services\Microsoft.IdentityModel.Clients.ActiveDirectory.dll"
       $adalforms = "${env:ProgramFiles(x86)}\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure\Services\Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms.dll"
       [System.Reflection.Assembly]::LoadFrom($adal) | Out-Null
       [System.Reflection.Assembly]::LoadFrom($adalforms) | Out-Null
       $clientId = "1950a258-227b-4e31-a9cf-717495945fc2" 
       $redirectUri = "urn:ietf:wg:oauth:2.0:oob"
       $resourceAppIdURI = ""
       $authority = "$TenantName"
       $authContext = New-Object "Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationContext" -ArgumentList $authority
       $authResult = $authContext.AcquireToken($resourceAppIdURI, $clientId,$redirectUri, "Auto")
       return $authResult
To use this function just type:
$token = GetAuthToken -TenantName "<your Azure AD tenant>"


For example:

$token = GetAuthToken -TenantName ""



Getting back to the example, lets define some variables so we can avoid lots of typing:

# Defining Azure AD tenant name, this is the name of your Azure Active Directory (do not use the verified domain name)
$tenant = ”” 
# Getting the authorization token
$token = GetAuthToken -TenantName $tenant
# Building Rest Api header with authorization token
$authHeader = @{


With these variables and results obtained from GetAuthToken function we built the foundation to start executing calls to Graph Api, this Api has the following format:


Each block of code now will perform a different task using Graph Api:

Getting tenant information

$resource = "tenantDetails"
$uri = "$tenant/$($resource)?api-version=1.6"
$tenantInfo = (Invoke-RestMethod -Uri $uri –Headers $authHeader –Method Get –Verbose).value




Getting a list of all users

$resource = "users"
$uri = "$tenant/$($resource)?api-version=1.6"
$users = (Invoke-RestMethod -Uri $uri –Headers $authHeader –Method Get –Verbose).value




Getting a list of users that Display Name starts with letter T by using OData filtering

$resource = "users"
$uri = "$tenant/$($resource)?api-version=1.6`&`$filter=startswith(displayName,'T')"
$users = (Invoke-RestMethod -Uri $uri –Headers $authHeader –Method Get –Verbose).value 




Getting a list of groups

$resource = "groups"
$uri = "$tenant/$($resource)?api-version=1.6"
$groups = (Invoke-RestMethod -Uri $uri –Headers $authHeader –Method Get –Verbose).value 




So far we only did read operations, what about creating a real user on Azure AD by using the graph API?

First, lets define our user properties in a Powershell hash table, in this way we can easily convert it to JSON format and send as the body content of the Graph Api Post method.

$newuser = @{
                "displayName"="Paulo Marques";

To see your hash table, just type $newuser and press enter:


Last step before jumping in the Invoke-RestMethod is converting this hash table into a JSON structure, type the following line and press enter:

$newuserJsonDef = $newuser | ConvertTo-Json

To see the newly converted object, just type $newuserJsonDef and press enter:


Lets build again our $uri variable:

$resource = "users"
$uri = "$tenant/$($resource)?api-version=1.6"

Run the Invoke-RestMethod cmdlet to get your user created on Azure Active Directory, notice the new parameters and values highlighted:

$result = Invoke-RestMethod -Uri $uri -Headers $authHeader -Method Post -Body $newuserJsonDef -ContentType "application/json"

Check the result by querying your new user:

$uri = "$tenant/users`?api-version=1.6`&`$filter=mailNickname eq 'pmc'"
(Invoke-RestMethod -Uri $uri –Headers $authHeader –Method Get –Verbose).value



For more information about Graph Api, please refer to the following articles:

Operations overview | Graph API concepts

Azure AD Graph API reference

Versioning | Graph API concepts

Supported queries, filters, and paging options | Graph API concepts


That’s it for this blog post, see you later!

Comments (11)

  1. UNIFYBob says:

    Minor uri variable correction:

    $uri = “$tenant/$($resource)?api-version=1.6”

    1. Hi UNIFYBob,

      The way the example also works, the issue that I was seeing is that when I pasted the code from Word it changed some of the characters and that’s why a direct copy and paste on PowerShell command prompt window was not working, I changed all the examples with your recommendation because it looks nicer that the original one and I also changed the way the examples are included in this post to follow all other subsequent posts that I had.

      Thanks for your comment.



  2. Ian Thomas says:

    Is there any way to automate the authentication process in a manner similar to the Connect-MsolService -Credential option?

    For example, if creds are stored in a variable $cred, then the following will authenticate without any prompts:
    Connect-MsolService -Credential $cred


    1. Bulent Ozkir says:

      Yes. You can visit my blog for that variation. I will post that this week sometime. Thanks.

  3. Irwin says:

    At the start of your post you probably should tell users to create an app in Azure AD first, from which they’ll get the client id and redirect URI that you use in the GetAuthToken method.

    1. Hi Irwin, the application ID in this case is PowerShell so this is not needed, it is already built in on Azure AD.

  4. How do i download the DLLs referenced?

    1. Hi Max,

      This DLL is part of the Azure PowerShell module which is the only requirement for this to work, as I mentioned in the blog, you can install it from URL.



  5. Matthias says:

    the function requires to authenticate with an user action.
    $authContext.AcquireToken($resourceAppIdURI,$clientId,$redirectUri, “auto”)
    Is there a way to use a encrypted password xml file that I can use the function within script that runs on a schedule ?
    $CredPath = “$home\Desktop\mycred.xml”
    Get-Credential | Export-Clixml -Path $CredPath

    1. Hi Matthias,

      The most secure way is to work with Azure Key Vault (, I put together below the list of documents and blog posts that will help you to securely authenticate:

      1) Create an Azure AD Service Principal and optionally assign what role that user will have.

      Using a Service Principal for Azure PowerShell Authentication

      2) Next, you can use my blog post on how to setup Azure Key vault and how to use it from PowerShell so you can securely retrieve the password (secret) you placed there.

      Safeguarding your passwords when deploying Azure Virtual Machines with Azure PowerShell module and ARM Templates by using Azure Key Vault

      3) Finally, the last step would be assigning a policy that allows the Service Principal to retrieve the secret from Key Vault, the steps are outlined at the Authorize the application to use the key or secret section.

      Get started with Azure Key Vault

      I didn’t test this but I believe it is a good start to automate an end to end scenario.

      Hope that helps.


      1. Matthias says:

        thanks – I will give it a try

Skip to main content