Previously, there was a description of using the Quagga VM to establish a BGP peer with NVA and RS, but now the tutorial has been changed to use RemoteAccess and Routing on Windows Features.
However, the new article appears to run afoul of Azure VM limitations, as described in the docs below.
Is the procedure described in the new article a supported procedure?
Important
Don't attempt to deploy Remote Access on a virtual machine (VM) in Microsoft Azure. Using Remote Access in Microsoft Azure is not supported. You can't use Remote Access in an Azure VM to deploy VPN, DirectAccess, or any other Remote Access feature in Windows Server. For more information, see Microsoft server software support for Microsoft Azure virtual machines.
I'm questioning the inclusion of deprecated configurations in the following RouteServer's docs. Tutorial: Configure BGP peering between Azure Route Server and NVA | Microsoft Learn
Previously, there was a description of using the Quagga VM to establish a BGP peer with NVA and RS, but now the tutorial has been changed to use RemoteAccess and Routing on Windows Features. However, the new article appears to run afoul of Azure VM limitations, as described in the docs below. Is the procedure described in the new article a supported procedure?
Remote Access | Microsoft Learn
[Microsoft server software support for Microsoft Azure Virtual Machines - Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/server-software-support#windows-server)
Previous article azure-docs/articles/route-server/configure-route-server-with-nva.md at c8162a67087d7316bfffe7455468550e76ad0e92 · MicrosoftDocs/azure-docs New article new article · MicrosoftDocs/azure-docs@c8162a6
author: @halkazwini ms.author: @halkazwini ms.service: azure-route-server ms.topic: tutorial