Skip to main content
This quickstart is designed to get you to a real result, not just a completed setup screen.

​
Expected outcome

By the end, you will have:
  • One CloudEval project
  • One input source: Cloud sync, a single ARM/Bicep-generated template, or a multi-file IaC workspace
  • One cost report
  • One architecture report
  • Optional CLI repeatability for scripts or terminal workflows
CloudEval split workspace showing an Azure architecture graph beside file explorer and generated cost report JSON
If you are trying CloudEval for the first time, the single-template infrastructure-as-code path is usually the fastest way to get to a real result. If you want to inspect value before connecting Azure or uploading your own source, start with the public GitHub sample.

​
Choose your starting path

Try the public sample

Inspect a real Azure ARM example repo and demo PRs before connecting Azure.

Create from GitHub URL

Fast browser path from a template URL to a project workspace.

Connect Azure

Cloud sync for an existing subscription or scoped resource groups.

Import infrastructure as code

Single ARM templates, parameters files, and nested ARM workspaces.

Use the CLI

Terminal-first setup for imports, reports, automation, and shell completion.

​
Before you start

  • Sign in to CloudEval AI.
  • Complete onboarding so the product can personalize the workspace.
  • Have one of the following ready:
    • Azure service principal credentials
    • ARM template or Bicep-generated ARM JSON
    • IaC workspace with .cloudeval/config.yaml when the source has linked or nested templates
  1. Try the public sample if you want to inspect CloudEval output before connecting Azure or uploading source.
  2. Create a project from a GitHub URL if the template already lives in GitHub.
  3. Connect an Azure environment if you want Cloud sync from deployed resources.
  4. Import an ARM or Bicep template if you want an IaC-first path from a single file, local workspace, or template URL.
  5. Use the CLI if you want a terminal-first workflow.
  6. Run your first reports.

​
Which path should most teams start with?

If you are evaluating CloudEval for the first time, the single-template path is usually faster because it avoids credential setup. If your source has nested or linked templates, use the IaC workspace path with .cloudeval/config.yaml. If you need current-state topology and subscription data, start with Cloud sync instead. If you already know you need JSON output or shell automation, start with the CLI page first.
CloudEval terminal UI with project-aware chat, reasoning progress, project context, model, mode, and credit status

​
Next step

Pick the path that matches your input source and continue with the corresponding setup guide.
Last modified on June 23, 2026