Enterprise reference design

Hybrid private connectivity with tested routing, DNS and failover

An enterprise ExpressRoute and VPN design that separates transport redundancy, selective inspection, bidirectional DNS and private service authorization.

Enterprise network architectsAzure platform engineersIdentity and security engineersOperations and recovery leads

The enterprise use case

Design for the actual operating context.

A company must connect datacenter applications and administrators to Azure application spokes and private PaaS endpoints. ExpressRoute carries normal production traffic; a separately operated site-to-site VPN preserves a defined subset of services during an ExpressRoute interruption.

Required outcomes

  • Prove both forward and return paths for selected inspected flows.
  • Resolve Azure private endpoints from the datacenter and corporate names from Azure without forwarding loops.
  • Make degraded VPN service explicit and separate it from full regional disaster recovery.
  • Retain identity enforcement and useful evidence across transport changes.

Enterprise architecture

Explore the design, one view at a time.

ExpressRoute and private application connectivity

Follow the selected inspected route, then distinguish the direct private-endpoint path.

Hybrid private connectivity: prove every path — ExpressRoute and private application connectivityFollow the selected inspected route, then distinguish the direct private-endpoint path.. Official Microsoft service icons; explicit resource and network boundaries. Green numbered steps match the F-numbered flow register below the diagram. Hybrid private connectivity: prove every path ExpressRoute and private application connectivity Follow the selected inspected route, then distinguish the direct private-endpoint path. On-premises datacenter Customer-owned routing Connectivity subscription Regional network ownership Hub VNet Gateway and firewall subnets Application subscription Application-owned services Application spoke VNet Runtime and endpoint subnets F1: Primary private peering. Approved datacenter and Azure prefixes exchange over ExpressRoute private peering. Redundant connections at one peering location do not remove location-level failure risk. F2: Selected inspection prefixes. Only traffic deliberately steered by supported prefix-specific routes crosses Firewall. Gateway control-plane dependencies are preserved and the return route is designed symmetrically. F3: Approved app path. Firewall permits the approved source/destination/port path to the spoke. The application still authenticates callers. Corresponding datacenter return prefixes use the same inspection path. F10: Direct private path. The baseline permits direct private endpoint access from the application. Hub Firewall is not claimed to inspect this traffic; additional inspection requires network policies, supported routes and return-path validation. F11: Private service access. Each endpoint targets its approved service subresource. Storage and Key Vault retain independent data authorization and public-network-access settings outside the VNet. Customer edge. ExpressRoute private peering Customer edge ExpressRoute private peering ExpressRoute gateway. ErGw2Az; validate capacity ExpressRoute gateway ErGw2Az; validate capacity Azure Firewall. Selected prefix inspection Azure Firewall Selected prefix inspection Application runtime. Managed identity Application runtime Managed identity Private endpoints. Approved service connections Private endpoints Approved service connections Blob and Key Vault. Managed services outside VNet Blob and Key Vault Managed services outside VNet Primary private peering 1 Selected inspection prefixes 2 Approved app path 3 Direct private path 10 Private service access 11 Inspection coverage is selected BGP and supported prefix routes must preserve both directions. Private-endpoint traffic is direct here; add inspection only through a separately validated topology. Reference design · Microsoft product icons used under Microsoft’s published terms · Numbered steps refer to the accompanying flow register
6 components · 5 numbered connections

Green step numbers match the F-numbered flow register below. Solid boundaries show ownership; dashed blue boundaries show networks. Logical groups are labeled explicitly. Microsoft service icons identify the components.

Hybrid DNS and identity boundaries

Resolve private service names in both directions, then follow separate administrative and workload authority.

