> ## 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.

# Evaluate an Azure environment with Cloud sync

> Run a full CloudEval AI review loop against deployed Azure resources.

Use this workflow when the question is about what exists today in Azure, not just what is defined in source control.

This is the **Cloud sync** workflow. It uses a least-privilege service principal
to read deployed Azure resources, export deployment templates, and enrich the
graph with Network Watcher topology when that permission is available.

## Best for

<Columns cols={2}>
  <Card title="Subscription reviews" icon="cloud">
    Review a scoped Azure estate with current deployed-state context.
  </Card>

  <Card title="Environment health checks" icon="activity">
    Check active resources, topology, and report readiness before planning work.
  </Card>

  <Card title="Architecture and cost baselines" icon="chart-no-axes-column">
    Generate baseline cost and architecture reports from the same project.
  </Card>

  <Card title="Stakeholder snapshots" icon="share-2">
    Share a project or read-only view when the review needs a broader audience.
  </Card>
</Columns>

## Workflow

```mermaid theme={null}
flowchart LR
  connection["Azure Cloud sync connection"] --> scope["Subscription or resource group scope"]
  scope --> project["Cloudeval project"]
  project --> sync["Sync deployed resources"]
  sync --> reports["Cost and architecture reports"]
  reports --> share["Share or export evidence"]
```

<Steps>
  <Step title="Create an Azure Cloud sync connection">
    Use a least-privilege service principal and the `CloudEval Live Sync Reader` role.
  </Step>

  <Step title="Scope the source">
    Choose the subscription or resource groups that match the review boundary.
  </Step>

  <Step title="Create and sync the project">
    Create a project from the connection, then run the initial sync.
  </Step>

  <Step title="Run reports">
    Generate cost and architecture reports from the synced project.
  </Step>

  <Step title="Share evidence">
    Share the project internally or publish a read-only view when the result is appropriate to distribute.
  </Step>
</Steps>

## 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

## Common mistake

<Warning>
  Do not start with a huge multi-subscription scope if your goal is to validate the product quickly. Start with one representative environment, then expand.
</Warning>

<Warning>
  Do not use `Contributor` for production sync. Use the `CloudEval Live Sync Reader` custom role from [Azure Cloud sync permissions](/reference/azure-live-sync-permissions).
</Warning>

## Next step

Use [Connect an Azure environment](/quickstart/connect-an-azure-environment) to set it up, then continue to [Run your first reports](/quickstart/run-your-first-reports).