Merge pull request #102219 from msrini-MSFT/patch-97

(AzureCXP) fixes MicrosoftDocs/azure-docs#

Author: PRMerger12

includes/virtual-wan-faq-include.md

@@ -37,9 +37,6 @@ No. You can use any VPN-capable device that adheres to the Azure requirements fo
 
 Software-defined connectivity solutions typically manage their branch devices using a controller, or a device provisioning center. The controller can use Azure APIs to automate connectivity to the Azure Virtual WAN. The automation includes uploading branch information, downloading the Azure configuration, setting up IPSec tunnels into Azure Virtual hubs, and automatically setting up connectivity form the branch device to Azure Virtual WAN. When you have hundreds of branches, connecting using Virtual WAN CPE Partners is easy because the onboarding experience takes away the need to set up, configure, and manage large-scale IPsec connectivity. For more information, see [Virtual WAN partner automation](../articles/virtual-wan/virtual-wan-configure-automation-providers.md).
 
-### Am I required to use a preferred partner device?
-
-No. You can use any VPN-capable device that adheres to the Azure requirements for IKEv2/IKEv1 IPsec support.
 
 ### How is Virtual WAN supporting SD-WAN devices?