# Visualize Azure Resource Group Architectures

Azure resource relationships can be difficult to review across complex groups. This skill inventories resources and creates structured Mermaid architecture documentation.

## Install

```bash
npx skillstore add microsoft/azure-resource-visualizer
```

## Metadata

- Status: approved
- Slug: microsoft-azure-resource-visualizer
- Version: 0.0.0-placeholder
- Author version: 0.0.0-placeholder
- Skillstore revision: r2
- Version status: valid
- Tree hash: 2d213d52f1aeeea63882ba08638fea0f5ab7074bb6213bc12c8c2798d21b6fc2
- Author: microsoft
- GitHub username: microsoft
- License: MIT
- Repository: https://github.com/microsoft/github-copilot-for-azure/tree/main/plugin/skills/azure-resource-visualizer/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/microsoft-azure-resource-visualizer
- Manifest: https://skillstore.pages.dev/api/skills/microsoft-azure-resource-visualizer/manifest

## Capabilities

- Lists available Azure resource groups and asks the user to select one.
- Inventories resource names, types, SKUs, locations, and important configuration properties.
- Maps verified network, identity, data flow, and dependency relationships.
- Generates Mermaid diagrams grouped by network, compute, data, security, and monitoring layers.
- Creates Markdown documentation with an overview, inventory, diagram, relationship details, and recommendations.

## Use Cases

- Create Architecture Documentation: Generate a current inventory and layered diagram for design reviews, handovers, or system documentation.
- Review Deployment Topology: Map deployed services, network boundaries, and dependencies before operational changes or incident analysis.
- Inspect Identity and Network Paths: Document managed identities, RBAC relationships, private endpoints, subnets, and Key Vault access paths.

## Prompt Templates

### Choose a Resource Group

```
List my available Azure resource groups with locations, then wait for me to select one before creating its architecture diagram.
```

### Document One Resource Group

```
Analyze [resource-group]. Create a Markdown document with an inventory, verified relationships, a layered Mermaid diagram, and concise architecture notes.
```

### Focus on Security Relationships

```
Analyze [resource-group] with emphasis on VNets, subnets, private endpoints, managed identities, RBAC, and Key Vault dependencies. Mark unverified relationships clearly.
```

### Map Cross-Group Dependencies

```
Use Azure Resource Graph across [subscriptions] to inventory [resource-groups]. Create separate layered diagrams and document verified cross-group dependencies and visibility gaps.
```

## Limitations

- Requires authenticated Azure MCP or Azure CLI access with sufficient read permissions.
- Accuracy depends on the resources and properties visible to the current Azure identity.
- Large resource groups may require multiple diagrams to remain readable.
- Cross-resource-group dependencies are documented only when available evidence confirms them.

## Best Practices

- Confirm the Azure subscription and resource group scope before discovery.
- Use placeholders for keys, secrets, connection strings, and other sensitive values.
- Verify each relationship from resource properties before adding it to the diagram.

## Anti Patterns

- Do not include secret values in diagrams, inventories, or notes.
- Do not infer dependencies from naming conventions without supporting Azure configuration.
- Do not run commands that modify or delete Azure resources.

## Security Audit

- Audited at: 2026-07-23T19:27:27.675\+00:00
- Summary: All 39 static findings are false positives caused by private example addresses, Markdown code formatting, Mermaid syntax, and legitimate read-only Azure discovery guidance. No executable Ruby code, malicious reconnaissance, prompt injection, secret exposure, or unsafe command construction was found.

## Stats

- Views: 115
- Downloads: 13
- Favorites: 0
- Popularity score: 0