Azure · Editable reference architecture
Azure hub spoke architecture
An editable azure hub spoke architecture reference showing Spoke application → Hub firewall → Spoke database. Make inspected routes explicit.
Open & Edit in DrawArc (Free, No Login Required)Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

6 components · 5 connections · Open the editor to zoom, move nodes and edit source.
Architectural overview
Azure hub spoke architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Spoke application and reaches Spoke database through Hub firewall. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Make inspected routes explicit.
The diagram contains 6 distinct components and 5 directed relationships. A separate path connects On premises → VPN gateway → Hub firewall. A separate path connects Hub DNS → Spoke application. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.
Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Spoke application a bounded dependency timeout and a documented failure response. For Spoke database, specify ownership, retention, access control and a tested recovery procedure. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.
The real-world problem
Design or explain azure hub spoke architecture with explicit ownership and dependency paths. Make inspected routes explicit.
Data flow
Connections from this diagram. Branches and control signals are not a single chronological sequence.
- Spoke application → Hub firewall. Define the interaction contract and trace the resulting response or state change.
- Hub firewall → Spoke database. Define the interaction contract and trace the resulting response or state change.
- On premises → VPN gateway. Define the interaction contract and trace the resulting response or state change.
- VPN gateway → Hub firewall. Define the interaction contract and trace the resulting response or state change.
- Hub DNS → Spoke application. Define the interaction contract and trace the resulting response or state change.
Security boundaries
- Authenticate callers at the boundary before Hub firewall accepts protected work; authorize the specific operation rather than trusting network placement.
- Use separate service identities and least-privilege permissions for Hub firewall, Spoke database, On premises. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
- Restrict and audit access to Spoke database; define retention and deletion requirements for the actual data.
Failure handling
Spoke application is unavailable or slow
Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.
Verify: Interrupt Spoke application in an isolated test and measure errors, recovery and any repeated side effects.
Spoke database loses or returns stale state
Response: Use workload-specific durability, reconciliation and tested recovery. Specify how stale reads or a failed write affect callers.
Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.
An invalid or incompatible input reaches Hub firewall
Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.
Verify: Send malformed and older-version inputs through Spoke application and verify rejection, observability and unchanged valid state.
Trade-offs and alternatives
Make inspected routes explicit.
- Benefit
- Makes the ownership and interaction boundaries visible for a focused design review.
- Cost
- The 6 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
- Alternative
- Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.
Logical boundaries versus deployment units in Azure hub spoke architecture
- Benefit
- Keeps the responsibilities of Spoke application, Hub firewall, Spoke database visible without requiring a separate server for each box.
- Cost
- A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
- Alternative
- Co-locate components in a simpler deployment first when ownership and workload requirements permit it.
When to use this architecture
- Explain azure hub spoke architecture to engineers or stakeholders using a concrete visual flow.
- Review this decision before deployment: Make inspected routes explicit.
- Adapt a starting diagram for your own requirements, then record and validate every changed boundary.
Key components
- Spoke application
- Spoke application participates in azure hub spoke architecture. Spoke application → Hub firewall; Hub DNS → Spoke application. Define its contract, owner and access permissions in your implementation.
- Hub firewall
- Hub firewall participates in azure hub spoke architecture. Spoke application → Hub firewall; Hub firewall → Spoke database; VPN gateway → Hub firewall. Define its contract, owner and access permissions in your implementation.
- Spoke database
- Spoke database participates in azure hub spoke architecture. Hub firewall → Spoke database. Define its contract, owner and access permissions in your implementation.
- On premises
- On premises participates in azure hub spoke architecture. On premises → VPN gateway. Define its contract, owner and access permissions in your implementation.
- VPN gateway
- VPN gateway participates in azure hub spoke architecture. On premises → VPN gateway; VPN gateway → Hub firewall. Define its contract, owner and access permissions in your implementation.
- Hub DNS
- Hub DNS participates in azure hub spoke architecture. Hub DNS → Spoke application. Define its contract, owner and access permissions in your implementation.
Questions about this template
What does this azure hub spoke architecture diagram show?
It shows 6 components with the core flow Spoke application → Hub firewall → Spoke database. Make inspected routes explicit.
Can I edit this diagram without signing in?
Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.
Is this a complete production implementation?
No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.
Validate your implementation
Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.