Tag: Office 365

Flow: Filter Array on Multiple Parameters Using and()

AlanPs1 Leave a comment

Back in part 8 – Call O365 Roadmap Web Service Weekly Digest you will see there is a Filter Array that I left alone at that time. This is because the scope of the blog post was to get a weekly digest of posts made by the Microsoft 365 Roadmap.

The expression within the Filter Array get’s you the last 7 days of updates and does no more.

This is great, unless of course you have no need to be viewing a specific category such as Windows or O365. Maybe you are an Office 365 Admin and would like to streamline the output by only sending those with category of O365. Or maybe you need to see all Security & Compliance updates along with O365 and the rest, so you would need to omit posts with category Windows Desktop.  Here are steps that you can take to modify the above Filter Array and why.

Consider this filter …

Read More

Call O365 Roadmap Web Service Weekly Digest – Part 8

AlanPs1 Leave a comment

The Microsoft 365 Roadmap can be an invaluable source of information at times, although staying on top of the hundreds and hundreds of information it has to offer can be overwhelming. I’ve seen it advised by some to export the data to excel and move it to Power BI. That works great, although the context of this blog series is to have key information alert you so that there is no need for you or your team to check of your own back. With the power of Microsoft Flow, we will capture the new entries on the RSS feed and we will then send a weekly digest email.

Here is a glimpse of what the email output will look like.

For the ID of 43977 featured here, please see this link.

As you can see, each title is a hyperlink and directs you to the Microsoft 365 Roadmap where you can see full information as below:

Read More

Call Microsoft Graph Organization Scope to Check Last AAD Connect Sync Time – Part 7

AlanPs1 Leave a comment

Within any organization who run a hybrid Office 365 setup, AAD Connect has a sync cycle of 30 minutes (default) and unless someone is on one of the sync servers or in the admin portal and spots an error, there is a possibility that Dir sync (deprecated technology but still can be used to refer to AAD Connect) could have failed and go unnoticed for some time.

In terms of generating an alert, there is more than one way to achieve this using a PowerShell job, or a task on the server using task scheduler that runs PowerShell, but for some organisations these things are not permitted or possible, so in steps Flow & Microsoft Graph.

Firstly, I’d advise popping over to the Microsoft Graph Explorer and authenticating with your admin account.

Check the box to Consent on behalf of your organization.

We are now going to access the organization resource type and look at at 2 properties, onPremisesSyncEnabled & onPremisesLastSyncDateTime.

Read More

Harness the Twitter API via flow to capture new tweets from @MSFT365Status – Part 6

AlanPs1 Leave a comment

In this post, we will now add an additional layer of visibility with the Office 365 Alerts Mailbox by monitoring tweets from @MSFT365Status.

Microsoft 365 Status only tweets relating to Service Incidents so having visability of these tweets within Outlook comes with many benefits.

Firstly you will need a Twitter account and to have created a connection for that account within Flow. We will use this to authenticate only, after that the email only contains Tweets from Microsoft 365 Status.

Here is the Flow:

It could not be simpler. There are templates for this also but I tend to start from blank and add When a new tweet is posted trigger.

Read More

Call Office 365 Service Communications API and Return a Daily Summary of Message Center Notices – Part 5

AlanPs1 Leave a comment

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

  1. Pages:
  2. 1
  3. 2
  4. 3