Skip to content

Based off of an existing set of script that end up being used as Azure Automation Runbooks. This script was updated to connect to multiple M365 Subscriptions, resolve the default domain of the M365 Tenant; connect to the the Service Health Dashboard and Message centre and send the data to Log Analytics for dashboarding and alerting.

Notifications You must be signed in to change notification settings

bzabber/M365Monitoring

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

65 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

M365 Monitoring

The M365Monitoring module has two cmdlets: Get-M365ServiceHealth is used to query the M365 Service Health API (O365 Service Communications API). The output can be then pipelined to something else or simple used dump the status to the console. You must provide the M365 TenantID, ClientID (AppID) and Client Secret.

Get-M365Messages.ps1 is used to query the M365 Message Center API found at https://manage.office.com/api/v1.0/contoso.com/ServiceComms/Messages. Get-M365ServiceHealth.ps1 is used to query the M365 Service Health API found at https://manage.office.com/api/v1.0/contoso.com/ServiceComms/CurrentStatus.

The M365Monitoring module must be located in your module path in a folder called M365Monitoring.

You must provide the M365 TenantID, ClientID (AppID) and Client Secret.

Use example: get-M365Messages.ps1 -TenantID -ClientID -ClientSecret get-M365ServiceHealth.ps1 -TenantID -ClientID -ClientSecret

About

Based off of an existing set of script that end up being used as Azure Automation Runbooks. This script was updated to connect to multiple M365 Subscriptions, resolve the default domain of the M365 Tenant; connect to the the Service Health Dashboard and Message centre and send the data to Log Analytics for dashboarding and alerting.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published