Hybrid private connectivity: prove every path — Hybrid DNS and identity boundariesResolve private service names in both directions, then follow separate administrative and workload authority.. Official Microsoft service icons; explicit resource and network boundaries. Green numbered steps match the F-numbered flow register below the diagram. Hybrid private connectivity: prove every path Hybrid DNS and identity boundaries Resolve private service names in both directions, then follow separate administrative and workload authority. On-premises authority Corporate DNS and administration Connectivity subscription Private DNS and conditional forwarding DNS Private Resolver VNet Separate delegated endpoint subnets Application subscription Azure-provided client DNS Application spoke VNet Runtime identity and resolver use Microsoft Entra tenant authority Identity services outside the VNets F6: Service-zone query. Corporate DNS forwards the recommended public service suffix, such as blob.core.windows.net, to the inbound endpoint. Normal service hostnames are retained. F7: Linked private zone. The resolver's VNet links provide access to the relevant private zone and endpoint address. DNS configuration is separate from peering and service authorization. F8: Corporate suffix rule. The runtime uses Azure-provided DNS. A ruleset linked to its VNet selects the corporate suffix and forwards via the associated outbound endpoint; the ruleset is configuration, not a DNS appliance. F9: Corporate DNS query. The outbound endpoint reaches corporate DNS over the permitted hybrid route using UDP/TCP 53. Return routing must work, and no rule may loop the query back to Azure. F12: Activate change role. The authorized operator uses tenant authentication and the configured privileged access process before changing shared routes, DNS or firewall policy. F13: Managed identity token. The workload obtains a service token with its managed identity. Token acquisition is an identity dependency, not proof that data access is authorized or routed through Firewall. Corporate DNS. Corporate DNS suffixes Corporate DNS Corporate DNS suffixes Inbound endpoint. Corporate forwarding target Inbound endpoint Corporate forwarding target Private DNS zones. Resolver and client links Private DNS zones Resolver and client links Outbound endpoint. Reach corporate DNS servers Outbound endpoint Reach corporate DNS servers Forwarding ruleset. Uses outbound endpoint Forwarding ruleset Uses outbound endpoint Application runtime. Normal service hostnames Application runtime Normal service hostnames Network operator. Approved privileged change Network operator Approved privileged change PIM activation. Scoped network and DNS roles PIM activation Scoped network and DNS roles Microsoft Entra ID. Workload token authority Microsoft Entra ID Workload token authority Service-zone query 6 Linked private zone 7 Corporate suffix rule 8 Corporate DNS query 9 Activate change role 12 Managed identity token 13 Links and authorization are explicit VNet peering does not create private-zone or forwarding-ruleset links. Avoid DNS forwarding loops; a private answer or valid token alone does not authorize service data access. Reference design · Microsoft product icons used under Microsoft’s published terms · Numbered steps refer to the accompanying flow register
9 components · 6 numbered connections

Green step numbers match the F-numbered flow register below. Solid boundaries show ownership; dashed blue boundaries show networks. Logical groups are labeled explicitly. Microsoft service icons identify the components.

Reduced-service failover and observable health

Separate backup transport from gateway, network-flow and security evidence.

Hybrid private connectivity: prove every path — Reduced-service failover and observable healthSeparate backup transport from gateway, network-flow and security evidence.. Official Microsoft service icons; explicit resource and network boundaries. Green numbered steps match the F-numbered flow register below the diagram. Hybrid private connectivity: prove every path Reduced-service failover and observable health Separate backup transport from gateway, network-flow and security evidence. Connectivity subscription Resource ownership; network topology is shown in the first view Management subscription Operational collection and alerts Independent internet edge Backup transport ownership Security subscription Selected security evidence F14: Gateway health. Configured gateway diagnostics and metrics feed operations. VPN telemetry and application synthetic tests are additional required sources, with their own collection verification. F16: Configured flow analysis. VNet flow logs are written to the configured storage destination; enabled Traffic Analytics provides supported analysis to operations. Flow metadata is not payload inspection or user attribution. F4: IPsec backup. An independent VPN path advertises the approved backup prefixes. Capacity and essential transaction performance are tested; this is not equivalent to full ExpressRoute service. F5: Backup route. After primary route withdrawal, the selected backup prefixes retain the approved inspection path. Failover and failback require route and application testing; sessions may drop. F15: Security diagnostics. Explicit Firewall diagnostic settings send selected supported categories to the SOC workspace. Resource and identity sources require separate configuration; tenant-wide coverage is not implied. ExpressRoute gateway. Primary transport health ExpressRoute gateway Primary transport health VNet flow-log storage. Configured Traffic Analytics VNet flow-log storage Configured Traffic Analytics Azure Monitor. Operational Log Analytics Azure Monitor Operational Log Analytics VPN edge. Independent IPsec path VPN edge Independent IPsec path VPN gateway. VpnGw2AZ and BGP VPN gateway VpnGw2AZ and BGP Azure Firewall. Selected backup inspection Azure Firewall Selected backup inspection Microsoft Sentinel. Security diagnostic settings Microsoft Sentinel Security diagnostic settings Gateway health 14 Configured flow analysis 16 IPsec backup 4 Backup route 5 Security diagnostics 15 Failover is a measured service commitment VPN preserves only the agreed essential workload. Test throughput, convergence and failback; region recovery additionally needs application, data, DNS and capacity preparation. Reference design · Microsoft product icons used under Microsoft’s published terms · Numbered steps refer to the accompanying flow register
7 components · 5 numbered connections

