This workflow is for teams that want faster feedback before infrastructure hits a live environment.Documentation Index
Fetch the complete documentation index at: https://docs.cloudeval.ai/llms.txt
Use this file to discover all available pages before exploring further.
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
- Import the ARM template or Bicep-generated ARM JSON.
- Add a parameters file if the template depends on one.
- Create a project from that IaC source.
- Run architecture and cost reports.
- Review the findings before the deployment decision.


Why teams like this path
- It avoids credential setup.
- It keeps code and findings in one workspace.
- 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
