We have an application that we'd like to move up on an Azure VM. But, it needs to be able to accept connections on 2 different ports - the old client port configuration, which we are phasing out but will take another year+, and the new standard port that we are phasing "in".
Example - the new port is 345, the old client port is 9345. The app itself can only accept the connection on one port or the other.
In our current network that work is taken care of by the WAN FW and NAT-ing. So, port 345 is passed straight through to the app, and port 9345 is NAT-ed to 345 and passed to the app as well. Standard functionality for a router/FW.
If I create 2 endpoints for the VM on Azure - 2 different public ports but the same private port - when trying to create the second endpoint it complains that there is a conflict with the protocol and private port, that they already exist, and will not let me create them.
Seems like a basic piece of functionality, maybe overlooked? Is there another method to create them that might not resist, like through PowerShell or a config file upload?