Green step numbers match the F-numbered flow register below. Solid boundaries show ownership; dashed blue boundaries show networks. Logical groups are labeled explicitly. Microsoft service icons identify the components.

Follow the numbered connections

Flow register

Paths shown in the diagram have the following scope.

FlowFrom → toPurpose and control
F1TrafficExpressRoute customer edge ExpressRoute gatewayPrimary private peering

Approved datacenter and Azure prefixes exchange over ExpressRoute private peering. Redundant connections at one peering location do not remove location-level failure risk.

F2TrafficExpressRoute gateway Azure Firewall StandardSelected inspected prefixes

Only traffic deliberately steered by supported prefix-specific routes crosses Firewall. Gateway control-plane dependencies are preserved and the return route is designed symmetrically.

F3TrafficAzure Firewall Standard Internal API / Azure workerAuthorized application path

Firewall permits the approved source/destination/port path to the spoke. The application still authenticates callers. Corresponding datacenter return prefixes use the same inspection path.

F4RecoveryIndependent VPN edge Route-based VPN gatewayReduced-service IPsec backup

An independent VPN path advertises the approved backup prefixes. Capacity and essential transaction performance are tested; this is not equivalent to full ExpressRoute service.

F5RecoveryRoute-based VPN gateway Azure Firewall StandardConverged backup path

After primary route withdrawal, the selected backup prefixes retain the approved inspection path. Failover and failback require route and application testing; sessions may drop.

F6TrafficCorporate DNS servers Resolver inbound endpointAzure service-zone query

Corporate DNS forwards the recommended public service suffix, such as blob.core.windows.net, to the inbound endpoint. Normal service hostnames are retained.

F7TrafficResolver inbound endpoint Private DNS zone resourcesLinked private-zone answer

The resolver's VNet links provide access to the relevant private zone and endpoint address. DNS configuration is separate from peering and service authorization.

F8TrafficInternal API / Azure worker DNS forwarding rulesetCorporate suffix resolution

The runtime uses Azure-provided DNS. A ruleset linked to its VNet selects the corporate suffix and forwards via the associated outbound endpoint; the ruleset is configuration, not a DNS appliance.

F9TrafficResolver outbound endpoint Corporate DNS serversCorporate DNS query

The outbound endpoint reaches corporate DNS over the permitted hybrid route using UDP/TCP 53. Return routing must work, and no rule may loop the query back to Azure.

F10TrafficInternal API / Azure worker Private endpoint interfacesDirect approved private path

The baseline permits direct private endpoint access from the application. Hub Firewall is not claimed to inspect this traffic; additional inspection requires network policies, supported routes and return-path validation.

F11TrafficPrivate endpoint interfaces Blob Storage + Key VaultPrivate service connection

Each endpoint targets its approved service subresource. Storage and Key Vault retain independent data authorization and public-network-access settings outside the VNet.

F12Identity & controlAuthorized network operator PIM-scoped platform rolesActivate scoped change role

The authorized operator uses tenant authentication and the configured privileged access process before changing shared routes, DNS or firewall policy.

F13Identity & controlInternal API / Azure worker Microsoft Entra IDManaged identity token

The workload obtains a service token with its managed identity. Token acquisition is an identity dependency, not proof that data access is authorized or routed through Firewall.

F14MonitoringExpressRoute gateway Azure Monitor + Log AnalyticsGateway health and diagnostics

Configured gateway diagnostics and metrics feed operations. VPN telemetry and application synthetic tests are additional required sources, with their own collection verification.

F15MonitoringAzure Firewall Standard Microsoft Sentinel workspaceSelected security records

Explicit Firewall diagnostic settings send selected supported categories to the SOC workspace. Resource and identity sources require separate configuration; tenant-wide coverage is not implied.

F16MonitoringVNet flow-log storage Azure Monitor + Log AnalyticsConfigured flow analysis

VNet flow logs are written to the configured storage destination; enabled Traffic Analytics provides supported analysis to operations. Flow metadata is not payload inspection or user attribution.

Assumptions to confirm

  • A single Microsoft Entra tenant governs the platform and application subscriptions.
  • On-premises, hub, DNS and spoke address spaces do not overlap; IPAM allocates future growth ranges.
  • Two customer-edge devices terminate ExpressRoute connectivity; the backup VPN uses independent internet connectivity where feasible.
  • Business owners accept a measured reduced service profile during VPN failover.
  • The baseline uses one Azure region; regional recovery needs a separately prepared target and application data recovery.
  • The workload uses Azure-provided DNS on its spoke and private endpoints for Blob Storage and Key Vault.

This design makes hybrid connectivity an explicit contract between network, DNS, identity and application owners. ExpressRoute, a firewall and a private endpoint solve different problems. Their presence does not demonstrate an inspected, authorized or recoverable end-to-end path. This is a documentation-reviewed reference, with no claim of testing in a customer tenant.

Use case and service contract

A datacenter application calls an Azure-hosted internal API and accesses approved Blob Storage data through a private endpoint. Azure workers also call a corporate service by DNS name. Production normally uses ExpressRoute private peering. VPN failover keeps a small set of essential transactions available; bulk ingestion pauses.

Before implementation, define the permitted source/destination prefixes, ports, identity requirements, throughput, latency, connection concurrency and degraded service list. ExpressRoute redundancy at one peering location does not remove location failure risk. If the business cannot accept VPN performance, use an appropriately resilient multi-location ExpressRoute design instead. Microsoft hybrid failover architecture.

Administrative and resource boundaries

Use the enterprise hierarchy described in the landing-zone foundation. The Connectivity subscription under Platform owns gateways, hub routing, Firewall and shared DNS. An application subscription under the Corp landing-zone archetype owns the spoke, runtime identity and private endpoints. Management owns operational collection; Security owns the Sentinel workspace and investigations.

The Entra tenant is the shared identity authority, outside every VNet. PIM-controlled human roles govern changes to routes, peering, DNS zones and service access. Application deployers cannot edit the shared route policy. Runtime managed identities receive only the required data roles. An optional Identity subscription is needed only for directory workloads such as AD DS, not to provide Entra authentication.

The connectivity view puts managed Storage and Key Vault resources outside the spoke’s VNet boundary. Their endpoint network interfaces are inside the private-endpoint subnet. Network reachability and data authorization remain separate acceptance tests.

Component and sizing decisions

Component Baseline choice Constraint to verify before deployment
ExpressRoute Private peering, redundant customer-edge connectivity, zone-capable gateway Start capacity assessment with ErGw2Az; validate region, actual traffic and connection limits rather than treating a SKU as a guarantee.
Backup VPN Route-based, BGP-enabled VpnGw2AZ, supported generation and Standard public IPs Basic is unsuitable for ExpressRoute coexistence; benchmark real failover traffic and encryption overhead.
Gateway subnet Dedicated GatewaySubnet with reserved growth capacity Coexistence requires /27 or larger; this design reserves /26. Avoid unsupported NSGs and arbitrary default routes on it.
Selective inspection Azure Firewall Standard with explicit prefix routes Premium is a separate decision for IDPS/TLS inspection; neither SKU automatically sees every flow.
Hybrid DNS DNS Private Resolver in a separate shared DNS VNet Separate delegated subnets for inbound and outbound endpoints; this design reserves /26 each.
Private service access Approved Blob and Key Vault private endpoints Correct service subresources, private zones, public-access settings and caller roles are all necessary.

