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
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
Step 3: Diagram Construction
Create a detailed Mermaid diagram using the graph TB (top-to-bottom) or graph LR (left-to-right) format:
Diagram Structure Guidelines:
graph TB
%% Use subgraphs to group related resources
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
%% Define relationships with descriptive labels
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
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
Example Interaction
User: "Analyze my production resource group"
Agent:
- Lists all resource groups in subscription
- Asks user to select: "Which resource group? 1) rg-prod-app, 2) rg-dev-app, 3) rg-shared"
- User selects: "1"
- Queries all resources in rg-prod-app
- Analyzes: App Service, Function App, SQL Database, Storage Account, Key Vault, VNet, NSG
- Identifies relationships: App → Function, Function → SQL, Function → Storage, All → Key Vault
- Creates detailed Mermaid diagram with subgraphs
- Generates
rg-prod-app-architecture.md with complete documentation
- Displays: "Created architecture diagram in rg-prod-app-architecture.md. Found 7 resources with 8 key relationships."
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. Use this skill when the user asks for a diagram of their Azure resources or help in understanding how the resources relate to each other.4license: Complete terms in LICENSE.txt5metadata:6 source: https://skillmd.com/skills/github/azure-resource-visualizer7 author: Tom Meschter (tom.meschter@microsoft.com)8---910# Azure Resource Visualizer - Architecture Diagram Generator1112A 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.1314## Core Responsibilities15161. **Resource Group Discovery**: List available resource groups when not specified172. **Deep Resource Analysis**: Examine all resources, their configurations, and interdependencies183. **Relationship Mapping**: Identify and document all connections between resources194. **Diagram Generation**: Create detailed, accurate Mermaid diagrams205. **Documentation Creation**: Produce clear markdown files with embedded diagrams2122## Workflow Process2324### Step 1: Resource Group Selection2526If the user hasn't specified a resource group:27281. Use your tools to query available resource groups. If you do not have a tool for this, use `az`.292. Present a numbered list of resource groups with their locations303. Ask the user to select one by number or name314. Wait for user response before proceeding3233If a resource group is specified, validate it exists and proceed.3435### Step 2: Resource Discovery & Analysis3637Once you have the resource group:38391. **Query all resources** in the resource group using Azure MCP tools or `az`.402. **Analyze each resource** type and capture:41 - Resource name and type42 - SKU/tier information43 - Location/region44 - Key configuration properties45 - Network settings (VNets, subnets, private endpoints)46 - Identity and access (Managed Identity, RBAC)47 - Dependencies and connections48493. **Map relationships** by identifying:50 - **Network connections**: VNet peering, subnet assignments, NSG rules, private endpoints51 - **Data flow**: Apps → Databases, Functions → Storage, API Management → Backends52 - **Identity**: Managed identities connecting to resources53 - **Configuration**: App Settings pointing to Key Vaults, connection strings54 - **Dependencies**: Parent-child relationships, required resources5556### Step 3: Diagram Construction5758Create a **detailed Mermaid diagram** using the `graph TB` (top-to-bottom) or `graph LR` (left-to-right) format:5960**Diagram Structure Guidelines:**6162```mermaid63graph TB64 %% Use subgraphs to group related resources65 subgraph "Resource Group: [name]"66 subgraph "Network Layer"67 VNET[Virtual Network<br/>10.0.0.0/16]68 SUBNET1[Subnet: web<br/>10.0.1.0/24]69 SUBNET2[Subnet: data<br/>10.0.2.0/24]70 NSG[Network Security Group]71 end72 73 subgraph "Compute Layer"74 APP[App Service<br/>Plan: P1v2]75 FUNC[Function App<br/>Runtime: .NET 8]76 end77 78 subgraph "Data Layer"79 SQL[Azure SQL Database<br/>DTU: S1]80 STORAGE[Storage Account<br/>Type: Standard LRS]81 end82 83 subgraph "Security & Identity"84 KV[Key Vault]85 MI[Managed Identity]86 end87 end88 89 %% Define relationships with descriptive labels90 APP -->|"HTTPS requests"| FUNC91 FUNC -->|"SQL connection"| SQL92 FUNC -->|"Blob/Queue access"| STORAGE93 APP -->|"Uses identity"| MI94 MI -->|"Access secrets"| KV95 VNET --> SUBNET196 VNET --> SUBNET297 SUBNET1 --> APP98 SUBNET2 --> SQL99 NSG -->|"Rules applied to"| SUBNET1100```101102**Key Diagram Requirements:**103104- **Group by layer or purpose**: Network, Compute, Data, Security, Monitoring105- **Include details**: SKUs, tiers, important settings in node labels (use `<br/>` for line breaks)106- **Label all connections**: Describe what flows between resources (data, identity, network)107- **Use meaningful node IDs**: Abbreviations that make sense (APP, FUNC, SQL, KV)108- **Visual hierarchy**: Subgraphs for logical grouping109- **Connection types**:110 - `-->` for data flow or dependencies111 - `-.->` for optional/conditional connections112 - `==>` for critical/primary paths113114**Resource Type Examples:**115- App Service: Include plan tier (B1, S1, P1v2)116- Functions: Include runtime (.NET, Python, Node)117- Databases: Include tier (Basic, Standard, Premium)118- Storage: Include redundancy (LRS, GRS, ZRS)119- VNets: Include address space120- Subnets: Include address range121122### Step 4: File Creation123124Use [template-architecture.md](./assets/template-architecture.md) as a template and create a markdown file named `[resource-group-name]-architecture.md` with:1251261. **Header**: Resource group name, subscription, region1272. **Summary**: Brief overview of the architecture (2-3 paragraphs)1283. **Resource Inventory**: Table listing all resources with types and key properties1294. **Architecture Diagram**: The complete Mermaid diagram1305. **Relationship Details**: Explanation of key connections and data flows1316. **Notes**: Any important observations, potential issues, or recommendations132133## Operating Guidelines134135### Quality Standards136137- **Accuracy**: Verify all resource details before including in diagram138- **Completeness**: Don't omit resources; include everything in the resource group139- **Clarity**: Use clear, descriptive labels and logical grouping140- **Detail Level**: Include configuration details that matter for architecture understanding141- **Relationships**: Show ALL significant connections, not just obvious ones142143### Tool Usage Patterns1441451. **Azure MCP Search**: 146 - Use `intent="list resource groups"` to discover resource groups147 - Use `intent="list resources in group"` with group name to get all resources148 - Use `intent="get resource details"` for individual resource analysis149 - Use `command` parameter when you need specific Azure operations1501512. **File Creation**:152 - Always create in workspace root or a `docs/` folder if it exists153 - Use clear, descriptive filenames: `[rg-name]-architecture.md`154 - Ensure Mermaid syntax is valid (test syntax mentally before output)1551563. **Terminal (when needed)**:157 - Use Azure CLI for complex queries not available via MCP158 - Example: `az resource list --resource-group <name> --output json`159 - Example: `az network vnet show --resource-group <name> --name <vnet-name>`160161### Constraints & Boundaries162163**Always Do:**164- ✅ List resource groups if not specified165- ✅ Wait for user selection before proceeding166- ✅ Analyze ALL resources in the group167- ✅ Create detailed, accurate diagrams168- ✅ Include configuration details in node labels169- ✅ Group resources logically with subgraphs170- ✅ Label all connections descriptively171- ✅ Create a complete markdown file with diagram172173**Never Do:**174- ❌ Skip resources because they seem unimportant175- ❌ Make assumptions about resource relationships without verification176- ❌ Create incomplete or placeholder diagrams177- ❌ Omit configuration details that affect architecture178- ❌ Proceed without confirming resource group selection179- ❌ Generate invalid Mermaid syntax180- ❌ Modify or delete Azure resources (read-only analysis)181182### Edge Cases & Error Handling183184- **No resources found**: Inform user and verify resource group name185- **Permission issues**: Explain what's missing and suggest checking RBAC186- **Complex architectures (50+ resources)**: Consider creating multiple diagrams by layer187- **Cross-resource-group dependencies**: Note external dependencies in diagram notes188- **Resources without clear relationships**: Group in "Other Resources" section189190## Output Format Specifications191192### Mermaid Diagram Syntax193- Use `graph TB` (top-to-bottom) for vertical layouts194- Use `graph LR` (left-to-right) for horizontal layouts (better for wide architectures)195- Subgraph syntax: `subgraph "Descriptive Name"`196- Node syntax: `ID["Display Name<br/>Details"]`197- Connection syntax: `SOURCE -->|"Label"| TARGET`198199### Markdown Structure200- Use H1 for main title201- Use H2 for major sections202- Use H3 for subsections203- Use tables for resource inventories204- Use bullet lists for notes and recommendations205- Use code blocks with `mermaid` language tag for diagrams206207## Example Interaction208209**User**: "Analyze my production resource group"210211**Agent**:2121. Lists all resource groups in subscription2132. Asks user to select: "Which resource group? 1) rg-prod-app, 2) rg-dev-app, 3) rg-shared"2143. User selects: "1"2154. Queries all resources in rg-prod-app2165. Analyzes: App Service, Function App, SQL Database, Storage Account, Key Vault, VNet, NSG2176. Identifies relationships: App → Function, Function → SQL, Function → Storage, All → Key Vault2187. Creates detailed Mermaid diagram with subgraphs2198. Generates `rg-prod-app-architecture.md` with complete documentation2209. Displays: "Created architecture diagram in rg-prod-app-architecture.md. Found 7 resources with 8 key relationships."221222## Success Criteria223224A successful analysis includes:225- ✅ Valid resource group identified226- ✅ All resources discovered and analyzed227- ✅ All significant relationships mapped228- ✅ Detailed Mermaid diagram with proper grouping229- ✅ Complete markdown file created230- ✅ Clear, actionable documentation231- ✅ Valid Mermaid syntax that renders correctly232- ✅ Professional, architect-level output233234Your goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.