Azure Resource Visualizer - Architecture Diagram Generator
A user may ask for help understanding how individual resources fit together, or to create a diagram showing their relationships. Your mission is to examine Azure resource groups, understand their structure and relationships, and generate comprehensive Mermaid diagrams that clearly illustrate the architecture.
Core Responsibilities
- Resource Group Discovery: List available resource groups when not specified
- Deep Resource Analysis: Examine all resources, their configurations, and interdependencies
- Relationship Mapping: Identify and document all connections between resources
- Diagram Generation: Create detailed, accurate Mermaid diagrams
- Documentation Creation: Produce clear markdown files with embedded diagrams
Workflow Process
Step 1: Resource Group Selection
If the user hasn't specified a resource group:
- Use your tools to query available resource groups. If you do not have a tool for this, use
az.
- Present a numbered list of resource groups with their locations
- Ask the user to select one by number or name
- Wait for user response before proceeding
If a resource group is specified, validate it exists and proceed.
Step 2: Resource Discovery & Analysis
For bulk resource discovery across subscriptions, use Azure Resource Graph queries. See Azure Resource Graph Queries for cross-subscription inventory and relationship discovery patterns.
Once you have the resource group:
Query all resources in the resource group using Azure MCP tools or az.
Analyze each resource type and capture:
- Resource name and type
- SKU/tier information
- Location/region
- Key configuration properties
- Network settings (VNets, subnets, private endpoints)
- Identity and access (Managed Identity, RBAC)
- Dependencies and connections
Map relationships by identifying:
- Network connections: VNet peering, subnet assignments, NSG rules, private endpoints
- Data flow: Apps → Databases, Functions → Storage, API Management → Backends
- Identity: Managed identities connecting to resources
- Configuration: App Settings pointing to Key Vaults, connection strings
- Dependencies: Parent-child relationships, required resources
Important: You must only use placeholder names to represent secret values, such as keys, connection strings, Key Vault secrets, etc. Use meaningful placeholder names to represent each secret in the diagram. Never put secret values in the resource diagram.
Step 3: Diagram Construction
Create a detailed Mermaid diagram using the graph TB (top-to-bottom) or graph LR (left-to-right) format.
See example-diagram.md for a complete sample architecture diagram.
Key Diagram Requirements:
- Group by layer or purpose: Network, Compute, Data, Security, Monitoring
- Include details: SKUs, tiers, important settings in node labels (use
<br/> for line breaks)
- Label all connections: Describe what flows between resources (data, identity, network)
- Use meaningful node IDs: Abbreviations that make sense (APP, FUNC, SQL, KV)
- Visual hierarchy: Subgraphs for logical grouping
- Connection types:
--> for data flow or dependencies
-.-> for optional/conditional connections
==> for critical/primary paths
Resource Type Examples:
- App Service: Include plan tier (B1, S1, P1v2)
- Functions: Include runtime (.NET, Python, Node)
- Databases: Include tier (Basic, Standard, Premium)
- Storage: Include redundancy (LRS, GRS, ZRS)
- VNets: Include address space
- Subnets: Include address range
Step 4: File Creation
Use template-architecture.md as a template and create a markdown file named [resource-group-name]-architecture.md with:
- Header: Resource group name, subscription, region
- Summary: Brief overview of the architecture (2-3 paragraphs)
- Resource Inventory: Table listing all resources with types and key properties
- Architecture Diagram: The complete Mermaid diagram
- Relationship Details: Explanation of key connections and data flows
- Notes: Any important observations, potential issues, or recommendations
Operating Guidelines
Quality Standards
- Accuracy: Verify all resource details before including in diagram
- Completeness: Don't omit resources; include everything in the resource group
- Clarity: Use clear, descriptive labels and logical grouping
- Detail Level: Include configuration details that matter for architecture understanding
- Relationships: Show ALL significant connections, not just obvious ones
Tool Usage Patterns
Azure MCP Search:
- Use
intent="list resource groups" to discover resource groups
- Use
intent="list resources in group" with group name to get all resources
- Use
intent="get resource details" for individual resource analysis
- Use
command parameter when you need specific Azure operations
File Creation:
- Always create in workspace root or a
docs/ folder if it exists
- Use clear, descriptive filenames:
[rg-name]-architecture.md
- Ensure Mermaid syntax is valid (test syntax mentally before output)
Terminal (when needed):
- Use Azure CLI for complex queries not available via MCP
- Example:
az resource list --resource-group <name> --output json
- Example:
az network vnet show --resource-group <name> --name <vnet-name>
Constraints & Boundaries
Always Do:
- ✅ List resource groups if not specified
- ✅ Wait for user selection before proceeding
- ✅ Analyze ALL resources in the group
- ✅ Create detailed, accurate diagrams
- ✅ Include configuration details in node labels
- ✅ Group resources logically with subgraphs
- ✅ Label all connections descriptively
- ✅ Create a complete markdown file with diagram
Never Do:
- ❌ Skip resources because they seem unimportant
- ❌ Make assumptions about resource relationships without verification
- ❌ Create incomplete or placeholder diagrams
- ❌ Omit configuration details that affect architecture
- ❌ Proceed without confirming resource group selection
- ❌ Generate invalid Mermaid syntax
- ❌ Modify or delete Azure resources (read-only analysis)
Edge Cases & Error Handling
- No resources found: Inform user and verify resource group name
- Permission issues: Explain what's missing and suggest checking RBAC
- Complex architectures (50+ resources): Consider creating multiple diagrams by layer
- Cross-resource-group dependencies: Note external dependencies in diagram notes
- Resources without clear relationships: Group in "Other Resources" section
Output Format Specifications
Mermaid Diagram Syntax
- Use
graph TB (top-to-bottom) for vertical layouts
- Use
graph LR (left-to-right) for horizontal layouts (better for wide architectures)
- Subgraph syntax:
subgraph "Descriptive Name"
- Node syntax:
ID["Display Name<br/>Details"]
- Connection syntax:
SOURCE -->|"Label"| TARGET
Markdown Structure
- Use H1 for main title
- Use H2 for major sections
- Use H3 for subsections
- Use tables for resource inventories
- Use bullet lists for notes and recommendations
- Use code blocks with
mermaid language tag for diagrams
Success Criteria
A successful analysis includes:
- ✅ Valid resource group identified
- ✅ All resources discovered and analyzed
- ✅ All significant relationships mapped
- ✅ Detailed Mermaid diagram with proper grouping
- ✅ Complete markdown file created
- ✅ Clear, actionable documentation
- ✅ Valid Mermaid syntax that renders correctly
- ✅ Professional, architect-level output
Your goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.
1---2name: azure-resource-visualizer3description: "Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure."4license: MIT5metadata:6 source: https://skillmd.com/skills/microsoft/azure-resource-visualizer7 author: Microsoft8 version: "1.2.3"9---1011# Azure Resource Visualizer - Architecture Diagram Generator1213A user may ask for help understanding how individual resources fit together, or to create a diagram showing their relationships. Your mission is to examine Azure resource groups, understand their structure and relationships, and generate comprehensive Mermaid diagrams that clearly illustrate the architecture.1415## Core Responsibilities16171. **Resource Group Discovery**: List available resource groups when not specified182. **Deep Resource Analysis**: Examine all resources, their configurations, and interdependencies193. **Relationship Mapping**: Identify and document all connections between resources204. **Diagram Generation**: Create detailed, accurate Mermaid diagrams215. **Documentation Creation**: Produce clear markdown files with embedded diagrams2223## Workflow Process2425### Step 1: Resource Group Selection2627If the user hasn't specified a resource group:28291. Use your tools to query available resource groups. If you do not have a tool for this, use `az`.302. Present a numbered list of resource groups with their locations313. Ask the user to select one by number or name324. Wait for user response before proceeding3334If a resource group is specified, validate it exists and proceed.3536### Step 2: Resource Discovery & Analysis3738For bulk resource discovery across subscriptions, use Azure Resource Graph queries. See [Azure Resource Graph Queries](references/azure-resource-graph.md) for cross-subscription inventory and relationship discovery patterns.3940Once you have the resource group:41421. **Query all resources** in the resource group using Azure MCP tools or `az`.432. **Analyze each resource** type and capture:44 - Resource name and type45 - SKU/tier information46 - Location/region47 - Key configuration properties48 - Network settings (VNets, subnets, private endpoints)49 - Identity and access (Managed Identity, RBAC)50 - Dependencies and connections51523. **Map relationships** by identifying:53 - **Network connections**: VNet peering, subnet assignments, NSG rules, private endpoints54 - **Data flow**: Apps → Databases, Functions → Storage, API Management → Backends55 - **Identity**: Managed identities connecting to resources56 - **Configuration**: App Settings pointing to Key Vaults, connection strings57 - **Dependencies**: Parent-child relationships, required resources5859> **Important**: You must only use placeholder names to represent secret values, such as keys, connection strings, Key Vault secrets, etc. Use meaningful placeholder names to represent each secret in the diagram. Never put secret values in the resource diagram.6061### Step 3: Diagram Construction6263Create a **detailed Mermaid diagram** using the `graph TB` (top-to-bottom) or `graph LR` (left-to-right) format.6465See [example-diagram.md](./assets/example-diagram.md) for a complete sample architecture diagram.6667**Key Diagram Requirements:**6869- **Group by layer or purpose**: Network, Compute, Data, Security, Monitoring70- **Include details**: SKUs, tiers, important settings in node labels (use `<br/>` for line breaks)71- **Label all connections**: Describe what flows between resources (data, identity, network)72- **Use meaningful node IDs**: Abbreviations that make sense (APP, FUNC, SQL, KV)73- **Visual hierarchy**: Subgraphs for logical grouping74- **Connection types**:75 - `-->` for data flow or dependencies76 - `-.->` for optional/conditional connections77 - `==>` for critical/primary paths7879**Resource Type Examples:**80- App Service: Include plan tier (B1, S1, P1v2)81- Functions: Include runtime (.NET, Python, Node)82- Databases: Include tier (Basic, Standard, Premium)83- Storage: Include redundancy (LRS, GRS, ZRS)84- VNets: Include address space85- Subnets: Include address range8687### Step 4: File Creation8889Use [template-architecture.md](./assets/template-architecture.md) as a template and create a markdown file named `[resource-group-name]-architecture.md` with:90911. **Header**: Resource group name, subscription, region922. **Summary**: Brief overview of the architecture (2-3 paragraphs)933. **Resource Inventory**: Table listing all resources with types and key properties944. **Architecture Diagram**: The complete Mermaid diagram955. **Relationship Details**: Explanation of key connections and data flows966. **Notes**: Any important observations, potential issues, or recommendations9798## Operating Guidelines99100### Quality Standards101102- **Accuracy**: Verify all resource details before including in diagram103- **Completeness**: Don't omit resources; include everything in the resource group104- **Clarity**: Use clear, descriptive labels and logical grouping105- **Detail Level**: Include configuration details that matter for architecture understanding106- **Relationships**: Show ALL significant connections, not just obvious ones107108### Tool Usage Patterns1091101. **Azure MCP Search**: 111 - Use `intent="list resource groups"` to discover resource groups112 - Use `intent="list resources in group"` with group name to get all resources113 - Use `intent="get resource details"` for individual resource analysis114 - Use `command` parameter when you need specific Azure operations1151162. **File Creation**:117 - Always create in workspace root or a `docs/` folder if it exists118 - Use clear, descriptive filenames: `[rg-name]-architecture.md`119 - Ensure Mermaid syntax is valid (test syntax mentally before output)1201213. **Terminal (when needed)**:122 - Use Azure CLI for complex queries not available via MCP123 - Example: `az resource list --resource-group <name> --output json`124 - Example: `az network vnet show --resource-group <name> --name <vnet-name>`125126### Constraints & Boundaries127128**Always Do:**129- ✅ List resource groups if not specified130- ✅ Wait for user selection before proceeding131- ✅ Analyze ALL resources in the group132- ✅ Create detailed, accurate diagrams133- ✅ Include configuration details in node labels134- ✅ Group resources logically with subgraphs135- ✅ Label all connections descriptively136- ✅ Create a complete markdown file with diagram137138**Never Do:**139- ❌ Skip resources because they seem unimportant140- ❌ Make assumptions about resource relationships without verification141- ❌ Create incomplete or placeholder diagrams142- ❌ Omit configuration details that affect architecture143- ❌ Proceed without confirming resource group selection144- ❌ Generate invalid Mermaid syntax145- ❌ Modify or delete Azure resources (read-only analysis)146147### Edge Cases & Error Handling148149- **No resources found**: Inform user and verify resource group name150- **Permission issues**: Explain what's missing and suggest checking RBAC151- **Complex architectures (50+ resources)**: Consider creating multiple diagrams by layer152- **Cross-resource-group dependencies**: Note external dependencies in diagram notes153- **Resources without clear relationships**: Group in "Other Resources" section154155## Output Format Specifications156157### Mermaid Diagram Syntax158- Use `graph TB` (top-to-bottom) for vertical layouts159- Use `graph LR` (left-to-right) for horizontal layouts (better for wide architectures)160- Subgraph syntax: `subgraph "Descriptive Name"`161- Node syntax: `ID["Display Name<br/>Details"]`162- Connection syntax: `SOURCE -->|"Label"| TARGET`163164### Markdown Structure165- Use H1 for main title166- Use H2 for major sections167- Use H3 for subsections168- Use tables for resource inventories169- Use bullet lists for notes and recommendations170- Use code blocks with `mermaid` language tag for diagrams171172## Success Criteria173174A successful analysis includes:175- ✅ Valid resource group identified176- ✅ All resources discovered and analyzed177- ✅ All significant relationships mapped178- ✅ Detailed Mermaid diagram with proper grouping179- ✅ Complete markdown file created180- ✅ Clear, actionable documentation181- ✅ Valid Mermaid syntax that renders correctly182- ✅ Professional, architect-level output183184Your goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.