I have a server in house I need to move to Azure. But it's IP address cannot be changed.
I have a site-to-site vpn between my local net and Azure.
So I want to move this server to Azure, but it's IP will be from ranges still used (and cannot be changed either) in my LAN.
The idea would be I would put this server behind a NAT device.
I would then create some VDI infrastructure that referred to a different IP than the server, but was then translated by the NAT device so that the server itself would not be impacted.
Eg. Local IP: 123.123.123.0/24
Local Server: 123.123.123.10 TO BE MOVED to Azure
Azure VDINet: 10.10.100.0/24
Azure ServerNet: 10.10.101.0/24
NAT DEVICE with Two IPs: 10.10.101.1 and 123.123.123.1
NAT Translate 10.10.101.10 to 123.123.123.10
So calls from a VDI device in the Azure VDINET would be to 10.10.101.10 (Can't have them calling back to the original Local IP of 123.123.123.10 because it would try to route that back to my LAN over the site-to-site VPN)
IS this possible?
THe other way I thought of doing this was just putting two network cards (or a loopback) on the server. Make the primary IP address of the server one within my AzureVNET, and the secnd one which goes nowhere except to loopback would be the 123.123.123.10
Looking for ideas. Legacy systems suck to maintain !