Updated May 12, 2026
How do I convert Bicep to a cloud architecture diagram?
Quick answer
Compile Bicep to ARM JSON, then create a Cloudeval Azure project from that ARM output.
Cloudeval can render diagrams, run reports, export images, and answer questions from the resulting project context.
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
Turn a Bicep deployment into a diagram and review path your team can inspect.
Best source to use
Start by compiling Bicep to ARM JSON. That gives Cloudeval the resource model it can diagram and review.
What you need
- Azure tooling that can compile Bicep to ARM JSON.
- A Cloudeval account.
- The compiled ARM JSON file or supported repository URL.
What you get
- A Cloudeval project based on compiled Bicep output.
- Architecture and dependency diagrams.
- Reports, exports, and AI answers based on the generated ARM resources.
Fastest path to a useful result
- 1Compile Bicep to ARM JSON.
- 2Create a Cloudeval Azure project from the compiled file.
- 3Open the generated diagram.
- 4Ask one targeted question, such as which resources are public or expensive.
When this works best
Use this when Bicep can be compiled to ARM JSON.
Native Bicep authoring is not the workflow described here.
Decision guide
| Check | Cloudeval path | Note |
|---|---|---|
| Input | Compiled ARM JSON from Bicep. | Keep the original Bicep nearby for code review context. |
| Diagram output | Resource and dependency views. | Review both before deployment. |
| AI answers | based on Cloudeval project and report context. | Quality depends on imported context. |
| Automation | CLI can help create projects and run reports. | Use scoped credentials in CI. |
Who this is for
- Azure Bicep users
- IaC reviewers
- DevOps engineers
- Cloud architects
How it works
- 1Compile the Bicep file to ARM JSON with the normal Azure tooling.
- 2Create a Cloudeval project using the compiled ARM JSON.
- 3Open the project diagram to inspect architecture grouping and dependencies.
- 4Run reports to attach cost, security, and architecture evidence where available.
- 5Ask Cloudeval AI to explain specific resources, risks, or report findings.
- 6Export the diagram for review or documentation.
Bicep module architecture review
For a web workload, compile the Bicep module and load the ARM JSON into Cloudeval.
- Inspect the virtual network, subnet, app, database, identity, and monitoring resources.
- Then ask which resources create cost or security review items before deployment.
Terminal and agent workflow
- Use Azure tooling to compile Bicep before creating the Cloudeval project.
- Use the Cloudeval CLI to create, open, ask, and export from the resulting project.
- Agents using MCP can ask Cloudeval for project and report context after the project exists.
How to trust the result
- Compile Bicep to ARM JSON so Cloudeval sees the deployable resource model.
- Remember that compiled output does not show every authoring choice from the original Bicep module.
- Review generated resources and parameters before relying on the diagram.
FAQ
Does Cloudeval parse Bicep directly?
The conservative documented path is to compile Bicep to ARM JSON and import that into Cloudeval as an Azure project.
Can Cloudeval explain the diagram after Bicep import?
Yes.
Cloudeval chat can answer questions using project, graph, report, and available evidence context.
Can I use this in CI?
Cloudeval's CLI supports automation-friendly commands and scoped access keys.
Use current CLI capability output as the source of truth for CI workflows.
Related pages
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.
