Answers

Updated May 12, 2026

How do I generate an Azure architecture diagram automatically?

Quick answer

Create a Cloudeval project from an ARM template, compiled Bicep JSON, GitHub template URL, or live Azure sync.

Cloudeval builds architecture and dependency diagrams, then connects them to reports, exports, CLI commands, and AI answers.

Generate an Azure diagram Try the public playground

What you can expect

A practical path from source input to diagram, report context, docs, exports, and the first AI question to ask.

Start here

Use this to

Generate a useful Azure architecture diagram without redrawing the environment by hand.

Best source to use

Use live Azure sync when you need deployed state. Use ARM JSON or compiled Bicep when you want to review code before deployment.

What you need

A Cloudeval account.
An ARM template, compiled Bicep JSON, GitHub template URL, or live Azure sync connection.
Permission to review the project and run reports.

What you get

Architecture and dependency diagrams.
Report-backed findings for architecture, security, cost, or Well-Architected review.
Exportable diagram or shareable review context.

Fastest path to a useful result

1
Create a Cloudeval Azure project.
2
Import ARM JSON, compiled Bicep JSON, a supported GitHub template URL, or live Azure context.
3
Open the diagram and switch between architecture and dependency views.
4
Run one report, then ask Cloudeval AI one focused question about the diagram.

Cloudeval diagram properties panel with resource details

Helpful docs

Diagram concepts Report concepts Review IaC before deployment CLI overview

When this works best

Use this when your source is ARM JSON, compiled Bicep, a supported GitHub template URL, or live Azure sync.

Check the current docs before planning AWS, GCP, Terraform, or CloudFormation workflows.

Decision guide

Check	Cloudeval path	Note
Source input	ARM JSON, compiled Bicep JSON, supported GitHub template URL, or live Azure sync.	Start with the source you already trust.
First output	Architecture and dependency diagrams.	Use the dependency view when relationships matter more than layout.
Review layer	Reports and AI answers connected to the project.	Run a report before relying on recommendations.
Export	Browser or CLI diagram export.	Avoid public sharing until private details are removed.

Who this is for

Cloud architects
DevOps engineers
Platform teams
Consultants reviewing Azure estates

How it works

1
Create a Cloudeval project from an ARM template, compiled Bicep JSON, GitHub template URL, or Azure live sync connection.
2
Let Cloudeval process resources, relationships, subscriptions, resource groups, networks, compute, data stores, and policy context where available.
3
Open the project diagram and switch between architecture and dependency views when you need layout or relationship detail.
4
Run architecture, security, cost, or Well-Architected reports to attach evidence and findings to the diagram.
5
Ask Cloudeval AI questions about the project, graph, reports, and evidence history.
6
Export the diagram or share a controlled project view when stakeholders need review material.

Azure web application architecture

A typical project can show a virtual network, subnets, application gateway, app service, SQL database, storage account, key vault, monitoring resources, and security findings.

The diagram is useful because each component stays connected to resource context, report findings, and follow-up questions.

Terminal and agent workflow

Use this command to create a project from local ARM JSON.
shell
```
cloudeval projects create --template-file ./azuredeploy.json --provider azure
```
Use this command to open the diagram from a terminal workflow.
shell
```
cloudeval open project <project-id> --view preview --layout architecture
```
MCP-compatible agents can query Cloudeval project, graph, report, pricing, and documentation context when configured.

How to trust the result

Check when the project data was last synced before using the diagram in a review.
Use linked reports and resource details to verify why a node or finding appears.
Treat AI answers as project summaries; verify risky changes against the source resource or template.

FAQ

Can Cloudeval generate a diagram from Bicep?

Yes, use the compiled ARM JSON output from Bicep as the project input.

Cloudeval's strongest shipped IaC path is Azure ARM/Bicep context.

Does Cloudeval keep Azure diagrams updated?

Cloudeval supports live Azure sync connections, so teams can refresh project context instead of relying only on manually maintained diagrams.

Can I ask AI questions about the generated diagram?

Yes.

Cloudeval chat can answer questions based on project metadata, diagram/resource graph data, reports, and available evidence.

How do I convert an ARM template to an architecture diagram?How can I chat with my Azure architecture?How do I export cloud diagrams from the CLI?

Build this workflow in Cloudeval

Start with a Cloudeval Azure project, then connect diagrams, reports, source links, CLI automation, and MCP-compatible agent workflows around the same source of truth.