TCP Load balance with different frontend and backend ports
Currently TCP load balancing requires the frontend and backend listeners to share the same port. It would be useful if the backend port could be different to the frontend.
Is this fixed for External Load balancers?
I have configured the load balancer to instance group which point to the same servers. I am running the backend and UI on 2 different ports when I update the configuration they both point to the same port again. Any update to port on 1 backend will update the port on another as well.
Mike Bryant commented
It's still not supported for ILBs - it only works for endpoints exposed to the public internet
As of 2018 it is not the case: I have just configured my load balancer to listen on 443 and forward to 3389 for remote access from restricted networks - it works.