So it seems we need to talk about Graph and authentication again…
Recently, Microsoft announced an official “end of support timeline” for Azure Active Directory Authentication Library (ADAL) which means, any scripts or automation workflows that you use will need to be migrated over to the newer Microsoft Authentication Libraries (MSAL).
There are many differences between the two libraries, but the workflows are very similar – a request is sent using the libraries for access to specific areas of Azure and an authentication token is sent back giving you the keys into your Azure tenant.
While the announcement from Microsoft gives us a few years to move on, right now if you have moved your workloads over to PowerShell 7 (which you 100% should be), you may have noticed that working with ADAL is tricky.
And for reference, the same code in PowerShell 5.1.
The primary issue here is that PowerShell 7 just doesn’t natively support the old authentication libraries – you can work around it if you have your existing authentication scripts in a module that you import using the
-UseWindowsPowerShell compatibility flag, but that’s not an ideal scenario.
So how do we authenticate successfully in PowerShell 7 then? With MSAL of course!
For simplicities sake, I will not deep dive into manually creating MSAL requests, as luckily there is already a great module available to us on the PowerShell Gallery – MSAL.PS (Written by Jason Thompson). So Let’s go ahead and install that on our computer.
One of the benefits of MSAL is that it has been designed from the ground up to be completely cross-platform compatible, which means we get a few new ways to authenticate to devices that are “input constrained”. This is called “device code flow”.
Using the well-known Intune app id, lets try out Device Code Flow.
This is pretty cool – adding
-DeviceCode to our command generates a code that we can use on another device to authenticate “on behalf of” the initial requesting device.
But what if we want to keep it “old school” ? Can we just interactively authenticate?
The answer to that is “Yes. But not with the well-known Intune app id..”
Let’s try it now..
How annoying! But what does this error mean?
Simply put, the reply URLs in the AAD application we went to try and authenticate are missing the specific reply URL that MSAL needs registered, which is
So, what this means, is that until the maintainer of the “PowerShell Intune” application updates the app to include the correct scope, the only way we can use it with MSAL is by following the device code flow.
Until that time, we can create our own AAD application with the same permissions contained within the well-known app and use that instead.
For those interested in this, the permissions required are below.
|Intune Client Scope:|
I’ve already gone ahead and created this in my tenant and will be using it for all of my existing workflows and tools.
So now we have a new AAD application registered with the correct permission scopes AND the correct reply URL, let’s see the authentication flow in a simple Graph call.
The code above is a very simple example that grabs the authentication interactively and then queries Intune for any Win32 applications that have been packaged. Let’s see it in action..
Hopefully this has helped you understand the importance of migrating over to MSAL and gives you and idea how to begin migrating your workflows over to this new authentication library!
For more light reading on MSAL and how to plan migrations away from ADAL, check the links below: