Office 365 Service Health Status

So we have been using the Office 365 Service Health Status and it was been working great up until a few days ago. On the application status page we are getting this error

"PowerShell script error. Scripting Error: Script does not contain the expected parameters or is improperly formatted. 'Statistic' missing."

however, when you go in and run the powershell script on the edit application monitor page. It gets results back. Has anyone else seen this behavior? or have an idea on how to fix it?

Thank you.

  • Anyone having issues today with this Service Health Monitor?
    I am getting the unknown and critical status with no Message with the below error:

    Exception was caught: The remote server returned an error: (403) Forbidden.


  • Also seeing the same issue with the 403 errors since 1/3.

  • and , 403 errors indicate some sort of permission issue. Either the account that you are using no longer has the ability hit the endpoint, or the endpoint no longer accepts those types of requests.

    Is the account you are using a registered app with the appropriate permissions?

    I no longer have a Demo instance to test a lot of this stuff out with, I'm working on standing one up.

    My recommendation would be to run the script in Powershell ISE from the Polling engine it's assigned to and see if it provides any additional errors that might point to the permission you might be missing. 

  • I suspect that the Request URL might have changed, if it was not permissions. But - I have noticed that things change unpredictably in Azure. 

  • Yeah I need to get around to testing via ISE still.  Noone has really noticed so far so... lol  But since other people were having the same issued starting at the same time it seemed likely something changed on that side of things and not likely specific to our tenant.

  • The Office 365 Service Communications API has been retired with Service Health information now available in the Microsoft Graph.

    Just looking at what's required to update the script to call Graph instead.

  • Hi ,
    Thanks for the information. Same thought I have when we first encounter this issue as when i run the powershell script manually i get the same error the first time.

    However, I am not really familiar on what to update with this template connecting to M365 as I can't find an updated information about this.

    Even the Solarwinds built-in API Poller templates like 'Microsoft 365 Exchange Online' is not working same day this template have an issue. I hope Solarwinds team can provide an updated working template for everyone to use like this one or hoping someone can come up with a fix.

  • Hi ,

    Yes I was able to run the powershell manually as a test and got the same error showing on the webconsole at first "Exception was caught: The remote server returned an error: (403) Forbidden.". After running the test again, now I am getting this error: "Warning: Exception was caught: Unable to connect to the remote server".

    There is no changes on the credential and permission used so as per , Office 365 Service Communications API has been retired.

    Now we are running days without this monitoring and hopefully waiting from Solarwinds Team or someone in thwack that can help fix this service health cloud monitoring that up to now, no built-in template.

  • , what's the URL it's trying to hit? i don't have a copy of this application monitor so I cannot look myself. Additionally, I would suggest looking at this API builder for Graph, if the endpoint did indeed change this would be the way to find out the new endpoint to update to.

  • The scope/ request URL has most likely change from something like
    to something like

    Graph documentation feels a lot like a trail of breadcrumbs. Anyone familiar enough with Graph to comment further? IF you are using the new API poller this will stick out. Send a test request and see if you get : The remote name could not be resolved: ''

    I dug abit and the request URL might be this: 365 suite

    Here is a reference document:
    Get serviceHealth - Microsoft Graph v1.0 | Microsoft Docs:

    Good Luck, I am in the middle of five other things but will post when I get a chance. 


  • Looking through the Graph API "List healthOverviews" documentation, I've been able to rewrite the application script body to successfully get the Status and Messages. It's also actually removed the need to do the second messages API query as the Issues are included in full in the first status call.

    MS Documentation:

    Updated Graph API Script included here, use at your own risk. Let me know if you spot any issues!

    #Pass Credentials from Solarwinds
    Function SecureStringToString($value)
        [System.IntPtr] $bstr = [System.Runtime.InteropServices.Marshal]::SecureStringToBSTR($value);
    $c = Get-Credential -credential ${CREDENTIAL}
    [string] $username = $c.Username
    [string] $password = SecureStringToString $c.Password
    # Objects
    $service = $args[0]
    $tenantId = $args[1]
    $client_id = $username
    $client_secret = $password
    # Construct URI for OAuth Token
    $uri = "$tenantId/oauth2/v2.0/token"
    # Construct Body for OAuth Token
    $body = @{
        client_id     = $client_id
        scope         = ""
        client_secret = $client_secret
        grant_type    = "client_credentials"
    # Get OAuth 2.0 Token
    $tokenRequest = try {
        Invoke-RestMethod -Method Post -Uri $uri -ContentType "application/x-www-form-urlencoded" -Body $body -ErrorAction Stop
    catch [System.Net.WebException] {
        Write-Warning "Exception was caught: $($_.Exception.Message)"
    $token = $tokenRequest.access_token
    $o365status = try {
        Invoke-RestMethod -Method Get -Uri '$expand=issues' -ContentType "application/json" -Headers @{Authorization = "Bearer $token"} -ErrorAction Stop
    catch [System.Net.WebException] {
        Write-Warning "Exception was caught: $($_.Exception.Message)"
    $Status = $o365status.Value | ? {$_.Id -eq $Service}
    $IncidentIds = $Status.issues | Where-Object isResolved -eq $False
    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}
    #Write-host 'Statistic.Status: '$Stat
    #write-host 'Message.Status: '$Status.StatusDisplayname
    Write-host 'Statistic: '$Stat
    if ($Status.status -notlike "ServiceOperational") {
    $Result = foreach ($issue in $IncidentIds) {
    $Output = '<p>' + $issue.Status + ' - ID: ' + $issue.ID + ' - ' + $issue.ImpactDescription + '</p>'
    write-host 'Message: '$Result
    Else {
    write-host 'Message: '$Status.StatusDisplayname

  • Hi

    Thanks for providing this information.
    were you able to successfully get the correct output and running the powershell script manually?
    When i try to use your script, i was getting the same error as before using our own tenant credentials:

    I am getting this error: "Warning: Exception was caught: Unable to connect to the remote server".

Reply Children
  • The previous script was getting 401 Unauthorized and upon manual execution I discover a message noting the API had been replaced with the Graph API.

    Suspect you have issues getting out to the internet from that host. Is there a proxy that you need to go through?

  • Hi

    I already added and used the proxy we used on our previous template and i update yours but same issue occur.

    So on your manual execution test can you share what is showing on the result via powershell?
    Here is what i am getting when running manuall on powershell:

    II also confirmed that the website for is accessible on the machine i'm using.

    Thanks in advance! Slight smile

    P.S: hoping anyone can share if they were able to successfully used this new template?

  • Bump! anyone able to use template successfully without issues?

    I even used a machine with no proxy that can connect to the internet but same occur and got the below error:

    WARNING: Exception was caught: The remote server returned an error: (403) Forbidden.

    I also confirmed there is no changes on the " ServiceHealth.Read.All" for Application.

    Thanks in advance!