Use this workflow when the question is about what exists today in Azure, not just what is defined in source control.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.
Best for
- Subscription reviews
- Environment health checks
- Architecture and cost baselining
- Stakeholder-ready snapshots before planning work
Workflow
- Create an Azure live-environment connection.
- Scope it to the right subscription or resource groups.
- Create a project from that connection.
- Sync the project.
- Run cost and architecture reports.
- Share the project internally or publish a read-only view.
What makes this workflow valuable
It gives you current-state context. That is useful when the real question is about drift, active cost exposure, or the architecture that is actually running now.Good output
A good first review ends with:- one project per environment or scope that matters
- a recent cost snapshot
- an architecture score the team can discuss
- a short list of fixes or follow-up questions