Estate mapWhat is joined to what
A table cannot tell you that moving one environment drags a custom connector two other production environments also depend on. The map is drawn from the same stored assessment as every other page, so it can never disagree with them — it is simply the projection that makes dependency visible.
- Environments on one side, connectors on the other, with edge thickness as the real connection count
- Connectors that cross environments listed separately — custom and production-touching first
- Drill into one environment for environment → apps → the flows and connectors they reach
- Selecting an app lights what it carries, including connectors it only reaches through a flow
Inside one environment
Three columns: the environment, the apps and standalone flows it holds, and the objects those reach. Selecting an app dims everything else and the inspector lists what it carries. Note the last panel — two connectors this app never binds itself. They arrive with the flows it calls, and they move with it. An app's own connector list will never show you that.
Every screen here is a live demo tenant
Contoso is sample data, generated rather than scanned — but it renders through exactly the same code as a real tenant, so what you walk around is what you would get.