Liongard Exchange On-Prem Read

Category: Liongard Inspectors · View source ↗

Runs as: Skill Run it in Super Magic and confirm each write. A Flow can also fire a shared skill through the Run Skill action (beta), though this one is written for a person to run rather than a ticket event. Connectors: Liongard Role: Technician Outcome: Risk & Compliance, Faster Resolution & Response When to use: “What CU/build is <client>‘s Exchange server on?” (Exchange CVEs are commonly build-gated), “what mailbox databases exist and how big are they?”, mailbox inventory, “what send/receive connectors and mail-flow routing are configured?”, or “did a connector or database setting change?”. For Exchange Online, use the M365 tenant read. Run it: on one client — name the client and the Exchange question.

Prompt

Read on-premises Microsoft Exchange state for CLIENT_NAME from the Liongard Exchange inspector. Read-only — Exchange config, connectors, and mailboxes are a technician's job via EMS/ECP.

1. Resolve the client's environment, then find the on-prem Exchange inspector (confirm it's the on-prem one, not Exchange Online) and confirm it ran recently — carry "as of <timestamp>." Mail config changes, so an old data read on an active mail-flow incident deserves a "verify live" caveat.
2. Read the values from its latest dataprint for the angle you need, verifying every field angle against the live dataprint (schemas vary by inspector version):
   - Version: server version/CU/build — report verbatim; compare against Microsoft's current CU and known-vuln advisories rather than asserting from memory.
   - Databases: database list with size and mount status — flag large/dismounted.
   - Mailboxes: mailbox count per database.
   - Connectors: send/receive connector list with smart-host/routing.
   - Admins: Exchange admin role assignments.
3. "What changed?" → check what changed on Exchange: CU/build upgrades, connector changes, database adds/removes, admin changes — ordered against the incident window (time-adjacency, not proven cause).
4. Sanity-check surprising zeros (zero databases) — usually a wrong field angle or partial inspection; re-probe broadly. Never paste connector credentials or smart-host secrets into notes — reference "credentials on file in <doc platform>." Exchange CU/build currency is a high-priority security finding (on-prem Exchange has repeatedly been actively exploited) — surface with the as-of date and recommend the tech patch.
5. Output: a compact table, source + data age line, flags (outdated CU/build, dismounted databases, unexpected connectors, excess admins). Offer to leave a plain-text note. Degradation: no on-prem Exchange inspector → documentation → ticket history → "verify on server."

​Prompt

Prompt