What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Azure Subscription Cost Sensor - Could not authenticate with AzureAD

Votes:

0

Your Vote:

Up

Down

Hi. I realise this sensor has just been realised and is still in beta, however was wondering if anyway else was having problems getting it working?

I have followed all the instructions in the following articles, and checked twice. I am happy I setup all the correct tenant, subscription and client ID's and also the correct client secret;

https://www.paessler.com/manuals/prtg/microsoft_azure_subscription_cost_sensor https://kb.paessler.com/en/topic/88625-how-do-i-obtain-credentials-and-create-custom-roles-for-the-microsoft-azure-sensors

Have tried on both our corporate network and on a standalone install directly connected to the Internet - so don't thing this is a problem with our corporate network, firewalls etc.

The sensor returns the error "The sensor could not authenticate with Azure AD. Check your credentials in the device settings or look into the sensor log for more details."

Here is a dump of sensor log;

2020-12-22 11:45:39.362268 DEBG TId    5856 Result of Sensor 14236> Response Message is: #:error.authentication_failed
2020-12-22 11:45:39.362268 DEBG TId    5856 Result of Sensor 14236> #################### Exit sensor scan  ####################
2020-12-22 11:45:41.159167 DEBG TId   13600 Result of Sensor 14236> #################### Enter sensor scan ####################
2020-12-22 11:45:41.502925 DEBG TId   13600 Result of Sensor 14236> Authentication failed: ChilkatLog:

  ObtainAccessToken:

    DllDate: Jul 24 2019

    ChilkatVersion: 9.5.0.79

    ogging: 0

    sendReqFormUrlEncoded:

      sendReqHeader:

        omitContentType: 0

        sendReqHeader2:

          checkEstablishConnection:

            The connection already exists, as far as we know..

          --checkEstablishConnection

        --sendReqHeader2

      --sendReqHeader

    --sendReqFormUrlEncoded

    responseStatusCode: 401

    responseCode: 401

    non-success response status code.

    Failed.

  --ObtainAccessToken

--ChilkatLog


2020-12-22 11:45:41.502925 DEBG TId   13600 Result of Sensor 14236> Response Message is: #:error.authentication_failed
2020-12-22 11:45:41.502925 DEBG TId   13600 Result of Sensor 14236> #################### Exit sensor scan  ####################

Many thanks.

azure cost prtg

Created on Dec 22, 2020 11:59:27 AM by  ChrisS (0) 1

Last change on Dec 22, 2020 2:27:45 PM by  Stephan Linke [Paessler Support]



4 Replies

Votes:

0

Your Vote:

Up

Down

Hi,

please make sure that you also set the correct permissions for the Office 365 Management APIs, as described here.


Kind regards,
Matthias Kupfer - Team Tech Support

Created on Dec 23, 2020 10:32:15 AM by  Matthias Kupfer [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks Matthias. I have had a look at that article, which seems to related to Office 365 rather than Azure - is that right? Regardless I followed the article and the only difference which I found was the O365 Management API was missing so I added that. This did not resolve the issue. I notice that the article is marked as out of date so followed the link to the updated article (https://kb.paessler.com/en/topic/88462-how-do-i-obtain-credentials-and-set-permissions-for-the-microsoft-365-sensors) - everything is setup as per that guide. I did notice in the forum at the bottom of that article someone has mentioned setting the URI. This is something that I wasn't clear about and wasn't clear in the PRTG instructions - I am not sure what to set this to? Initially I had this set to the URL of my PRTG install, but changed it as suggested in the forum post to hhtps:login.windows.net however this hasn't resolved the issue either. Not sure if the URI is the root of my issue, but would be good to get some clarity on this also. Thanks.

Created on Dec 23, 2020 2:07:27 PM by  ChrisS (0) 1



Votes:

0

Your Vote:

Up

Down

Hi,

yes, that's definitely the right guide.

What does the logfile of the sensor look like? Did the error change?


Kind regards,
Matthias Kupfer - Team Tech Support

Created on Dec 24, 2020 3:15:52 PM by  Matthias Kupfer [Paessler Support]



Votes:

0

Your Vote:

Up

Down

The log file has not changed and reports the same error as in the original post, authorisation failure. I am still not sure exactly what I need to enter for the Redirect URI ?

Created on Feb 5, 2021 9:55:09 AM by  ChrisS (0) 1



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.