Monitor Tenant Health and Network Readiness
Use Service Health dashboards, configure notifications, review network connectivity insights, and manage software updates — before your users notice problems.
Why proactive monitoring matters at scale
At 20,000 users, you can’t wait for complaints to tell you something’s broken.
Imagine managing a motorway system. You don’t wait for a pile-up to find out there’s black ice — you have sensors, cameras, and alerts. Microsoft 365 gives you the same tools: Service Health for outage detection, Network Insights for connectivity analysis, and update channels for controlled software rollouts.
The difference between a good admin and a great admin? Great admins know about problems before users do.
Service Health: Your early warning system
The Service Health dashboard shows the real-time status of every M365 service in your tenant.
What you see on the dashboard
| Category | What It Shows | Action Required |
|---|---|---|
| Service incidents | Active issues affecting your tenant | Monitor updates, communicate to users |
| Advisories | Performance degradation or known issues | Assess impact, plan workarounds |
| Planned maintenance | Scheduled maintenance windows | Notify affected teams in advance |
| Issue history | Resolved incidents (last 30 days) | Review for patterns, post-incident analysis |
Configuring notifications
Priya can’t watch the dashboard 24/7 across six time zones. She configures:
-
Email notifications — Health > Service health > Preferences > Email
- Send to a distribution list:
m365-ops@globalreach.com - Include service incidents AND advisories
- Configure for specific services (Exchange, Teams, SharePoint — the critical ones)
- Send to a distribution list:
-
Message Center notifications — separate from Service Health
- Alerts about upcoming changes, feature retirements, action required
- Priya assigns a Message Center reader role to her regional admins
Exam tip: Service Health vs Message Center
The exam distinguishes between these two:
- Service Health = current problems (incidents, advisories, maintenance)
- Message Center = upcoming changes (new features, retirements, required actions)
A common exam question pattern: “Where should Priya look to find out why Teams meetings are dropping?” → Service Health. “Where should Priya look to find out about a new Teams feature rolling out next month?” → Message Center.
Network connectivity insights
The Network connectivity page analyses how well your office locations connect to Microsoft 365 service endpoints.
How it works
- Office locations are detected — from Entra sign-in data or manually added
- Network assessments run — measuring latency, bandwidth, and routing to M365 service front doors
- A score is calculated — 0 to 100, benchmarked against similar organisations
- Recommendations appear — specific issues like DNS resolution delays, proxy interference, or suboptimal routing
What the score means
| Score Range | Status | Typical Cause |
|---|---|---|
| 80-100 | Excellent | Direct internet breakout, local DNS, optimal routing |
| 60-79 | Acceptable | Minor proxy overhead, regional DNS |
| Below 60 | Needs attention | Backhauled traffic, remote DNS, proxy inspection on M365 traffic |
Priya’s network challenge
GlobalReach has offices in Singapore, Sydney, London, Tokyo, Mumbai, and New York. The Sydney office scores 45/100. Investigation reveals:
- All internet traffic is backhauled to Singapore through a central firewall
- DNS resolution happens in Singapore, not Sydney
- M365 traffic is routed through a proxy that performs SSL inspection
The fix: implement local internet breakout in Sydney for M365 traffic, following Microsoft’s network connectivity principles (direct egress, local DNS, bypass proxy for trusted M365 endpoints).
Deep dive: Microsoft's network connectivity principles
Microsoft recommends three principles for optimal M365 connectivity:
- Differentiate M365 traffic — classify endpoints as Optimize, Allow, Default
- Optimize locally — direct internet breakout at each office, no backhauling
- Avoid network hairpins — don’t route M365 traffic through central inspection points
The Optimize category includes Exchange, SharePoint, and Teams endpoints that are most sensitive to latency. These should bypass proxies entirely. The exam may present scenarios where you need to identify which approach fixes a connectivity issue.
Software updates management
The Software updates page in the admin center shows Microsoft 365 Apps update status across your organisation.
Update channels explained
| Feature | Current Channel | Monthly Enterprise | Semi-Annual Enterprise |
|---|---|---|---|
| Update frequency | Multiple times per month | Once per month (2nd Tuesday) | Twice per year (Jan, Jul) |
| Feature updates | As soon as ready | Monthly | Every 6 months |
| Security updates | As soon as ready | Monthly (2nd Tuesday) | Monthly (2nd Tuesday) |
| Best for | Users who want latest features | Organisations wanting predictability | Regulated environments needing stability |
| Support duration | Until next release | 2 months | 14 months (changing to ~3 months from July 2026) |
| Exam relevance | Know it's the default | Most common enterprise choice | Know when this is appropriate |
What the dashboard shows
- Devices by update channel — how many devices are on each channel
- Update compliance — percentage of devices running the latest version for their channel
- Devices behind — count of devices that haven’t updated within the expected window
- Servicing profiles — admin-defined update schedules with rollout waves
Marcus uses Monthly Enterprise Channel for Oakwood Financial — predictable monthly updates on Patch Tuesday, with a one-week rollout window and automatic deferral for devices that are offline.
Exam tip: Update channels and servicing profiles
The exam tests whether you can choose the right update channel for a scenario:
- Startup wanting latest features → Current Channel
- Enterprise wanting monthly predictability → Monthly Enterprise Channel
- Bank requiring 6-month validation cycles → Semi-Annual Enterprise Channel
Servicing profiles let you create phased rollouts — e.g., IT team gets updates in week 1, finance in week 2, everyone else in week 3. This is configured in the M365 admin center, not Intune.
Key concepts to remember
Knowledge check
Priya notices that GlobalReach's Sydney office reports slow Teams call quality and SharePoint uploads. The network connectivity score for that office is 42/100. Network analysis shows all traffic is backhauled to the Singapore datacenter. What should Priya recommend?
Marcus receives a report that 30% of Oakwood Financial's devices are running an outdated version of Microsoft 365 Apps. He wants monthly, predictable updates with a phased rollout (IT team first, then general staff). Which approach should he use?
🎬 Video coming soon
Next up: Adoption Tracking and Microsoft 365 Backup — proving ROI to leadership and protecting your tenant’s data from the unexpected.