Problem overview.
The challenge this resource is designed to solve.
Microsoft Exchange powers business-critical email communications. Service disruptions can cause missed emails and productivity losses. This policy ensures Exchange services remain operational by automatically restarting stopped instances and notifying your team immediately.
About this resource.
What it does and how it fits into your workflow.
This monitoring policy targets devices tagged with “Exchange” and checks the status of Microsoft Exchange services. If the service stops or fails to start, it automatically triggers a restart and sends a real-time alert. This reduces downtime and ensures uninterrupted email functionality for your users.
| Monitor name | Monitor type |
|---|---|
| Exchange CPU Usage (CPUUsed monitor) | Exchange CPU Usage (CPUUsed monitor) |
| Exchange Information Store (Service monitor) | Exchange Information Store (Service monitor) |
| Exchange Transport (Service monitor) | Exchange Transport (Service monitor) |
| Exchange Frontend Transport (Service monitor) | Exchange Frontend Transport (Service monitor) |
| Exchange Mailbox Transport Submission (Service monitor) | Exchange Mailbox Transport Submission (Service monitor) |
| Exchange Mailbox Transport Delivery (Service monitor) | Exchange Mailbox Transport Delivery (Service monitor) |
| Exchange Health Manager (Service monitor) | Exchange Health Manager (Service monitor) |
| Exchange Search (Service monitor) | Exchange Search (Service monitor) |
| Exchange Replication (Service monitor) | Exchange Replication (Service monitor) |
| Exchange DAG Management (Service monitor) | Exchange DAG Management (Service monitor) |
Included with this resource.
Everything added when you import.
Tags
- EXCHANGE
Use cases.
Common ways to put this resource to work.
- Ensuring uptime for on-premises Microsoft Exchange servers.
- Proactively monitoring critical email and calendaring services.
- Supporting business continuity in hybrid Exchange environments.
- Avoiding SLA breaches related to email availability.
Recommendations.
Practical guidance for a reliable rollout.
- Tagging: Apply the “Exchange” tag to all relevant devices. We recommend automatically tagging to avoid missing key devices. See “Service Based Tagging” automation as an example.
- Testing: Simulate service failures to validate the monitor’s ability to restart services and send alerts.
- Regular Updates: Keep Exchange servers updated to avoid service interruptions caused by outdated software.
- Resource Monitoring: Pair this policy with monitors for CPU, memory, and storage usage to catch underlying issues.