If you have no PIP attached or NAT Gateway etc. it will randomly use a PIP from the range in the region, so this will change. If you need to give your external host a fixed IP for an ACL, you should assign an IP to the NIC, or create a NAT gateway for the subnet the VM is in.
Azure VM failing connection on Port 22 to external host with ACL receiving from different IP
Chris Westlake_A
25
Reputation points
Hi, currently have an Azure VM with no PIP attempting to connect to external host on port 22, connection works on port 443, or via browser.
External host has an ACL in place which has whitelisted our public domain IP however they are receiving requests in real time from an address within 51.142.242.0/22 subnet would said address be fixed or change.