Architecture

This is the most commonly used Combine Network Architecture. In this topology Combine is deployed to a single VNet. Private DNS entries redirect all emulated endpoint traffic to local Combine Endpoint servers. The 'Customer' subnets (reserved for your use) are routed to Combine's Proxy machine which acts as an airgap.

Architecture Diagram

Note that this diagram is for Combine AWS but is analogous to Combine Azure from a networking perspective.

Advantages

• This architecture is simple and very very predictable.

Disadvantages

• None inherently. If your workload spans a single VNet this is the ideal configuration. If your workload spans more than one VPCs then you must use a different topology.

Shared Responsibilities

• None.