User-Agent based behaviour in AzureAD vs. AADInternals's Get-AADIntAccessTokenForAzureCoreManagement

[muzso]

User-Agent based behaviour in AzureAD vs. AADInternals's Get-AADIntAccessTokenForAzureCoreManagement

[muzso]

Here's a sample screenshot from the error message with the default AADInternals code:

(Note: I've edited the page by replacing the company name and logo before I took the screenshot :-) )

Here's a sample screenshot from the successful result where a custom (curl) user-agent is used in AADInternals:

[NestoriSyynimaa]

Thanks for letting me know this! Conditional Access "Device platform" conditions are based on User-Agents, so probably related to that. Have you tried to run it from Cloud Shell or Mac?

[muzso]

Have you tried to run it from Cloud Shell or Mac?

No.
I've tried to run AADInternals with the latest PowerShell for Linux, but it didn't work.
I've tried the (at the time) latest PowerShell for Windows 10, but it didn't work either.
Finally I've settled on the old PowerShell 5.1 (that probably came as a default with Windows 10 itself), because that was the only PS that AADInternals seemed to work with.

[NestoriSyynimaa]

v0.9.x versions should work in other PowerShell versions too.