These docs focus on the workflows customers can use today.
CloudEval is Azure-first today. Do not infer AWS or GCP parity from provider names that may appear in the UI.
Current support status
| Workflow | Status | Notes |
|---|
| Azure Cloud sync connection | Available | This is the main supported live-cloud 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. |
| Single ARM template import | Available | Supported through file upload or template URL. |
| Multi-file ARM workspace import | Available | Supported with .cloudeval/config.yaml for visualization source and linked-template resolution. |
| 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 Cloud sync with Azure service principal credentials.
- If you want an IaC-first workflow, use ARM or Bicep-generated ARM JSON as the supported baseline.
- If the IaC source has linked or nested ARM templates, add
.cloudeval/config.yaml so CloudEval knows the visualization source.
- If your team is exploring AWS or GCP with CloudEval, treat that as an early or limited path rather than a standard workflow.
Why the docs are strict here
We only document workflows that customers can rely on today. That is why the docs stay Azure-first instead of implying full provider parity.
Next step
If you want a Cloud sync path, start with Connect an Azure environment. If you want an IaC path, go to Import an ARM or Bicep template. 