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.

Use this path when your infrastructure template already lives in GitHub and you want the shortest browser flow from URL to CloudEval project. CloudEval can consume supported GitHub template URLs, create the project, and redirect you into the resulting workspace when creation completes.
CloudEval quick project creation form with project name, cloud provider, template URL, file upload, and optional parameters URL fields

​
Prerequisites

  • A signed-in CloudEval account
  • A public or accessible GitHub URL to an ARM JSON template
  • A parameters file URL if the template requires one and CloudEval cannot auto-detect it
If your source of truth is Bicep, compile it to ARM JSON first, then use the generated ARM JSON URL or upload the generated file.

​
Create the project

1

Open the project creation flow

Open Projects, then choose Create project.
2

Choose a GitHub URL source

Select the template URL option and paste the GitHub URL.CloudEval accepts common GitHub URL shapes such as blob, tree, and raw GitHub content URLs when they point to supported template content.
3

Review parameter detection

When the URL points at GitHub, CloudEval tries to find a matching parameters file from the same repository when the naming pattern is recognizable.You may see states such as Looking…, Found, or Not found beside the parameters field. If the auto-detected file is not the right one, replace it with the exact parameters file URL.
4

Review and create

Confirm the project name, provider, template URL, and optional parameters URL.After you choose Review & Create, CloudEval creates the project and starts setting up the backing connection.
5

Follow the redirect

When project creation completes, CloudEval redirects you to the new project workspace.If background setup is still running, wait for the project status to finish before running reports or sharing the project.
CloudEval project workspace after creation showing project files, generated reports, code editor, validation counts, cost, and Well-Architected status

​
When to use this instead of upload

Use GitHub URL when:
  • the template already has a stable repository URL
  • you want teammates to recognize the source
  • you want CloudEval to try parameters-file detection
  • you want a browser-first flow without downloading files locally
Use local upload when the template is private, generated locally, or not available through a URL CloudEval can read.
CloudEval project creation connection selection step showing available Azure connections

​
Agent or CLI handoff

Agents and scripts can open the same browser flow with a prefilled template URL: 
cloudeval open projects \
  --quick \
  --template-url https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.compute/1vm-2nics-2subnets-1vnet/azuredeploy.json \
  --name "Azure quickstart import" \
  --provider azure \
  --print-url \
  --no-open
Use --auto-submit only when you have already tested the exact URL and defaults you want the browser flow to use.

​
Troubleshooting

SymptomWhat to check
CloudEval cannot read the URLConfirm the URL is public or accessible and points to supported template content.
Parameters are not auto-detectedPaste the exact parameters file URL manually.
The project opens but reports are unavailableWait for project setup to complete, then run cost and architecture reports.
The redirected workspace is not the expected projectCheck the project name and source URL in the review step before creating another project.

​
Next step

Run your first reports, or read Diagrams and workspace views to understand how the resulting project can be reviewed visually.
Last modified on May 5, 2026