{"id":110966,"date":"2018-09-05T05:02:11","date_gmt":"2018-09-05T12:02:11","guid":{"rendered":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-automate\/get-office365-health-notices-using-microsoft-flow\/"},"modified":"2025-06-11T08:07:06","modified_gmt":"2025-06-11T15:07:06","slug":"get-office365-health-notices-using-microsoft-flow","status":"publish","type":"post","link":"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/power-automate\/get-office365-health-notices-using-microsoft-flow\/","title":{"rendered":"Advanced | Flow of The Week: Retrieving Office 365 Message Center and Service Health Notices using Microsoft Flow"},"content":{"rendered":"

Hello Flow Fans!<\/p>\n

This weeks post comes from Antonio Maio from Protiviti, inc.<\/p>\n

Antonio Maio is an enterprise architect with over 20 years of experience in enterprise application architecture, information security, cybersecurity practices and systems, software development and team leadership. Antonio is an Associate Director and Senior Enterprise Architect with Protiviti. Based in Canada, he has been awarded a Microsoft Most Valuable Professional (MVP) award for 7 consecutive years, from 2012 to 2018, specializing in Microsoft SharePoint Server, Office 365 and Office Services. His background includes implementing large scale SharePoint and Office 365 environments, information security technologies, and information governance best practices. His experience with Microsoft SharePoint and Office 365 extends over the last 12 years. Be sure to Follow him on Twitter<\/a> and check out his blog www.trustsharepoint.com<\/a>\u00a0<\/em><\/p>\n

To automate critical business processes in Office 365 using Microsoft Flow, we typically need to call cloud-based services in order to retrieve data.\u00a0 Calling these services often requires us to use the HTTP connector and action, and as a result, provide our TenantID, along with an App\u2019s ClientID and SecretID in the Flow.\u00a0 This blog post will provide a detailed walkthrough of configuring these required parameters when calling cloud services using the HTTP connector.\u00a0 We\u2019ll use a recently released Flow template as an example, which retrieves data from the Office 365 Message Center and Service Health dashboards.<\/p>\n

Using the Office 365 Message Center<\/strong><\/p>\n

A common recommended strategy for managing and maintaining an enterprise-class Office 365 environment is to designate a \u201cservice owner\u201d for your corporate Office 365 tenant.\u00a0 The service owner\u2019s role usually includes staying up to date with changes and new capabilities that are coming to Office 365, and being proactive about determining the best way to roll out those changes to the organization\u2019s user community.\u00a0 One of the best tools available to help service owners stay up to date with Office 365 features and changes is the Office 365 Message Center.\u00a0 The Office 365 Message Center is a dashboard available in the Office 365 Admin Center (Health > Message Center) which hosts messages from Microsoft about new features, planned changes to features or service issues within the Office 365 environment.<\/p>\n

There are several ways to stay up to date with messages posted to the Message Center.\u00a0 For example, the Message Center allows you to get push notifications from the Office 365 Admin App, or in the Message Center you can select to have a weekly email with posted announcements sent to up to 2 users or to a group.<\/p>\n

A great way to have Office 365 Message Center announcements sent directly to your inbox, in a weekly summary format, and to even customize the list that\u2019s sent, is to use Microsoft Flow.\u00a0 The Microsoft Flow team has recently released a new Flow template called \u201cEmail me a weekly summary of Office 365 Message Center notices\u201d that gets you started.\u00a0 Although this template works very similarly to the built in Message Center feature of sending a weekly digest email, using Flow has the advantage of allowing you to customize the weekly email to either send it to more than 2 people (without using a Group) or to highlighting updates or service outages related to only specific services you might be interested in.\u00a0 For example, you could send emails that alert your Exchange team to Exchange Online specific updates, or your SharePoint team to SharePoint Online specific updates, and so on.\u00a0 You could even automatically register service outages with your internal governance and security tools for alerting and auditing purposes.<\/p>\n

\u00a0<\/p>\n

<\/p>\n

This template will actually send a weekly summary email containing all Office 365 Message Center notices and all Service Health issues posted in the last week to your Office 365 tenant.<\/p>\n

It relies on two connectors (Office 365 Outlook and Office 365 Users) and calls to the Office 365 Service Communications API. \u00a0So once those two connections are established, the template is actually fairly easy to setup and use.\u00a0 It does however require the user to fill out three parameters that might be confusing to some, so we\u2019ll walk through how those parameters are configured here so that you can quickly get up and running with this Flow template.<\/p>\n

When you first create the template, it looks like this:<\/p>\n

<\/p>\n

Notice, here are those three variables right out the gate that you need to provide: TenantID, ClientID, and SecretID.\u00a0<\/p>\n

Provide the TenantID<\/strong><\/p>\n

First you need to provide your Office 365 TenantID.\u00a0 This is not your tenant name or your domain.\u00a0 This is a globally unique identifier (GUID) that uniquely identifies your Office 365 tenant.\u00a0 There\u2019s 2 ways to retrieve your Office 365 tenant ID:<\/p>\n

    \n
  1. From the Azure Active Directory Admin Console<\/li>\n<\/ol>\n