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

How do I set permissions for the Office 365 Management APIs?

Votes:

0

Your Vote:

Up

Down

I want to use the Microsoft 365 Service Status sensor or the Microsoft 365 Service Status Advanced sensor. I know that these sensors require permissions for the Office 365 Management APIs, but I don't know how to set the respective rights.

What do I have to do?

api azure azure-ad microsoft-365 office-365 permissions prtg

Created on Aug 18, 2020 8:17:13 AM by  Maike Guba [Paessler Support]

Last change on Aug 18, 2020 9:03:07 AM by  Maike Guba [Paessler Support]



18 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down


Important notice: This article is outdated. Please see our step-by-step guide: How do I obtain credentials and set permissions for the Microsoft 365 sensors?

Permissions for the Office 365 Management APIs

For the Microsoft 365 Service Status sensor or the Microsoft 365 Service Status Advanced sensor to work properly, your PRTG installation needs sufficient rights to query data like the subscribed services or the current status of services from the Office 365 Management APIs.

Set the following permission:

  • API / Permissions name: Office 365 Management API.ServiceHealth.Read
  • Type: Application

Office 365
Click to enlarge.

For more detailed information, see https://docs.microsoft.com/en-us/office/office-365-management-api/office-365-service-communications-api-reference.

More

Created on Aug 18, 2020 8:25:13 AM by  Maike Guba [Paessler Support]

Last change on Oct 20, 2020 10:37:02 AM by  Maike Guba [Paessler Support]



Votes:

2

Your Vote:

Up

Down

The detailed information does not show how to grant access.

Created on Aug 25, 2020 3:06:10 PM by  youngr13 (30) 1



Votes:

0

Your Vote:

Up

Down

Created on Aug 26, 2020 7:54:30 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

The link does not says anything about the Office 365 Management API: https://kb.paessler.com/en/topic/88462-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

Created on Aug 27, 2020 3:33:32 AM by  cschulenburg (0) 1



Votes:

0

Your Vote:

Up

Down

Hi Christian,

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

Created on Aug 27, 2020 6:59:15 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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

Created on Aug 28, 2020 3:50:47 AM by  cschulenburg (0) 1

Last change on Aug 28, 2020 7:57:43 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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.

Created on Aug 28, 2020 8:00:07 AM by  Moritz Heller [Paessler Support]

Last change on Aug 28, 2020 8:00:17 AM by  Moritz Heller [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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

Created on Oct 7, 2020 6:51:08 PM by  mbaybarsk (30) 1



Votes:

0

Your Vote:

Up

Down

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.

Created on Oct 8, 2020 1:27:50 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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?

Created on Nov 9, 2020 8:25:08 AM by  sharbatlyfruit (0) 1



Votes:

0

Your Vote:

Up

Down

Hello sharbatlyfruit,

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

Created on Nov 9, 2020 1:52:03 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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?

Created on Nov 11, 2020 7:34:57 PM by  ARLMaitland (0)



Votes:

0

Your Vote:

Up

Down

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.) :(

Created on Dec 10, 2020 12:23:25 AM by  Matthew Tucker (0) 1

Last change on Dec 10, 2020 10:34:10 PM by  Matthew Tucker (0) 1



Votes:

0

Your Vote:

Up

Down

Same Problem here.

Created on Feb 5, 2021 6:57:03 AM by  Rixius (0) 1



Votes:

0

Your Vote:

Up

Down

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.

Created on Feb 5, 2021 5:26:10 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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

Created on Jun 9, 2021 3:22:45 PM by  idivitj (5) 1



Votes:

0

Your Vote:

Up

Down

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?

Created on Aug 18, 2021 6:21:52 AM by  BezirkSchwaben (0)



Votes:

0

Your Vote:

Up

Down

Hello,

there are no known general issues with this sensor type. If you consistently experience issues, please contact [email protected] and include screenshots.

Created on Aug 23, 2021 9:38:21 AM by  Arne Seifert [Paessler Support]



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.