TCTS SD-WAN and Azure Virtual WAN Standard Offering:

In the standard Azure SD-WAN Virtual WAN offering, thousands of applications can be selected and assigned SLA performance objectives. The SD-WAN edge at any given site will then traffic steer accordingly to the SLA performance objective provisioned by the enterprise subscriber. It should be noted that in the standard model, traffic steering is only unidirectional from any given site towards the Azure cloud. Any returning traffic will not be traffic steered by the cloud, however the path back to any site should follow the originating path so that path unification is maintained. The key value proposition of SD-WAN being built on top of Azure Virtual WAN is the following:

Find more: SD-WAN vs mpls

Value Proposition:

  • Site-to-site, site-to-cloud and device-to-cloud utilizes Azure Virtual WAN including Azure’s global backbone
  • Express Route is fully automated using orchestration, SDN and NFV via TCTS’s patented Virtual Cloud Exchange (VCX) solution offering. Since Express Route requires BGP and possible NATing, all of the routing functions are automated using SDN separation of the control and forwarding planes. A full NFV implementation supporting both BGP control and IP forwarding VNFs are utilized. Both IPv4 and IPv6 are supported.
  • Hybrid MPLS/Internet and all Internet local loops are supported. Smaller sites can use an all Internet approach while larger site can use the hybrid approach.
  • Hybrid Virtual WAN and SD-WAN polices are combined by the SD-WAN edge appliance.
  • No SD-WAN virtual appliances or any additional non-Azure virtual functions are required in the Azure cloud. This makes deployment of SD-WAN for Azure Virtual WAN vastly simple. However, traffic steering is unidirectional only from the site to the cloud.
  • Security functions can we added to any given site SD-WAN implementation and Azure native security function can be invoked in the Azure cloud
  • Each enterprise customer gets their own Azure Virtual WAN hub and Express Route gateway in their own VNET. Any Azure region can be configured using this method and then inter-region routing can be configured utilizing native Azure routing and gateway functions
Or visit this link or this one