Exchange Web Services HTTPS endpoint
124-exchange-ews.yaml
HTTP(S)
What this example does
Exchange infrastructure monitoring: Exchange Web Services HTTPS endpoint. It helps operators check the availability of this client-access or mail-routing dependency.
Checks and behavior
- Sends an GET request to https://mail.example.com/EWS/Exchange.asmx.
- Checks allowed/denied HTTP status codes.
- TLS settings cover certificate trust, certificate expiry.
- Formats results for nagios output.
Adapt example domains, addresses, credentials and thresholds to your environment before use. HTTP availability does not confirm an authenticated Exchange workflow.
YAML configuration
# Copyright (c) 2026 mati peterson. Maintainer: mati peterson <ipsonic@mailbox.org>. Project: https://ipsonic.com/probe/. Disclaimer: Provided AS IS, without warranty of any kind. Use at your own risk; validate checks and configurations before production use.
# Exchange example: replace placeholder domains/IPs and adapt expected HTTP statuses to your deployment.
# HTTP status alone does NOT prove successful Exchange authentication or mailbox functionality.
name: Exchange Web Services HTTPS endpoint
url: https://mail.example.com/EWS/Exchange.asmx
timeouts:
connect: 4
response: 12
request:
method: GET
follow_redirects: false
tls:
verify: true
min_valid_days: 21
tests:
status:
allow:
- 200
- 401
- 403
monitoring:
service_name: Exchange Web Services HTTPS endpoint
output: nagios
on_failure: critical