Hi Kyle, thanks for the quick reply, really appreciate it.
Maybe I'm misunderstanding this, I was comparing the SM bindings page with our current setup where we have a standalone VPS (not in Azure).
So maybe I should back up a couple of steps.
I'm planning for the new SM server to be hosted in Azure as the first step of our migration from our existing host.
I know that Azure initially blocks outgoing port 25, I'm having a dialog with them about that, but I believe incoming port 25 should be open and I'm trying to confirm this.
Let's say the public IP is 188.8.131.52.
I believe everything in Azure is correctly connecting this to the VM.
The NSG and VM WFAS both have incoming 25 open.
From outside, I can RDP to the VM on 184.108.40.206:3389.
But I cannot telnet 220.127.116.11 25
So I moved to testing locally. Within the VM, I can successfully
telnet localhost 25
(and also via internal IP)
but I still cannot
telnet 18.104.22.168 25
This is what was making me wonder if lack of direct SM binding to this public IP was the difference.
Am I misunderstanding something here?