Office 365 Service Health using Office 365 Service Communications API

Hi Team, i am trying to get the benefit out of this template as our customer is looking for a way to monitor Office 365 service using SolarWinds.

I am very green to use SAM templates. Reques your support here.

As per the instruction given in the article, we have created an application for SolarWinds in Azure. Now the questions running in my mind to take this further are:

1. Where do i need to add my client id, client secret as credentials in SolarWinds, is it under manage API credentials (if so what type i should choose, is it API Key, basic authorization. there are a lot of types i can see while adding..), please help. 

2. In the template, under each component monitor for service, there is another option to select "Credential for monitoring" - what credential i should use". i cannot see the API credential that i added in the drop down-- so i suspect i added the credentials in a wrong place - please correct me.

3. The biggest concern is once the template is good, against what device i should assign this template to test- this leaves me blank. Please help.

We had this working just fine months ago.  When I looked recently, everything is failing and if I test an individual component, I get back 
Exception was caught: The remote server returned an error: (500) Internal Server Error.

Have gone through the credentials in Azure AD and Solarwinds and verified everything, but not working. Where do I look now?

There are many potential pitfalls that one may be faced with in the process of developing their own mobile application. One of the most common mistakes that companies make is hiring third party developers and also they can check outsourced document management and digitization to get their best services. Third party developers set up the SDK, but they do not actually develop any code, they only provide the actual code that will be used in the app.

After running the script manually, we were able to determine that the line 'if ($Status.status -match "PIRPublished") {$Stat = 7}' was the issue.  It seem Microsoft has updated this status to 'PostIncidentReviewPublished' instead.  Once we updated that, then we were able to get a correct status reading.  Also, some of the items are outdated (OSub, DynamicCRM).  We saw that no status would show on them, but after reviewing our O365 admin center health page, we noticed those were not there.  This module might need some minor updating.  But thanks for it nevertheless!

This is actually the error I'm getting as well.  Supposedly due to a missing powershell extension but haven't been able to test this.  Anyone else get past this?