The example gateway names are selection starting points, not a capacity commitment. Current VPN guidance favors AZ SKUs for new deployments; do not copy legacy non-AZ or dynamic-public-IP examples from older deployment snippets. VPN SKU guidance, coexistence requirements.

Keep ExpressRoute FastPath outside this baseline until its changed data path has been reviewed against inspection requirements. Check the selected gateway’s support before adopting it. The separate DNS VNet also avoids placing a resolver with a wildcard forwarding rule in the same VNet as an ExpressRoute gateway, a documented unsupported combination. ExpressRoute gateway constraints.

Ordered flows and route selection

  1. F1–F3: selected production traffic. Customer-edge routers advertise approved datacenter prefixes through ExpressRoute private peering. For flows designated for inspection, prefix-specific routes steer gateway-to-spoke traffic through Firewall; the spoke’s return route sends the corresponding datacenter prefixes through the same firewall. Keep gateway control-plane dependencies intact.
  2. F4–F5: degraded transport. The VPN advertises the approved backup prefixes. Configure customer-edge preference and verify Azure route selection so ExpressRoute is primary and VPN takes over after route withdrawal. Test both directions and actual failback. Existing sessions can drop; a connected tunnel alone is not evidence of working application recovery.
  3. F6–F7: datacenter DNS to Azure. Corporate DNS conditionally forwards the recommended public service zones to the resolver inbound address. The resolver uses the linked private zones and returns the private endpoint address.
  4. F8–F9: Azure DNS to corporate services. A forwarding ruleset linked to the application VNet matches the corporate suffix and uses the outbound endpoint to reach corporate DNS. Configure both UDP and TCP 53 reachability and return routing.
  5. F10–F11: private data access. The application uses its normal Blob or Key Vault hostname and reaches the endpoint NIC. This baseline permits the approved direct private-endpoint path; it does not claim the hub firewall inspects that path.
  6. F12–F13: authorization. Administrators use the tenant’s privileged access process; the application obtains a token for its managed identity. A valid token without the required resource permission still must not grant data access.
  7. F14–F16: operations and security evidence. Gateway health and network telemetry reach operations; configured security diagnostics reach the SOC. These exports are independent of the application request path and must be tested separately.

Route selection uses longest-prefix matching before equal-prefix source precedence. A spoke 0.0.0.0/0 UDR therefore does not automatically override a more-specific BGP route. Peering is not transitive; set and test gateway transit, remote gateway use and forwarded-traffic options for the chosen topology. Compare effective routes on the actual workload NIC with the advertised and learned routes on both gateway paths. Azure routing behavior.

DNS and private endpoint failure boundaries

Use Azure-provided DNS on the application spoke, explicit links to the required private zones, and a forwarding ruleset for corporate suffixes. Link the private zones to the resolver VNet for inbound queries. Private-zone links, ruleset links and network peering are separate configurations. Avoid wildcard forwarding and circular rules between corporate DNS and the inbound endpoint. Resolver architecture, resolver endpoint requirements.

For Blob access, forward blob.core.windows.net from corporate DNS and host the endpoint record in privatelink.blob.core.windows.net. Use the documented Key Vault forwarder zones for its actual hostname. Continue using normal service URLs; do not hard-code endpoint IPs or replace application URLs with private-link names. Private endpoint DNS integration, service zone mapping.

If a policy requires private-endpoint inspection, treat it as an additional design. Enable the appropriate endpoint-subnet network policies, install supported sufficiently specific routes, and prove the return path and source-NAT behavior required by the selected inspection topology. A default route alone does not override the endpoint route. Record exactly which endpoint flows are covered. Private endpoint network policies.

TLS inspection additionally needs a compatible client trust configuration and an operated certificate lifecycle; certificate-pinned applications may need a documented exception. Transport encryption, ExpressRoute private peering, Premium TLS inspection and service authorization are not interchangeable controls. Firewall capabilities.

