From c58f47b24076ba9b206089211e3adc91e8ad718f Mon Sep 17 00:00:00 2001 From: marciocloudflare Date: Tue, 4 Feb 2025 17:33:12 +0000 Subject: [PATCH] refined text --- .../manually/third-party/azure/azure-virtual-wan.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/magic-wan/configuration/manually/third-party/azure/azure-virtual-wan.mdx b/src/content/docs/magic-wan/configuration/manually/third-party/azure/azure-virtual-wan.mdx index 4000a904d96f94..81ec73c4d862ea 100644 --- a/src/content/docs/magic-wan/configuration/manually/third-party/azure/azure-virtual-wan.mdx +++ b/src/content/docs/magic-wan/configuration/manually/third-party/azure/azure-virtual-wan.mdx @@ -91,7 +91,7 @@ To connect your existing VNet to your newly created vHub: ## Configure Magic WAN -When connecting your Azure vHub VPN Gateway to Magic WAN, two Cloudflare tunnels are required to map to the single Azure VPN Gateway Connection created above. This is because Azure VPN Gateways are deployed with two public IP addresses. +When connecting your Azure vHub VPN Gateway to Magic WAN, you need to create two Magic WAN IPsec tunnels to map to the single Azure VPN Gateway Connection created above. This is because Azure VPN Gateways are deployed with two public IP addresses. 1. Create an [IPsec tunnel](/magic-wan/configuration/manually/how-to/configure-tunnels/#add-tunnels) in the Cloudflare dashboard. 2. Make sure you have the following settings: