AI Azure architecture diagram generator.
From Bicep, ARM or Terraform, without granting a reader role on the subscription.
Sources it reads
Bicep files, ARM templates, Terraform using the azurerm provider, and Kubernetes manifests for AKS workloads. Bicep in particular reads well, because its module structure and symbolic references map cleanly onto components and edges without much inference.
How Lucid Train draws one
Describe what you want, or point it at a repository. The agent emits a semantic graph of nodes and edges with no coordinates, and the ELK layout engine computes positions and orthogonal routing. That separation is the reason the output cannot come back with boxes overlapping or arrows crossing through cards, which is the characteristic failure when a language model is asked to place things on a canvas itself. It also means editing is editing the graph: change a component and the layout re-solves rather than drifting out of alignment.
Resource groups are organisation, not architecture
Azure diagrams often use resource group boundaries as the primary grouping, which reflects how resources are administered rather than how the system works. Tiers describe the system; resource group membership becomes a note. If governance is the subject, draw that separately rather than letting it dominate the architecture picture.
Managed identity edges are worth drawing
Azure systems lean heavily on managed identities for service-to-service authentication, and those relationships are real edges that rarely appear in hand-drawn diagrams. Showing which identity a component uses to reach which resource makes an access model visible that is otherwise spread across role assignments.
Local, offline, your models
It runs as a desktop application. Against a local Ollama model the whole thing works offline with no API key and no telemetry, which is the practical difference from every browser-based diagram tool: your architecture never leaves the machine.
Azure services by tier
| Service | Tier |
|---|---|
| Front Door, CDN, Application Gateway | Edge |
| API Management | Edge |
| App Service, Container Apps, AKS | Application |
| Functions, Logic Apps | Application |
| SQL Database, Cosmos DB | Data |
| Blob Storage, Files | Data |
| Cache for Redis | Data |
| Service Bus, Event Grid, Event Hubs | Drawn as edges |
| Entra ID, Key Vault | Authentication boundary |
| Monitor, Application Insights | Infrastructure |
Try it
Questions
Does it need an Azure subscription?
No. It reads files, so no subscription, no reader role and no authentication.
Bicep or ARM?
Both. Bicep produces the better diagram because it is more readable and its references are explicit; ARM templates work but are noisier.
Does it use official Azure icons?
Bundled service icons that render offline. Some services fall back to a generic glyph rather than the exact mark.
Can it diagram AKS workloads too?
Yes, from the manifests, and that is usually a separate diagram: the infrastructure that provisions the cluster and the workloads running on it are different levels of zoom.
Related
- AI GCP Architecture Diagram GeneratorFrom the Terraform in your repository, with no project access and nothing uploaded.
- AI Kubernetes Architecture Diagram GeneratorThe topology is in the YAML. It is just spread across forty files and expressed as label matches.
- AI Microservices Diagram GeneratorThe interesting question is never how many services there are, it is which ones cannot be deployed without the others.
- AI Database Schema Diagram GeneratorThe physical view: tables, columns, keys and indexes, for when you need what is actually stored rather than the conceptual model.
Last updated