These docs focus on the workflows customers can use today.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.
Current support status
| Workflow | Status | Notes |
|---|---|---|
| Azure live environment connection and sync | Available | This is the main supported path today. |
| Azure subscription discovery | Available | Supported for Azure service principal connections. |
| Azure resource group discovery and scoping | Available | Optional scoping is available during connection setup. |
| ARM template import | Available | Supported through file upload or template URL. |
| Bicep-generated ARM JSON review | Available | Documented when the output is imported as template input. |
| AWS live environment connection | Not available today | AWS appears in some UI surfaces, but connection creation is currently disabled. |
| GCP live environment connection | Not available today | GCP is not yet documented as a shipped workflow. |
| Multi-cloud parity | Coming soon | Do not assume Azure workflows map 1:1 to other providers. |
What this means in practice
- This documentation uses Azure examples on purpose.
- If you are evaluating a live cloud environment, use Azure service principal credentials.
- If you want an IaC-first workflow, use ARM or Bicep output as the supported baseline.
- If your team is exploring AWS or GCP with CloudEval, treat that as an early or limited path rather than a standard workflow.