Reputation: 3558
I was using Azure Connect, but found that the new Point-to-Site VPN is replacing Azure Connect. So I have an existing network set up that I want to configure.
However, when I click on the "Configure Point-To-Site connectivity" checkbox, nothing happens.
At the top of the page, it says "The virtual network is in use. Configuration changes are limited to adding new subnets." However, this can't mean that I can't configure the Point-to-Site VPN, since it's supposed to be a replacement for Azure Connect, and Azure Connect let me add computers to this network.
Am I missing something?
Upvotes: 0
Views: 936
Reputation: 8058
It would appear that this is no longer the case. I've just successfully created a new Point-to-Site VPN connection on a virtual network that had existing VMs on it (as well as other external load-balanced endpoints)
Upvotes: 1
Reputation: 3206
Unfortunately, Point-to-Site VPN has to be configured before you deploy any VMs to the virtual network. This also applies to Site-To-Site VPN.
Upvotes: 0