Azure Resource Visualizer
Turn an Azure resource group inventory into an architecture write-up with Mermaid diagram, relationships, and ops-oriented notes.
Overview
Azure Resource Visualizer is an agent skill most often used in Operate (also Ship launch prep, Build integrations) that formats Azure resource-group architecture as inventory tables, Mermaid diagrams, and relationship na
Install
npx skills add https://github.com/github/awesome-copilot --skill azure-resource-visualizerWhat is this skill?
- Markdown report template with subscription, region, resource count, and generation date
- Resource inventory table columns: name, type, tier/SKU, location, notes
- Embedded Mermaid architecture diagram section
- Dedicated sections for network, data flow, identity & access, and critical dependencies
- Notes & recommendations block for operational observations
- Report sections: Overview, Resource Inventory table, Architecture Diagram (Mermaid), Relationship Details (4 subsections
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know resources exist in Azure but lack a single shareable architecture doc that explains how they connect and who depends on whom.
Who is it for?
Solo builders documenting an existing Azure resource group before handoff, compliance review, or infra troubleshooting.
Skip if: Teams needing automated live discovery with zero input—the skill is a structured reporter; you still source accurate resource data.
When should I use this skill?
You need a standardized Azure resource-group architecture document with diagram and relationship narrative from known subscription resources.
What do I get? / Deliverables
You receive a standardized architecture markdown package suitable for runbooks, audits, and team onboarding, with diagram and dependency narrative slots filled from your inventory.
- Markdown architecture document with Mermaid diagram block
- Resource inventory table and dependency/identity narrative sections
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Operate is the canonical shelf because the skill documents live Azure topology for running systems, not greenfield scaffolding. Infra subphase matches subscription-level resource groups, networking, identity, and dependency ordering called out in the template.
Where it fits
Produce a resource-group brief before paging a vendor about App Service and Function App coupling.
Attach dependency ordering to an on-call doc so engineers know which components to check first.
Ship a launch checklist appendix that shows production Azure layout for stakeholders.
Document how a new API integrates with existing VNet and Key Vault access patterns.
How it compares
Documentation template for Azure topology, not an IaC provisioner or Terraform plan generator.
Common Questions / FAQ
Who is azure-resource-visualizer for?
Indie SaaS founders and small teams operating Azure apps who need human-readable architecture artifacts without building diagrams from scratch in Lucidchart.
When should I use azure-resource-visualizer?
In Operate when mapping prod infra; during Ship launch prep when documenting what you are releasing; during Build integrations when wiring new services into an existing resource group narrative.
Is azure-resource-visualizer safe to install?
The skill describes documentation layout; any subscription access depends on how your agent queries Azure—review scopes and the Security Audits panel on this Prism page.
SKILL.md
READMESKILL.md - Azure Resource Visualizer
# Azure Architecture: [Resource Group Name] **Subscription**: [subscription-name] **Region**: [primary-region] **Resource Count**: [count] **Generated**: [date] ## Overview [2-3 paragraph summary of the architecture, its purpose, and key components] ## Resource Inventory | Resource Name | Type | Tier/SKU | Location | Notes | |--------------|------|----------|----------|-------| | app-prod-001 | App Service | P1v2 | East US | Production web app | | func-prod-001 | Function App | Y1 | East US | Consumption plan | ## Architecture Diagram ```mermaid [full diagram here] ``` ## Relationship Details ### Network Architecture [Describe VNets, subnets, network security] ### Data Flow [Describe how data moves between components] ### Identity & Access [Describe managed identities, key vault access, RBAC] ### Dependencies [Describe critical dependencies and their order] ## Notes & Recommendations [Any observations, potential issues, or suggestions] MIT License Copyright 2025 (c) Microsoft Corporation. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE --- name: azure-resource-visualizer description: 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. license: Complete terms in LICENSE.txt metadata: author: Tom Meschter (tom.meschter@microsoft.com) --- # 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 1. **Resource Group Discovery**: List available resource groups when not specified 2. **Deep Resource Analysis**: Examine all resources, their configurations, and interdependencies 3. **Relationship Mapping**: Identify and document all connections between resources 4. **Diagram Generation**: Create detailed, accurate Mermaid diagrams 5. **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: 1. Use your tools to query available resource groups. If you do not have a tool for this, use `az`. 2. Present a numbered list of resource groups with their locations 3. Ask the user to select one by number or name 4. 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: 1. **Query all resources** in the resource group using Azure MCP tools or `az`. 2. **Analyze each resource** type and capture: - Resource name and type - SKU/tier information -