Skip to main content

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.

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: either a live Azure connection or an imported ARM/Bicep source
  • One cost report
  • One architecture report
  • Optional CLI repeatability for scripts or terminal workflows
If you are trying CloudEval for the first time, the template path is usually the fastest way to get to a real result.

​
Choose your starting path

Create from GitHub URL

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

Connect Azure

Best when you want to inspect an existing subscription or scoped resource groups.

Import a template

Best when you want to review infrastructure before deployment or without cloud credentials.

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
  1. Create a project from a GitHub URL if the template already lives in GitHub.
  2. Connect an Azure environment if you want a live cloud path.
  3. Import an ARM or Bicep template if you want an IaC-first path from local files or a template URL.
  4. Use the CLI if you want a terminal-first workflow.
  5. Run your first reports.

​
Which path should most teams start with?

If you are evaluating CloudEval for the first time, the template path is usually faster because it avoids credential setup. If you need current-state topology and subscription data, start with a live Azure connection instead. If you already know you need JSON output or shell automation, start with the CLI page first.

​
Next step

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