Monitoring and actionable evidence

Collect subscription change events, supported gateway diagnostics and metrics, firewall rule logs, and the service access logs needed for investigations. Map each source to an expected table and alert owner. Enable resource diagnostic settings explicitly and distinguish them from guest-agent/DCR collection. Diagnostic settings.

Use VNet flow logs for supported traffic, with storage and analysis configured to meet retention needs. Flow metadata cannot establish the authenticated user or prove TLS payload inspection. Check coverage limitations before accepting a blind spot. Flow-log scope.

Send selected security records to a Sentinel workspace in the approved region; tenant-specific SaaS connectors require their own scope review. Alert separately on tunnel/BGP health, application synthetic failure, DNS failures, unexpected route changes and missing telemetry. A quiet firewall is not proof of no traffic if a route bypasses it. Workspace and tenant considerations.

Rollout and adversarial acceptance tests

Deploy address allocation and telemetry first, then private DNS and one nonproduction endpoint. Establish ExpressRoute and VPN before adding selected inspection routes. Expand one source/destination pair at a time and retain a known-good route and DNS configuration for rollback.

Controlled test Acceptance evidence
Resolve the same normal service hostname on premises and in Azure Both approved clients receive the intended private address; resolver and zone ownership are recorded.
Call the service with an unauthorized application identity Data authorization fails despite a working private route.
Withdraw the primary advertised path during an approved exercise The essential transaction succeeds within its agreed recovery window; throughput and dropped sessions are measured.
Restore ExpressRoute Failback follows the intended route preference without sustained asymmetric flows.
Attempt an explicitly blocked source/destination pair Deny is observed at the expected control with no alternate route succeeding.
Break a test forwarding rule and stop a synthetic log source DNS and ingestion alerts reach different accountable owners.

Recovery, ownership and cost tradeoffs

The network team owns circuit/provider escalation, routes and firewall rollback. DNS administrators own zone/ruleset recovery. The application owner owns retries, reduced-mode behavior and data restoration; the SOC owns evidence continuity. Preserve configuration exports and infrastructure definitions outside the failed workload boundary.

VPN backup is not regional disaster recovery. Regional loss requires a prepared alternate network, DNS/endpoint plan, application capacity and restored or replicated data. Rehearse the complete dependency sequence before promising an RTO; route convergence alone does not restore an application.

Budget separately for provider circuits, ExpressRoute and VPN gateways, firewall uptime and processing, resolver endpoints, peering/data transfer, private endpoints, logs and a recovery region. The backup VPN incurs cost while idle. A single peering location plus VPN costs less than stronger private-circuit diversity but accepts reduced service. Compare those options against measured outage impact and traffic requirements instead of an unsupported fixed monthly estimate.

Trace the design decisions

Microsoft architecture & product guidance

  1. Microsoft Learn — ExpressRoute with VPN failover reference architecture ↗
  2. Microsoft Learn — ExpressRoute and site-to-site VPN coexistence ↗
  3. Microsoft Learn — ExpressRoute virtual network gateways ↗
  4. Microsoft Learn — VPN gateway SKUs ↗
  5. Microsoft Learn — Azure virtual network routing ↗
  6. Microsoft Learn — DNS Private Resolver ↗
  7. Microsoft Learn — Hybrid DNS architecture ↗
  8. Microsoft Learn — Private endpoint DNS integration ↗
  9. Microsoft Learn — Private endpoint DNS zones and forwarders ↗
  10. Microsoft Learn — Private endpoint network policies ↗
  11. Microsoft Learn — Azure Firewall SKU features ↗
  12. Microsoft Learn — Diagnostic settings in Azure Monitor ↗
  13. Microsoft Learn — VNet flow logs ↗
  14. Microsoft Learn — Microsoft Sentinel workspace and tenant boundaries ↗

Inspect operational evidence

Supporting Sentinel queries

These are contextual hunting starters, not end-to-end validation of the architecture. Check each query's source tables, collection scope and limitations.

Query library →