Please be aware that Azure is experiencing a severe shortage of Compute resources. Please reach out to the Combine team for more information on how this might affect you.
Skip to main content

Topology - Multiple VNet

Architecture​

Use this topology when your workload must span multiple VNets.

In this topology, Combine is deployed to each VNet in your workload. Private DNS entries redirect all emulated endpoint traffic to the local Endpoint Servers. The Customer subnets (reserved for your use, see Default VNet) are routed to local Combine Proxy machines, which act as an airgap.

Architecture Diagram​

Multiple VNet Architecture

NOTE: This diagram is for Combine AWS, but from a networking perspective it is analogous to Combine Azure.

Advantages​

  • This architecture is simple and predictable.
  • Each VNet can be configured independently.

Disadvantages​

  • Cloud spend is higher because additional infrastructure is deployed to each VNet.
  • At present, each VNet has its own independent Combine Dashboard, because violation information is not shared between VNets.

Shared Responsibilities​

  • None.
Last updated on by Stephen Mouring