PrizmikAca 
PrizmikWeb 
PrizmikFunc 
PrizmikApi 
PrizmikSwa 
PrizmikSuite
Azure Functions are powerful, but as your Function App grows beyond a handful of functions, understanding how everything connects becomes a challenge. Which functions share the same Service Bus queue? Which HTTP triggers feed into which orchestrators? Which bindings are unused?
Azure Portal shows you a flat list of functions. PrizmikFunc shows you a Dependency Graph.
What the Dependency Graph shows
The Dependency Graph is an interactive node graph that visualizes the relationships between your functions, triggers, and bindings:
- Functions are the central nodes
- Triggers (HTTP, Timer, Service Bus, Queue, Blob, Event Grid, etc.) are shown as input connections
- Input bindings connect data sources to functions
- Output bindings connect functions to downstream services
Edges between nodes show the flow of data: a Service Bus trigger feeds into a function, which has an output binding to a Cosmos DB collection, which triggers another function via a change feed.
How to use it
- Open PrizmikFunc and select your Function App
- Go to the Dependency Graph panel (or use
⌘Kand type "dependency") - The graph renders automatically based on your function.json definitions
- Click any node to see its details — trigger configuration, binding parameters, function code path
- Use the toolbar to zoom, fit-to-screen, or export to PNG/SVG/PDF
Practical use cases
Onboarding new team members
Instead of walking through each function.json file, share a screenshot or PDF export of the Dependency Graph. New developers can see the entire architecture in one view and understand how data flows through the system.
Debugging event chains
When a downstream function isn't being triggered, the Dependency Graph shows you the exact chain: which trigger should fire, which bindings carry the data, and where the chain might be broken.
Refactoring planning
Before splitting a Function App or consolidating functions, the graph shows you which functions are tightly coupled (sharing triggers or bindings) and which are independent. This makes refactoring decisions data-driven rather than guesswork.
Documentation
Export the graph as SVG or PDF and include it in your architecture documentation. It stays accurate because it's generated from the actual function definitions, not a manually maintained diagram.
Distributed Tracing
Beyond the static Dependency Graph, PrizmikFunc also provides a Distributed Tracing waterfall view. This shows actual request flows across functions in real time — how long each function took, where delays occurred, and which functions failed.
Combined with the Dependency Graph, you get both the design-time architecture (how things are wired) and the runtime behavior (how things actually perform).
Try it yourself
The Dependency Graph is available in the free Community Edition of PrizmikFunc. If you have Azure Functions in production, download PrizmikFunc and see your architecture visualized in seconds.