Compute Emulator: Allow multiple running emulated deployments to use the same port number
When debugging co-dependent deployments side by side, those deployments cannot use the same port number even though the deployments run on different IP addresses. This forces the developer to use non standard ports on at least one deployment, which when deployed for real causes issues with corporate firewalls blocking access to those ports.
see also https://social.msdn.microsoft.com/Forums/en-US/36224e19-091b-4c61-9b9e-28f0b2e34952/issue-debugging-on-emulator-two-deployments-when-they-both-have-port-443-defined-as-an-endpoint?forum=windowsazuredevelopment
Similar issue here, with another service running on 10.x.y.z:443. In Azure SDK 2.9, the Compute Emulator now refuses to start on 127.x.y.z:443 (this worked in previous SDK versions, although I don't remember which ones exactly).
Instead of "Remapping public port 443 to 444 to avoid conflict during emulation", the Compute Emulator should use port 443, since there is not actual conflict (127.x.y.z:443 is free).