Office 365 Service Health Status

After following the solution from @christopher.t.jones123 the data is now showing with 0 value (service interruption) however, upon checking the Microsoft Service Health Dashboard, it does not match as some are showing healthy in Service Health but Critical in the SAM Template (Sharepoint Online, OneDrive for Business, Office Online and Dynamics 365). Is this happening as well on other thwack users having this template? if yes, is there an issue on the template or Microsoft changes the way we need to poll information in service health? what is the possible solution or workaround? Thanks :)

mat12 can you post a screenshot of the differences between the Microsoft Service Health Dashboard and the SAM template, I just ran a test in my environment using the same template, and everything I'm seeing lines up with what is returned. There might be some tweaks that need to be made to align with what Microsoft Service is saying is "healthy" if that change is necessary then it would have to be in this portion of the script.

if ($Status.status -match "ServiceOperational") {$Stat = 99}
if ($Status.status -match "FalsePositive") {$Stat = 6}
if ($Status.status -match "ExtendedRecovery") {$Stat = 3}
if ($Status.status -match "InformationUnavailable") {$Stat = 8}
if ($Status.status -match "PIRPublished") {$Stat = 7}
if ($Status.status -match "RestoringService") {$Stat = 2}
if ($Status.status -match "ServiceDegradation") {$Stat = 1}
if ($Status.status -match "ServiceInterruption") {$Stat = 0}
if ($Status.status -match "Investigating") {$Stat = 4}
if ($Status.status -match "ServiceRestored") {$Stat = 5}

Hi christopher.t.jones123, here is the comparison which shows critical with value 0 for statistics but Healthy in Service Health Dashboard in Microsoft.

Kindly let me know we have a workaround to fix this. :) thanks in advance!

mat12, I think I see what's going on but it would require some testing. What I believe is going on is that its returning a value that is not recognized and setting it to zero. in order to be sure we need to see what is being returned for $Status.status. Are you able to run the script locally on the polling engine and see what that statistic is?

Hi christopher.t.jones123, here is the result of the powershell script after running it directly on the Solarwinds Poller Server. I noticed that for others, they are showing correct statistics and message but for those critical showing in SAM template but Healthy in Service Health, they return "0" statistics instead of the correct value of UP or Healthy (99 or 6)

Thanks in advance! 

mat12, when you open the script up in ISE and run it, can you just have it return $Status.status to see the raw value its returning?

Hi christopher.t.jones123, no value is returning, only 0 for those showing critical but healthy in Microsoft service health website (example sharepoint online and officeonline). But for those with correct status, it is showing the message (example Teams):

Thanks in advance!

Kudos to christopher.t.jones123 in identifying the real value we are getting from Microsoft.
Running the script manually via Powershell ISE and run the $Status.status command, we get the "PostIncidentReviewPublished" status from Microsoft.

Adding the below script fixed the issue:

if ($Status.status -match "PostIncidentReviewPublished") {$Stat = 98}

Here is the updated status from Microsoft links:

• https://docs.microsoft.com/en-us/microsoft-365/enterprise/view-service-health?view=o365-worldwide
• https://docs.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/service-health-and-continuity

Hope this helps!

Kudos to christopher.t.jones123 in identifying the real value we are getting from Microsoft.
Running the script manually via Powershell ISE and run the $Status.status command, we get the "PostIncidentReviewPublished" status from Microsoft.

Adding the below script fixed the issue:

if ($Status.status -match "PostIncidentReviewPublished") {$Stat = 98}

Here is the updated status from Microsoft links:

• https://docs.microsoft.com/en-us/microsoft-365/enterprise/view-service-health?view=o365-worldwide
• https://docs.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/service-health-and-continuity

Hope this helps!

Greetings.  I have run into this same issue but I am a bit confused at what was added to the PS script to fix it.  I added the $stat=[int]$stat to the script and it works but I am stuck at it returning the 0.  I tried adding the f ($Status.status -match "PostIncidentReviewPublished") {$Stat = 98} to the script and it still returns 0.  What am I missing here?  Thanks!

martian_monster, run the script in PowerShell ISE from the polling engine conducting the polling, once it is completed in the terminal run $Status.Status, it'll then output the returned status from Microsoft, you need to ensure there is a match for it in the block that takes the String data and converts it to an integer. If the string returned is ServiceInteruption then 0 would be an accurate integer because that's what the conversion is calling for. 

I am a huge novice in PS. I tried running it but it did not like something.  We patched this server over the weekend and that seemed to be part of this issue 2016 KB5008207.  Adding $stat to the script seemed to fix it but all I can get as a return is 0.  I think I am more confused now than when I started.  Thanks for your help!!!

martian_monster, you're probably missing what you would've added as script arguments or credentials to it when running it in ISE, that's something I see forgotten quite often. make sure whoever it is referencing a credential or script argument you are filling in the appropriate data and try it again.