The detailed information does not show how to grant access.

Hi there,

Did you also checked this article: https://helpdesk.paessler.com/en/support/solutions/articles/76000063073-how-and-where-do-i-obtain-credentials-for-azure-ad

The link does not says anything about the Office 365 Management API: https://helpdesk.paessler.com/en/support/solutions/articles/76000063073-how-and-where-do-i-obtain-credentials-for-azure-ad

Is it enough to create the azure app and get the ids?

The manual for the sensor creation could be better...

Thanks Christian

Hi Christian,

The mentioned article has a link about the "Office 365 Management APIs". Contains the link not the required information?

Thanks for your fast response but in this link 4 steps are described:

• Register your application in Azure AD
• Get Office 365 tenant admin consent
• Request access tokens from Azure AD
• Call the Office 365 Management APIs
  
  Nowhere it tells something about your instruction:
  "Set the following permission:
  
  API / Permissions name: Office 365 Management API.ServiceHealth.Read
  Type: Application"
  
  Thanks Christian

Hi Christian,

please note that you only need the tenant ID, Client ID and Client secret to use the Sensor. If you set the permissions, the Sensor should work.

Can Paessler please take this a bit seriously and create a document for it?

Hello,

the creation of the IDs and secret keys to access the Azure API is something documented by Microsoft, as Azure is their product. How to get the data is outlined here, though not as detailed step-by-step documentation.

Following the above instructions I met this problem in the STEP 4 Authorize the APP

https://login.windows.net/common/oauth2/authorize?response_type=code&resource=https%3A%2F%2Fmanage.office.com&client_id={your_client_id}

Sorry, but we’re having trouble signing you in. AADSTS500113: No reply address is registered for the application.

How to proceed?

Hello sharbatlyfruit,

that would be a question for Microsoft. As of now, accessing the Office 365 API is quite complex.

I'm also having the Sorry, but we’re having trouble signing you in. AADSTS500113: No reply address is registered for the application.

Anybody managed to get this working?

I'm at the same error: AADSTS500113: No reply address is registered for the application. It seems it might have something to do with Redirect URI (reply URL) ... Paessler's article says it's an optional if you don't know (how should I know it?)... but never revisits in the article. It appears it's required... how do we know what to set for the Redirect URI setting?

(I've tried setting it to "Web" type and entering the URL of my PRTG server but that did nothing.) :(

Same Problem here.

Hello,

for the Advanced version of the MS365 sensor, please check the device credentials, please enter the tenant id in the ID form, like 0000-0000-0000-0000...

The normal service status sensor works with the URL notation of the tenant id, the Service Advanced needs the ID form.

Hello - Had the hardest time getting the Office365 sensor working. Tenet ID, Client ID and Client Secret all matched with what we had in the portal. Turns out we needed the VALUE of the Secret ID. Not the Secret ID designation.

Click on this link and scroll to the bottom to see the real value to put in the "Credentials for Microsoft 365"

https://docs.microsoft.com/en-us/answers/questions/323082/problem-using-postman-to-call-rest-apis-34error-de.html

Hello, I'm getting this error: The request has failed. Request failed: HTTP request was not successful: 500: Internal Server Error

The error is random. Sometimes it shows up, sometimes the sensor is working fine.

any idea why this is happening?

Hello,

there are no known general issues with this sensor type. If you consistently experience issues, please contact support@paessler.com and include screenshots.

After having initially setup this sensor in July, working without fault until now - I'm now getting HTTP request was not successful: 403: Forbidden.

Quite frustrating, any reason for this? The client secret has not expired, I've tried re-authorising the app too. No dice.

A search of the forum doesn't show 403: Forbidden for this sensor.

I've got the same problem as James Mitchell above

Hello.

Regarding the 403 issue, please also update to PRTG 73 because we recently changed the sensors in order to use the new APU. As of now, this stable release has to be installed manually, please open Setup / Auto-Update and check for the latest version manually.

Arne Seifert, update to PRTG 73 does not solve the problem. Probablement, it's a compatibility issue between PRTG et Microsoft 365. Due to recent changes Microsoft for security. We all hope for Paessler :)

I have updated to PRTG Network Monitor 21.4.73.1656 x64 and I'm still getting the 403 issue.

As above issue was happening for me also, but the new update 21.4.73.1656+ for PRTG worked fine, after I created the new Microsoft Graph API permissions as per the KB article - https://helpdesk.paessler.com/en/support/solutions/articles/76000063073-how-do-i-obtain-credentials-and-set-permissions-for-the-microsoft-365-sensors

Happens for me, too. Please provide a fix/solution... thank you!

If you are already at the new PRTG 73 is necessary, please set the rights for ServiceHealth.Read.All in Azure, according to our updated article.