Note to self

The Office 365 Service Health scripts have grown from a simple script to a collections of scripts with central configuration files. This can make it look quite complicated but its straight forward. pre-reqs: An Azure App with Service Health (Office 365 management API), Reports.Read.All (Graph API) and Organization.Read.All (Graph API) A web service to host the html output a task scheduler to run the command lines on a regular basis. Azure AD App Lee Ford (others great bloggers also available!) has a great step-by-step article on how to create an app, so theres no point in reinventing the wheel!: https://www.lee-ford.co.uk/get-latest-office-365-service-status-with-flow-or-powershell/ Its also worth looking at consuming the App in Flow and pushing to teams - having an 'in-cloud' monitoring solution can help pinpoint local issue (ie proxy, internet access). Similarly having an on-premises solution allows you to test from a user perspective and also works during teams/flow

I've been busy working on the office 365 Service Health script and i've added some new features. Its actually becomming a bit of a handful, so I'll need to cut back or split out the functionality to keep it relevant. Azure App will require the following permissions: Graph API : Organization.Read.All (licences) Graph API: Reports.Read.All (Usage reports) Office 365 Management API: ServiceHealth.Read First though - New Features! Config files - I'm moving most values to configuration files. This allows for multiple tenants, test configurations etc. ProfileBuilder.ps1 - this ps1 script will update an existing config file with the new settings Monitor.ps1 - email alerting on new and closed incidents Office 365 Usage Reports (7day) - add in usage report permissions to your azure app graph API permissions and you can download the usage reports in CSV Dashboard - The animated gif below has a quick flick through the dashboard page. New features include Office 36