Category: Flow

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 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 O365 Notices – Daily Update (or similar).

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

We will set it to run daily and a nice enhancement is also to set a start time. You can play around with this to suit but in my environment, having an email drop through like this first thing in the morning means that the engineer who does the daily checks knows about any new notices. They can then decide whether Change Management or the Service Desk need to be made aware of anything on the back of the communication.

Read More

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.

Read More

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 returned in FQDN Format.

The full unformated worldwide list can be found here in JSON format & here in CSV format.

As part of the article, it explains how you can access the changes, essentially the newest updates since the month before. You can see the data here.

The URI looks like this – https://endpoints.office.com/changes/Worldwide/2018102900?singleVersion&clientRequestId=b10c5ed1-bad1-445f-b386-b919946339a7

This can be changed as and when a new version is published by Microsoft, but of course the output via the browser is in JSON format. So let's walk through how I have captured the new FQDNs and emailed them to a shared mailbox. I did this with some help from Paul Andrew as he had detailed a good deal of the process at this blog.

Let's begin …

Firstly, we will need to use a SharePoint list in order to compare old and new versions. It will look like the next image:

Go to SharePoint and click the Lists menu item, then click New, and select List to create a new list.

Read More