1
00:00:02,040 --> 00:00:06,200
The next option available to administrators wanting to deploy Always On

2
00:00:06,200 --> 00:00:12,010
VPN infrastructure in Azure is Azure Virtual WAN. Azure Virtual WAN is an

3
00:00:12,010 --> 00:00:17,000
advanced networking capability that's a part of Azure, and it is an

4
00:00:17,000 --> 00:00:20,240
extremely powerful networking platform.

5
00:00:20,240 --> 00:00:23,790
There's a lot of capabilities built into Azure Virtual WAN,

6
00:00:23,790 --> 00:00:27,110
and it is it is a quite compelling solution,

7
00:00:27,110 --> 00:00:31,480
no doubt. The advantages, of course, to using Azure Virtual WAN,

8
00:00:31,480 --> 00:00:37,170
especially considering its use over Azure Virtual Gateway, is

9
00:00:37,170 --> 00:00:40,530
that it has much more scalability and throughput. As you'll

10
00:00:40,530 --> 00:00:44,530
notice later in the demonstration, you'll see that it supports many,

11
00:00:44,530 --> 00:00:48,020
many more concurrent users for point‑to‑site VPN.

12
00:00:48,020 --> 00:00:52,490
The disadvantages, of course, are much like the VPN Gateway in Azure

13
00:00:52,490 --> 00:00:58,110
that it has limited support for Always On VPN and, in fact, even more

14
00:00:58,110 --> 00:01:01,540
limited support than the Azure Virtual Gateway.

15
00:01:01,540 --> 00:01:05,800
In terms of the Azure Virtual WAN, it supports IKEv2 only,

16
00:01:05,800 --> 00:01:11,680
so there's no support for SSTP whatsoever in Azure Virtual WAN. In addition,

17
00:01:11,680 --> 00:01:16,660
much like the Azure Virtual Gateway, it does support single tunnel only,

18
00:01:16,660 --> 00:01:20,740
so you can only deploy a device‑based connection or a user‑based connection.

19
00:01:20,740 --> 00:01:22,640
You cannot deploy both.

20
00:01:22,640 --> 00:01:26,320
In that case, it has the same restrictions as Azure VPN Gateway.

21
00:01:26,320 --> 00:01:28,360
Again, no support for force tunneling,

22
00:01:28,360 --> 00:01:34,990
no support for geographic redundancy. When you implement the Azure Virtual WAN,

23
00:01:34,990 --> 00:01:42,000
you must use the standard SKU, so be aware of that if you decide to go this route.