by erik

**Azure Reservations** — Monitor your Microsoft Azure Reservations directly from Checkmk 2.4. A special agent talks to the Azure REST APIs (no SDK, no per-server agents) and exposes three service classes per target: - **Azure Reservation** *reservationname* — one service per reservation: expiry (days remaining / end date) and multi-window utilization (7d/30d/90d/6mo/12mo) from the Consumption API, with configurable thresholds, per-item overrides and alerting on expected-but-missing reservations. - **Azure Reservations Permissions** — an RBAC self-check that verifies the service principal's roles and prints the exact *az role assignment create* command for anything missing. - **Azure Reservations Summary** — per-host collection diagnostics: fetch health, data freshness and error counts. The client secret is stored in the Checkmk password store, whole-output caching keeps Azure API load (and 429 throttling) low, and a hold-last-good cache prevents false alerts during transient Consumption-API outages. Pure site-Python dependencies (*requests*). Works on all editions, including MSP/CME. GPLv2.