See Overview of Azure PowerShell for more information about installing the PowerShell cmdlets.
You need to install the Azure Resource Manager PowerShell cmdlets if you don't want to use Cloud Shell in your browser.
If you don't already have an Azure subscription, you can activate your MSDN subscriber benefits or sign up for a free account.
Verify that you have an Azure subscription.
The other properties are the same as the non-active-active gateways.
The gateway SKU must be VpnGw1, VpnGw2, VpnGw3, or HighPerformance (legacy SKU).
You need set the EnableActiveActiveFeature flag.
You need to create two Gateway IP configurations with two public IP addresses.
The key differences between the active-active and active-standby gateways: The following steps configure your Azure VPN gateway in active-active modes. Part 1 - Create and configure active-active VPN gateways The active-active mode is available for all SKUs except Basic. You can combine these together to build a more complex, highly available network topology that meets your needs.
Update an existing VPN gateway from active-standby to active-active, or vice versa.
If you already have a VPN gateway, you can:
Part 3 - Establish active-active VNet-to-VNet connections.
Part 2 - Establish active-active cross-premises connections.
Part 1 - Create and configure your Azure VPN gateway in active-active mode.
This article provides the instructions to set up an active-active cross-premises VPN connection, and active-active connection between two virtual networks. See Highly Available Cross-Premises and VNet-to-VNet Connectivity for an overview of connectivity options and topology. To achieve high availability for cross-premises and VNet-to-VNet connectivity, you should deploy multiple VPN gateways and establish multiple parallel connections between your networks and Azure. About highly available cross-premises connections You can also configure an active-active gateway in the Azure portal. This article walks you through the steps to create active-active cross-premises and VNet-to-VNet connections using the Resource Manager deployment model and PowerShell.