Does this show real network traffic?

No. Architecture and dependency views describe the relationships available in project evidence. Verify actual routing, firewall rules and reachability in the deployed environment.

Can I start without connecting Azure?

Yes. Import supported ARM JSON, or compile Bicep to ARM JSON first. That describes the template rather than the live environment; a Cloudeval account is still required.

What should I ask first?

Select one application resource and ask what it depends on, which evidence supports those relationships, and what context is missing. Inspect the cited source or report before acting.

How do I investigate an inherited Azure environment safely?

Start with the imported scope and sync time, inspect one dependency at a time, and ask which source or report supports the answer. Do not treat a graph as proof of live traffic.

Can I start without Azure credentials?

Yes. Import supported ARM JSON for a source-only review. Live discovery needs the documented Azure permissions.

What should I ask an architecture agent first?

Ask what one resource depends on, which evidence supports the relationship, and what scope or data is missing.

Should I use Azure Resource Graph or Cloudeval first?

Use Azure Resource Graph for live inventory queries and Cloudeval for diagrams, reports, source-linked findings and project questions. They complement each other; neither alone proves runtime reachability.

What should I document when taking over an Azure estate?

Record subscription and resource-group scope, regions, ownership, network boundaries, identity dependencies, last collection time and every missing or unsupported evidence area.

Answers

How do I understand an Azure environment I inherited?

Quick answer

To understand an inherited Azure environment, start with the subscription and resource-group scope, map the resources and dependencies, then investigate one risk at a time.

Azure Resource Graph and portal tools help inventory live resources; Cloudeval adds diagrams, reports, source-linked findings and project-aware questions for an imported ARM JSON template or documented Azure sync.

Ask AI about a project Read MCP setup

Start here

Use this to

Build a trustworthy inventory of an inherited Azure environment, trace one dependency, and record what the available evidence does and does not establish.

Best source to use

A missing relationship may mean missing source or stale sync. Check the last sync and the imported scope before assuming two services are disconnected.

What you need

A Cloudeval project with imported or synced Azure context.
At least one diagram, report, or resource graph to ground the answer.
A specific question, not a broad prompt.

What you get

An answer tied to project context.
Evidence, citations, or report references where available.
A next step when evidence is missing.

Get started

1
Connect Azure with the documented permissions, or import ARM JSON for a source-only review.
2
Start with resource groups and service boundaries in Architecture view.
3
Select one resource in Dependency view and trace its relationships.
4
Ask which source properties or report findings support the explanation.
5
Check sync time and missing evidence before sharing the result.
6
Start with one resource and one question, then open the referenced source or report before making a change.
7
Compare the observation time, imported scope and report status when an answer seems incomplete.
8
Export the relevant diagram or report section with its source revision when handing the review to another engineer.
9
Record subscriptions, resource groups, regions and the last sync or source revision before drawing conclusions.
10
Use Azure Resource Graph for live inventory queries, then use the Cloudeval graph and reports to investigate architecture and findings together.
11
Write down missing permissions, unsupported relationships and stale source areas as follow-up work rather than treating them as empty results.

Helpful docs

Walk through architecture with AI Guide Report concepts Diagram concepts MCP setup Sharing and collaboration Azure sync permissions Review a live Azure environment

When this works best

A graph describes collected relationships, not observed network traffic.

ARM import does not require live Azure credentials; live discovery does.
Neither proves runtime reachability.

AI Guide

Turn a diagram into a guided investigation

When a written answer is not enough, AI Guide walks through the architecture or dependency view, highlights the resources under discussion, and keeps the explanation, evidence, and next check together.

Personas adjust the emphasis for executive, architecture, security, or operations reviews. They do not change the available project evidence.

See how AI Guide works

Cloudeval Playground Architecture view with AI Guide entry point and a generated resource diagram — Real Playground capture. A guide explains available project evidence; it does not prove runtime traffic, health, or ownership.

Decision guide

Check	Cloudeval path	Note
Question style	Ask about one project, report, resource, or risk.	Specific questions produce clearer answers.
Grounding	Project graph, reports, docs, and evidence.	Cloudeval should say when evidence is missing.
Output	Answer plus next step.	Use reports for decisions that need source support.
Sharing	Export or share reviewed findings.	Do not expose private resource details unintentionally.

Trace one application dependency

Start with a load balancer or application resource.

Ask which resources it depends on, inspect those resources in the graph, and open the supporting source or report.
If the question is whether traffic can actually pass, verify deployed networking separately.

Terminal and agent workflow

Use this command for one-shot project questions.
shell
```
cloudeval ask "Summarize this project's top architecture risks" --project <project-id>
```
MCP-compatible agents can query Cloudeval context from supported clients.
CLI sessions can preserve useful local history for automation and investigation workflows.

How to trust the result

Ask which resource, report, or diagram element supports the answer when it affects a decision.
Check sync time and report confidence before sharing recommendations.
Use narrow questions for specific resources, findings, or dependencies.

Frequently asked questions

How do I convert an ARM template to an architecture diagram?How do I check whether my cloud inventory is complete?azure architecture review checklist