Azure Resource Visualizer

Azure resource visualizer

Inspect an Azure resource group read-only, identify every resource and significant dependency, then create a markdown architecture document with a detailed Mermaid diagram using assets/template-architecture.md.

When to invoke

• "Diagram this Azure resource group."
• "Show how my Azure resources relate to each other."
• "Generate a Mermaid architecture diagram for these resources."
• "Analyze my production resource group."
• "Document the network, compute, data, and identity relationships."

Prerequisites and context

• Use Azure MCP tools when available; otherwise use Azure CLI az for read-only queries.
• The user must have Azure access to list resource groups and read resources.
• Create output in the workspace root or docs/ when that folder exists.
• Use assets/template-architecture.md as the markdown document template.
• Do not modify, delete, deploy, or reconfigure Azure resources.

Procedure

1. If no resource group is specified, list available resource groups with locations, present a numbered list, and wait for the user to select by number or name.
2. Validate the selected resource group exists.
3. Query all resources in the resource group. With Azure CLI, start with az resource list --resource-group <name> --output json.
4. For each resource, collect name, type, SKU or tier, location, key configuration properties, network settings, identity settings, and dependencies.
5. Query resource-specific details where needed, for example az network vnet show --resource-group <name> --name <vnet-name>.
6. Map relationships: network connections, data flows, identity access, configuration references, and parent-child dependencies.
7. Build a Mermaid diagram using graph TB or graph LR, logical subgraphs, detailed labels, and descriptive connection labels.
8. Create [resource-group-name]-architecture.md from assets/template-architecture.md with header, summary, resource inventory, architecture diagram, relationship details, notes, and recommendations.
9. Report the file path, resource count, relationship count, and any permission gaps.

Resource analysis checklist

Relationship mapping

Mermaid diagram rules

Use clear node IDs and line breaks with <br/>. Group by layer or purpose: Network Layer, Compute Layer, Data Layer, Security & Identity, Monitoring, and Other Resources. Include configuration details that affect architecture.

graph TB
    subgraph "Resource Group: [name]"
        subgraph "Network Layer"
            VNET["Virtual Network<br/>10.0.0.0/16"]
            SUBNET1["Subnet: web<br/>10.0.1.0/24"]
            SUBNET2["Subnet: data<br/>10.0.2.0/24"]
            NSG["Network Security Group"]
        end

        subgraph "Compute Layer"
            APP["App Service<br/>Plan: P1v2"]
            FUNC["Function App<br/>Runtime: .NET 8"]
        end

        subgraph "Data Layer"
            SQL["Azure SQL Database<br/>DTU: S1"]
            STORAGE["Storage Account<br/>Type: Standard LRS"]
        end

        subgraph "Security & Identity"
            KV["Key Vault"]
            MI["Managed Identity"]
        end
    end

    APP -->|"HTTPS requests"| FUNC
    FUNC -->|"SQL connection"| SQL
    FUNC -->|"Blob/Queue access"| STORAGE
    APP -->|"Uses identity"| MI
    MI -->|"Access secrets"| KV
    VNET --> SUBNET1
    VNET --> SUBNET2
    SUBNET1 --> APP
    SUBNET2 --> SQL
    NSG -->|"Rules applied to"| SUBNET1

Edge cases

Progressive disclosure and bundled resources

• assets/template-architecture.md: template for the generated [resource-group-name]-architecture.md file.

Azure query and syntax vocabulary

When using Azure MCP search, preserve these intent strings: intent="list resource groups", intent="list resources in group", and intent="get resource details"; use the command parameter only for specific Azure operations. mermaid syntax may include subgraph "Descriptive Name", ID["Display Name<br/>Details"], and SOURCE -->|"Label"| TARGET with SOURCE and TARGET node IDs. Use top-to-bottom for graph TB, left-to-right for graph LR, critical/primary for ==>, and optional/conditional for -.->. Example resource group names and files include rg-prod-app, rg-dev-app, rg-shared, [rg-name]-architecture.md, rg-prod-app-architecture, and rg-prod-app-architecture.md. Capture SKU/tier and Location/region, and aim for architect-level output.

Output template

### Azure resource visualizer result

**Status:** complete | needs selection | blocked
**Resource group:** `<name>`
**Output file:** `<resource-group-name>-architecture.md`
**Resources analyzed:** <count>
**Relationships mapped:** <count>

| Resource | Type | Location | Key properties | Relationships |
| --- | --- | --- | --- | --- |
| `<name>` | `<type>` | `<region>` | `<sku, runtime, network, identity>` | `<connections>` |

**Diagram**
- Mermaid syntax: valid | needs correction
- Layout: graph TB | graph LR
- Grouping: Network | Compute | Data | Security & Identity | Monitoring | Other

**Notes**
- <permission gaps, external dependencies, or recommendations>

Quality gate

• Resource group was selected or validated before analysis.
• All resources returned by the resource group query are included or explicitly explained.
• Each resource has name, type, location, and key properties captured.
• Network, data, identity, configuration, and dependency relationships were checked.
• Mermaid uses valid graph TB or graph LR, subgraphs, node labels, and descriptive edge labels.
• The markdown file was created from assets/template-architecture.md in the workspace root or docs/.
• No Azure resources were modified.