A connection is how CloudEval learns about the infrastructure you want to evaluate.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.
Two connection modes
| Mode | Use it when | Current support |
|---|---|---|
| Live cloud environment | You want to evaluate deployed Azure resources | Azure today |
| Infrastructure as code | You want to review templates before deployment | ARM and Bicep-generated ARM JSON |
What a connection stores
Depending on the connection type, CloudEval can store or reference:- provider metadata
- sync configuration
- template URL or uploaded files
- scoped Azure subscription and resource groups
- connection health and test results
Why connections exist separately from projects
Connections answer the question, “Where does this infrastructure come from?” Projects answer a different question: “Where does my team review, report on, and share this work?” That separation matters because the same source model can be used to create or update project state over time.Azure connection reality
For live Azure environments, the current product supports:- service principal credential validation
- subscription discovery
- optional resource group scoping