Doing a test configuration for Intune Asset Match but getting URL redirect errors

[CTRL_Admin]

Hi Team so I was following the YouTube video regarding Intune Automations I am currently stuck with this issue where I am doing a test connection and I keep on running to "no reply address registered for the application".

So, I enabled in the Platform configurations the Mobile and Desktop Applications Redirect URI's I have tried the two URL links in the Intune Connection but no go.

I have used the one that is on the yaml that was provided in the YouTube video. Can someone from this group to enlighten me a bit.

[CTRL_Admin]

Thanks Jacob, I will let you know.

[CTRL_Admin]

Hi Jacob,

Do you think that having a different username logged in in Lansweeper affects the access or permissions on it? Because the username that is being used in Lansweeper Flow Builder is not connected to the Azure AD.

Just a thought while trying this.

[Jacob_H]

I think it does - I had to have a license for my (personal) account to authenticate/connect Intune.  It's not ideal, and I submitted a ticket to have that fixed - aaand.... it looks like they upgraded the intune connector to use OAuth Client Credentials 🙂  - I'll see if they updated the documentation.  if you update the intune connector to the latest version, you will see the choice under 'Connection Type'  there's a new choice (OAuth 2.0 (Client Credentials).... give that a try.

[Jacob_H]

I tried the above and it at first didn't authenticate, by the time i asked the developers (10 minutes) and re-tested for them, it worked.  (shrug) 🙂   give it a go -  but you will need to put in the following callback URL under the app registrations > (app name) >  Manage > authentication>  Web Redirect URL:  https://oauth2.flowbuilder.eu.lansweeper.com/callback

[CTRL_Admin]

I have recreated the Intune connector and everything, but I still get authorization failed. Is there something that is missing?

Microsoft Intune - followed again this instructions

Intune Automations - Lansweeper - and this after still getting 

Authorization failed.

Please contact the person who initiated the authentication request for more information.

Could someone assist me?

[Jacob_H]

Hey CRTL - apologies for not responding sooner - I get that when either my client secret expires or i have the wrong ID/secret, but i suppose it could also be permissions.

Try this powershell script with your tenant, clientid, clientsecret - the script authenticates and lists your intune devices.

$tenantId = "<your tenant ID>"
$clientId = "<your client ID>"
$clientSecret = "<your client secret>"
$scope = "https://graph.microsoft.com/.default"

$body = @{
    client_id     = $clientId
    scope         = $scope
    client_secret = $clientSecret
    grant_type    = "client_credentials"
}

$tokenResponse = Invoke-RestMethod -Uri "https://login.microsoftonline.com/$tenantId/oauth2/v2.0/token" -Method POST -Body $body
$accessToken = $tokenResponse.access_token

# Now use the token to call Intune
$headers = @{ Authorization = "Bearer $accessToken" }
Invoke-RestMethod -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices" -Headers $headers

[CTRL_Admin]

 I get this error if I don't put a URL. I am not sure if what URL to use.

If I use the URL message that Lansweeper is giving me I get this.

Is there a specific URL that is needed?

[Jacob_H]

Yes, if you delete it, the InTune steps will turn red until you add it back and connect it.  Have you seen my article versus the video?  https://www.lansweeper.com/blog/pro-tips/intune-automations (sorry if the link doesn't load right, I'm on my phone).  Delete that connector and re-do it... If you still can't connect it, I'll see if I can fix the file.  You might be better off just following the complete walkthrough.. let me know how it turns out .. and apologies for the YAML being weird

[Jacob_H]

Wow so you're the one who watches the video :). Sorry for the frustration - have you tried blowing away the InTune connector and recreating it?  I've had that happen before when importing those files, I might not have exported correctly.