Call Office 365 Service Communications API and Return an Hourly Summary of Service Health Notices – Part 4

In part 4, we will now look to create the flow that will populate the nested folder called Live Updates. More information on the folder structure in part 1.

We will base this post mostly around part 3 as they are very similar in what they do but with a few subtle changes and enhancements.

Please familiarise yourself with part 3 as this post will only discuss the changes required in order to achieve an hourly live update summary.

On the My Flows page, select the Flow you have created from part 3 and choose Save as, now rename the flow to Live Incidents – Hourly Update (or similar).

The first modification we will make will be at the beginning to the Recurrence trigger.

This will run hourly and it can help by reminding you of the issues that are live and may be affecting your tenant.

If you work in a 24 hour environment, then this should work well for you. but what if your company is Monday to Friday business hours, say 8am to 5pm. Do we really need a summary of live service incidents on a Saturday or Sunday or at midnight?

I would suggest not, so right after the Recurrence trigger but before we initialise variable TenantID, ClientID & SecretID we have the option to stop the flow from running if out with the time constraints. I have written a separate blog on this called So you just want Flow running in business hours – 8am to 5pm so you may want to integrate these steps for this one.

We then move on through the flow and we request the token and the Service Health data in the same way but we make changes when we come to filter that data.

First thing to do would be to delete Filter Array 2 as it is no longer required

We then change the expression in Filter Array as below.

@and(equals(item()?[‘MessageType’], ‘Incident’), equals(item()?[‘EndTime’], Null))

EDIT: 6th February 2019 – https://www.alanps1.io/power-platform/flow/flow-so-where-has-edit-in-advanced-mode-gone-on-condition-actions/

And that’s pretty much it, everything else can stay the same although, you may want to put some consideration to the data that is used to populate the HTML table.

As this is a live update, you may want to see it’s start time, when it was updated etc.

You can easily change the table data by change the Dynamic Content to suit.

My Output at present looks like this but it is open to interpretation:

Alan
Part 5 >>>

Related Post

PowerShell Office 365: SMTP Email Sent with PowerS... In this example, I have an extremely simple function called MyCode. The purpose of the function is only to demonstrate us taking any PowerShell output...
New Emails between 10am & 11am move to Subfol... Using Microsoft Outlook. If you have a need to receive an email, then to file it in a sub-folder based on 2 time parameters this method should do the ...
Call O365 Endpoints Web Service and Return the Lat... Now we will look into an automated process that allows us to call the Office 365 IP Address and URL Web service and to have the news Endpoints returne...
Call Office 365 Service Communications API and Ret... In part 5, we will now look to create the flow that will populate the nested folder called O365 Notices. More information on the folder structure in p...