Skip to main content
This workflow is for teams that want faster feedback before infrastructure hits a live environment.

​
Best for

  • Design review before release
  • Pull request review support
  • Architecture and cost checks during planning
  • Shared review between engineers and stakeholders who do not want to parse raw template JSON

​
Workflow

  1. Choose the IaC source shape:
    • single ARM JSON template
    • ARM JSON plus parameters file
    • multi-file workspace with linked or nested ARM templates
  2. For a multi-file workspace, add .cloudeval/config.yaml and set stacks[].entry to the visualization source.
  3. Create a project from that IaC source.
  4. Run architecture and cost reports.
  5. Review the findings before the deployment decision.
CloudEval workspace code editor showing an imported ARM template, file explorer, report files, and outline

Imported infrastructure code can be reviewed beside the project files, report outputs, and generated ARM JSON outline.

CloudEval code editor with selected ARM JSON lines and an AI assistant response explaining the selected resource

Code review can stay grounded in a selected template range, file path, line numbers, and the assistant response.

​
Why teams like this path

  • It avoids credential setup.
  • It keeps code and findings in one workspace.
  • It keeps linked ARM files separate in the code view while using a resolved bundle for diagrams and reports.
  • It makes pre-deployment review easier for people outside the original authoring context.

​
What to look for

  • High-severity architecture issues
  • Unexpected dependencies or topology shape
  • Cost signals that should change SKU or resource choices before rollout

​
Next step

If you have not imported a template yet, start with Import an ARM or Bicep template.
Last modified on May 22, 2026