REP · Reports & Analytics
Dependencies and impact
What relies on what, and what stops working if something goes.
4 min read
Insights → Dependencies maps the links between your items — a certificate deployed on a server, a licence installed on a device, a licence or certificate that depends on another item — and follows the chains, so before you retire a server or let a certificate lapse you can see everything it takes down with it. It reads the links recorded on each item: the ones you add, plus the licence-to-device links a Microsoft 365 sync records for group-licensed devices.
- 01
Record the links on each item
Links live on an item's Overview. On hardware the section is "Assigned licences & certificates": Link item adds the licences installed on the device and the certificates deployed on it, and a Depends on group lists the items that depend on the device. On licences and certificates the section is "Dependencies": Link item records something the item depends on, and the devices it runs on are set in its Assignments tab. Once an item has a link, See full impact on that card jumps straight to it on the Dependencies page.
- 02
Browse the map
Tabs split Hosts, Certificates and Licences. On Hosts, choose Infrastructure (hosts that carry certificates or sit in a chain with other hardware), Endpoints or All. Search by name, sort by Most affected, Open alerts first, Expires soonest, Most hosts, Most devices or Name A–Z, depending on the tab, and expand rows (or Expand all) to follow each chain.
- 03
Check the impact
Select a host to see what it relies on, what goes if it goes down or is retired, and the open alerts on it and on everything that depends on it. A certificate shows the hosts it's deployed on; a licence shows the devices it's installed on. Triage still happens on the Alerts page — this view only shows where the alerts sit. An alert's details also offer See impact when its item has links.
- 04
Share it
Copy impact summary puts the chain into plain text, ready for a change ticket or a client email.