Azure Diagram

Azure Architecture Diagram Generator

You are creating a professional Azure cloud architecture diagram in SVG format.

User Request

$ARGUMENTS

Instructions

Step 1: Understand the Architecture

Parse the user's request to identify:

• Which Azure services are involved
• The data flow / connections between services
• Logical groupings (e.g., networking, compute, data, security)
• The output file path (default: ./azure-architecture.svg if not specified)

Step 2: Fetch Official Azure Icons

Fetch the official Microsoft Azure architecture icons from the benc-uk/icon-collection GitHub repository. These are the actual icons from the Azure Architecture Icon set.

Base URL: https://raw.githubusercontent.com/benc-uk/icon-collection/master/azure-icons/

For each Azure service in the diagram, fetch its SVG icon from:

Additional icons for Power BI: https://raw.githubusercontent.com/microsoft/PowerBI-Icons/main/SVG/Power-BI.svg

If a specific icon filename returns 404, try variations:

• Add/remove "Azure-" prefix
• Try plural/singular forms
• Check the gallery at https://code.benco.io/icon-collection/azure-icons/

Step 3: Process Fetched Icons

When embedding icons into the diagram SVG:

1. Namespace all gradient/filter/clipPath IDs to avoid conflicts. Each icon's internal id="a", id="b" etc. MUST be renamed to unique IDs like sql_a, cosmos_a, storage_a etc. Update all url(#...) and fill="url(#...)" references accordingly.

2. Place all <defs> (gradients, filters, clipPaths) in a single top-level <defs> block in the output SVG.

3. Scale icons using transform="translate(x, y) scale(s)" on a <g> element wrapping each icon's paths. Icons from benc-uk have an 18x18 viewBox, so scale(2) gives ~36px, scale(2.5) gives ~45px icons.

Step 4: Build the SVG Diagram

Create a complete SVG with:

Design system (Azure-style):

• Font: Segoe UI, Arial, sans-serif
• Primary blue: #0078D4
• Background: #FAFAFA or #F9F9F9
• Card background: #fff with stroke="#E1DFDD" and subtle drop shadow
• Section header colors per domain:
  • Networking: #0078D4 (blue)
  • Compute: #5C2D91 (purple)
  • Data: #0078D4 (blue)
  • AI/ML: #5C2D91 (purple)
  • Security: #D83B01 (dark orange)
  • Integration: #F7630C (orange)
  • DevOps: #107C10 (green)
  • Monitoring: #0078D4 (blue)

Layout structure:

┌─────────────────────────────────────────┐
│ Title Banner (gradient blue header)     │
├─────────────────────────────────────────┤
│                                         │
│  ┌──────┐    ┌──────┐    ┌──────┐      │
│  │ Icon │───>│ Icon │───>│ Icon │      │
│  │ Label│    │ Label│    │ Label│      │
│  └──────┘    └──────┘    └──────┘      │
│       │           │           │         │
│  Grouping boxes with headers            │
│  Flow arrows between components         │
│                                         │
├─────────────────────────────────────────┤
│ Foundation / Infrastructure layer       │
├─────────────────────────────────────────┤
│ Legend                                  │
└─────────────────────────────────────────┘

Each service card pattern:

<g transform="translate(x, y)" filter="url(#shadowSm)">
  <rect width="W" height="H" rx="6" fill="#fff" stroke="#E1DFDD"/>
  <!-- Official Azure icon, scaled -->
  <g transform="translate(8, 8) scale(2.2)">
    <!-- icon paths here -->
  </g>
  <text x="52" y="26" fill="#323130" font-size="11" font-weight="600">Service Name</text>
</g>

Standard defs to always include:

<filter id="shadow" x="-5%" y="-5%" width="115%" height="115%">
  <feDropShadow dx="1" dy="2" stdDeviation="3" flood-color="#000" flood-opacity="0.12"/>
</filter>
<filter id="shadowSm" x="-5%" y="-5%" width="115%" height="115%">
  <feDropShadow dx="0" dy="1" stdDeviation="2" flood-color="#000" flood-opacity="0.08"/>
</filter>
<marker id="arrowR" markerWidth="8" markerHeight="6" refX="8" refY="3" orient="auto">
  <polygon points="0 0, 8 3, 0 6" fill="#0078D4"/>
</marker>

Flow arrows: Use <line> or <path> elements with marker-end="url(#arrowR)", stroke #0078D4, stroke-width 1.5.

Grouping boxes: Use rounded <rect> with colored header bar + white body, similar to Azure portal resource group visualization.

Step 5: Write Output

Save the SVG file to the path specified by the user (or default ./azure-architecture.svg).

Important Rules

1. Always fetch real icons — never use placeholder shapes or hand-drawn approximations.
2. Always namespace gradient IDs — icon SVGs reuse generic IDs like a, b which WILL conflict. Prefix them (e.g., sql_a, cosmos_b).
3. Keep the layout clean — use consistent spacing (16px grid), aligned elements, and clear visual hierarchy.
4. Include a legend explaining color coding.
5. Use proper Azure naming — "Entra ID" (not just "Azure AD"), "Azure Cosmos DB" (not just "Cosmos"), etc.
6. Responsive viewBox — use viewBox on the root SVG, no fixed width/height attributes so it scales.
7. Show data flow — use directional arrows to indicate how data/requests move between services.
8. For fetching icons, fetch multiple icons in parallel using concurrent WebFetch calls to be efficient.
9. When processing fetched SVG content, extract only the inner elements (paths, rects, circles, etc.) and their defs — strip the outer <svg> wrapper.
10. Handle complex icons carefully — some icons (like Power BI) have masks and filters that also need ID namespacing.