Templates / Review pattern
Review the connections in your Azure hub-spoke design.
A hub-spoke review examines shared connectivity in the hub, workload separation in spokes, and the routing, DNS and access controls between them. Prepare your ARM JSON and parameters, inspect the available resource relationships, and verify network behavior against Azure configuration and runtime evidence.
Conceptual topology
Shared hub. Separate workloads.
Hub virtual network
Shared connectivity and services
VNet peering · validate routing and access separately
Spoke A
Workload boundary
Spoke B
Workload boundary
Inputs to prepare
Bring the proposed topology and the source needed to explain it.
- ARM JSON, parameter files and required linked or nested templates.
- Address spaces, peering intent, shared-service placement and DNS requirements.
- The expected traffic paths and environment-specific constraints.
Relationships to inspect
Check whether the visible graph agrees with the intended boundaries and shared services.
- Hub-to-spoke peering and the intended routing path.
- Gateway, firewall and route-table configuration where present.
- Private endpoint and DNS dependencies where included in the source.
Evidence still required
A conceptual topology or imported graph cannot establish effective connectivity.
- Inspect effective routes, network security rules and DNS resolution.
- Test the intended path in the deployed environment before asserting reachability.
Frequently asked questions
No. The diagram illustrates a review pattern. Use an appropriate source template and validate its configuration separately.
No. Check the intended routing design, security controls and actual connectivity. Do not infer reachability from a line in the diagram.
