An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
What you are seeing in your firewall logs is a packet with a source IP of 40.87.160.0. The destination IP is a private IP in your virtual network, while the source is a public IP, likely assigned to Microsoft or one of their cloud services. Even though the packet shows as coming to your private IP, this doesn’t necessarily mean it originated inside your virtual network—it could be routed through Azure’s infrastructure, which sometimes injects packets for things like health probes, service management, or other platform operations.
The TCP flags show both SYN and ACK set, which is unusual for the start of a new connection (normally a new connection is just SYN). That combination could indicate it’s part of a scanning attempt, a misrouted packet, or some service-level heartbeat or probe. Since your NSG blocks that port, the packet would never reach your VM application anyway, but it can still appear in logs because firewalls log both allowed and blocked traffic depending on configuration.
This does look like “internal” in the sense that Azure’s routing and virtual network architecture often forwards platform-originated traffic to VMs for monitoring or infrastructure purposes. It’s not necessarily malicious, but the fact it comes from a public IP and targets a blocked port is suspicious. If this pattern repeats or originates from multiple external IPs, it’s likely an external scan being stopped by the NSG. You could further validate by checking the Azure NSG flow logs to see whether the packet is being dropped and if the source IP maps to an Azure service tag, which would confirm it is platform traffic.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin