GitHub outage on April 23, 2026

Read more >

Introducing StatusGator’s Accessibility Conformance Report (VPAT)

Read more >

StatusGator logo
Schedule a Demo
StatusGator logo
Use cases

IT Teams

Stay informed of outages and reduce tickets

DevOps

One status page for all your providers

Features designed specifically for K12

Advanced features designed for enterprise

Impress clients with proactive monitoring

Analyze and compare peer performance

Monitor dependencies to prevent revenue loss

Create and manage custom status pages for your product

Features

Status page

A status page with service, website, and custom monitors built-in

Status aggregation

Aggregate the status of all vendors to a single page

Monitor all your cloud services from a single dashboard

Monitor your website with uptime monitoring built-in

Monitor network connectivity

Control the status of custom monitors manually with incidents

Get notified of disruptions before they become public

Pricing

Business

From startup to enterprise and everything in between

Education

Special plans and discounts for K12 and higher ed

Integrations

Incident Management

Better Uptime
FireHydrant
Opsgenie
PagerDuty

Notifications

Private Status

AT&T status
AWS status
Azure status
Microsoft 365 status
Zendesk status

Status Pages

Atlassian Statuspage
StatusHub

Advanced

Sign In Sign Up

Improved Microsoft 365 private status integration

Keeping track of your Microsoft 365 services just got easier.

We’ve rolled out an update to the Microsoft 365 integration that removes manual setup and improves visibility. All services in your account can now automatically appear as components, so you can monitor them right away.

What changed

Before this update, you had to go into the Monitors tab and manually enable each Microsoft 365 service you wanted to track. This added extra steps and made setup slower, especially if you were managing multiple services.

You also had to manage multiple individual services separately, which made your setup more fragmented.

What’s new

All your Microsoft 365 services now show up as components automatically after you connect the integration. There’s no need to configure them one by one.

You now get a more unified setup, where Microsoft 365 is treated as a single service with multiple components underneath it.

You can also monitor services specific to your own Microsoft 365 account, including ones that may not be part of the standard public list.

Why it matters

Less manual work
You don’t need to enable each service individually anymore.

Simpler structure
Instead of managing multiple separate services, everything is organized under one Microsoft 365 service with components.

Better visibility
Services appear as components, making it easier to understand their status at a glance.

Faster response
When issues happen, affected services are clearer and easier to communicate.

More control with filtering
You can now filter by components to focus only on the services that matter to you and ignore less relevant ones.

More complete monitoring
You can include services that are unique to your Microsoft 365 environment.

Getting started

If you already use the Microsoft 365 integration, you have two options to get the new setup:

Remove and reconnect the integration
This will immediately switch you to the new single service with components configuration.

Wait for automatic migration
We’ll convert existing integrations to the new structure over the next month.

If you’re setting it up for the first time, just connect your account and your services will appear as components right away.

Note

We still recommend keeping the public Microsoft 365 service enabled so you can benefit from Early Warning Signals and get notified about issues before they impact your environment.

If you need help or have any questions, feel free to reach out at hi@statusgator.com.

Share this

Photo of author

Valeria Kurolapova

Valeria Kurolapova is the Senior Product Designer and UX Manager at StatusGator. She manages product design initiatives, focusing on improving user experience.