azure-resource-visualizer

Name: azure-resource-visualizer
Author: microsoft

bymicrosoft· 555 skills

Installs

483k

Stars

1.3k

Forks

219

How to install azure-resource-visualizer?

microsoft/azure-skills/azure-resource-visualizer

$npx -y skills add microsoft/azure-skills --skill azure-resource-visualizer

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Use this skill

Run `npx skills use "https://github.com/microsoft/azure-skills" --skill "microsoft/azure-skills/azure-resource-visualizer"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the whole pack

Use the skills in "https://github.com/microsoft/azure-skills" that are relevant to the current task. Run `npx skills add "https://github.com/microsoft/azure-skills"` and select the relevant skills, then follow their instructions.

Files · 1

View on GitHub

SKILL.md

1	# Azure Resource Visualizer - Architecture Diagram Generator
2
3	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.
4
5	## Core Responsibilities
6
7	1. Resource Group Discovery: List available resource groups when not specified
8	2. Deep Resource Analysis: Examine all resources, their configurations, and interdependencies
9	3. Relationship Mapping: Identify and document all connections between resources
10	4. Diagram Generation: Create detailed, accurate Mermaid diagrams
11	5. Documentation Creation: Produce clear markdown files with embedded diagrams
12
13	## Workflow Process
14
15	### Step 1: Resource Group Selection
16
17	If the user hasn't specified a resource group:
18
19	1. Use your tools to query available resource groups. If you do not have a tool for this, use `az`.
20	2. Present a numbered list of resource groups with their locations
21	3. Ask the user to select one by number or name
22	4. Wait for user response before proceeding
23
24	If a resource group is specified, validate it exists and proceed.
25
26	### Step 2: Resource Discovery & Analysis
27
28	For 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.
29
30	Once you have the resource group:
31
32	1. Query all resources in the resource group using Azure MCP tools or `az`.
33	2. Analyze each resource type and capture:
34	- Resource name and type
35	- SKU/tier information
36	- Location/region
37	- Key configuration properties
38	- Network settings (VNets, subnets, private endpoints)
39	- Identity and access (Managed Identity, RBAC)
40	- Dependencies and connections
41
42	3. Map relationships by identifying:
43	- Network connections: VNet peering, subnet assignments, NSG rules, private endpoints
44	- Data flow: Apps → Databases, Functions → Storage, API Management → Backends
45	- Identity: Managed identities connecting to resources
46	- Configuration: App Settings pointing to Key Vaults, connection strings
47	- Dependencies: Parent-child relationships, required resources
48
49	> 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.
50
51	### Step 3: Diagram Construction
52
53	Create a detailed Mermaid diagram using the `graph TB` (top-to-bottom) or `graph LR` (left-to-right) format.
54
55	See [example-diagram.md](./assets/example-diagram.md) for a complete sample architecture diagram.
56
57	Key Diagram Requirements:
58
59	- Group by layer or purpose: Network, Compute, Data, Security, Monitoring
60	- Include details: SKUs, tiers, important settings in node labels (use `<br/>` for line breaks)
61	- Label all connections: Describe what flows between resources (data, identity, network)
62	- Use meaningful node IDs: Abbreviations that make sense (APP, FUNC, SQL, KV)
63	- Visual hierarchy: Subgraphs for logical grouping
64	- Connection types:
65	- `-->` for data flow or dependencies
66	- `-.->` for optional/conditional connections
67	- `==>` for critical/primary paths
68
69	Resource Type Examples:
70	- App Service: Include plan tier (B1, S1, P1v2)
71	- Functions: Include runtime (.NET, Python, Node)
72	- Databases: Include tier (Basic, Standard, Premium)
73	- Storage: Include redundancy (LRS, GRS, ZRS)
74	- VNets: Include address space
75	- Subnets: Include address range
76
77	### Step 4: File Creation
78
79	Use [template-architecture.md](./assets/template-architecture.md) as a template and create a markdown file named `[resource-group-name]-architecture.md` with:
80
81	1. Header: Resource group name, subscription, region
82	2. Summary: Brief overview of the architecture (2-3 paragraphs)
83	3. Resource Inventory: Table listing all resources with types and key properties
84	4. Architecture Diagram: The complete Mermaid diagram
85	5. Relationship Details: Explanation of key connections and data flows
86	6. Notes: Any important observations, potential issues, or recommendations
87
88	## Operating Guidelines
89
90	### Quality Standards
91
92	- Accuracy: Verify all resource details before including in diagram
93	- Completeness: Don't omit resources; include everything in the resource group
94	- Clarity: Use clear, descriptive labels and logical grouping
95	- Detail Level: Include configuration details that matter for architecture understanding
96	- Relationships: Show ALL significant connections, not just obvious ones
97
98	### Tool Usage Patterns
99
100	1. Azure MCP Search:
101	- Use `intent="list resource groups"` to discover resource groups
102	- Use `intent="list resources in group"` with group name to get all resources
103	- Use `intent="get resource details"` for individual resource analysis
104	- Use `command` parameter when you need specific Azure operations
105
106	2. File Creation:
107	- Always create in workspace root or a `docs/` folder if it exists
108	- Use clear, descriptive filenames: `[rg-name]-architecture.md`
109	- Ensure Mermaid syntax is valid (test syntax mentally before output)
110
111	3. Terminal (when needed):
112	- Use Azure CLI for complex queries not available via MCP
113	- Example: `az resource list --resource-group <name> --output json`
114	- Example: `az network vnet show --resource-group <name> --name <vnet-name>`
115
116	### Constraints & Boundaries
117
118	Always Do:
119	- ✅ List resource groups if not specified
120	- ✅ Wait for user selection before proceeding
121	- ✅ Analyze ALL resources in the group
122	- ✅ Create detailed, accurate diagrams
123	- ✅ Include configuration details in node labels
124	- ✅ Group resources logically with subgraphs
125	- ✅ Label all connections descriptively
126	- ✅ Create a complete markdown file with diagram
127
128	Never Do:
129	- ❌ Skip resources because they seem unimportant
130	- ❌ Make assumptions about resource relationships without verification
131	- ❌ Create incomplete or placeholder diagrams
132	- ❌ Omit configuration details that affect architecture
133	- ❌ Proceed without confirming resource group selection
134	- ❌ Generate invalid Mermaid syntax
135	- ❌ Modify or delete Azure resources (read-only analysis)
136
137	### Edge Cases & Error Handling
138
139	- No resources found: Inform user and verify resource group name
140	- Permission issues: Explain what's missing and suggest checking RBAC
141	- Complex architectures (50+ resources): Consider creating multiple diagrams by layer
142	- Cross-resource-group dependencies: Note external dependencies in diagram notes
143	- Resources without clear relationships: Group in "Other Resources" section
144
145	## Output Format Specifications
146
147	### Mermaid Diagram Syntax
148	- Use `graph TB` (top-to-bottom) for vertical layouts
149	- Use `graph LR` (left-to-right) for horizontal layouts (better for wide architectures)
150	- Subgraph syntax: `subgraph "Descriptive Name"`
151	- Node syntax: `ID["Display Name<br/>Details"]`
152	- Connection syntax: `SOURCE -->\|"Label"\| TARGET`
153
154	### Markdown Structure
155	- Use H1 for main title
156	- Use H2 for major sections
157	- Use H3 for subsections
158	- Use tables for resource inventories
159	- Use bullet lists for notes and recommendations
160	- Use code blocks with `mermaid` language tag for diagrams
161
162	## Success Criteria
163
164	A successful analysis includes:
165	- ✅ Valid resource group identified
166	- ✅ All resources discovered and analyzed
167	- ✅ All significant relationships mapped
168	- ✅ Detailed Mermaid diagram with proper grouping
169	- ✅ Complete markdown file created
170	- ✅ Clear, actionable documentation
171	- ✅ Valid Mermaid syntax that renders correctly
172	- ✅ Professional, architect-level output
173
174	Your goal is to provide clarity and insight into Azure architectures, making complex resource relationships easy to understand through excellent visualization.

6 picks

Type

Run `npx skills use "https://github.com/microsoft/azure-skills" --skill "microsoft/azure-skills/azure-resource-visualizer"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the skills in "https://github.com/microsoft/azure-skills" that are relevant to the current task. Run `npx skills add "https://github.com/microsoft/azure-skills"` and select the relevant skills, then follow their instructions.

azure-resource-visualizer

How to install azure-resource-visualizer?

Related

azure-resource-visualizer

How to install azure-resource-visualizer?

Related