P2S IP address leasing
Currently our P2S model uses a predefined address space, and then VPN clients are assigned an address out of that pool.
This is pretty standard.
What I would like to see is an option to apply lease times to those IP addresses, the same way DHCP normally functions. The reason being most of our VPN connectors are cellular dial-in clients, and they suffer brief disconnects.
Each time they disconnect and reconnect they receive a new IP address, and we have a service running that then has to re-establish where the client's listener port is, and do a bunch of housekeeping to clean up the (now orphan) old connection.
By having even a modest lease time of 5 minutes we could avoid this programmatical overhead, and a reconnected client would simply pick up their same, leased IP address.
We don't want static IP addresses, we don't need reserved IP addresses, but a short lease time to deal with brief disconnects I think would be useful.
Thanks for the feedback Daniel. We currently don’t have support for any kind of IP address assignment policy. We will evaluate this ask.
Kim Raymond commented
Would also help for migrating to Azure SQL Managed Instance using the Database Migration Service. From my local machine, the VPN connection drops and upon reconnecting I get a new IP address which then invalidates the online migration project. We're unable to migrate data using P2S for online migrations.
Aanand Ramachandran commented
Thanks for the feedback Daniel. We currently dont have support for any kind of IP address assignment policy. We will evaluate this ask.