Share via

Virtual machine server published with custom ports is not reachable from internet

Kristian Ceranja (Span) 25 Reputation points
2026-02-05T14:15:43.57+00:00

Hello all,

We have one virtual machine published on custom ports (443, 8027, 8383, 8031, 8443) utilizing load balancer with health probes and public frontend IP address. NSG rules are in place, probes are healthy and alive, local firewall on VM is down, ping goes through but those specific ports do not.

This is Microsoft Sponsored Azure sub.

Public DNS is configured and pointing to the public IP address.

We have tried with associating public IP directly to the VM and we tried to setup NAT gateway with the frontend public IP configuration and that setup is also not working.

Kind regards

Azure Load Balancer
Azure Load Balancer

An Azure service that delivers high availability and network performance to applications.

0 comments
Answer accepted by question author
  1. Ravi Varma Mudduluru 9,285 Reputation points Microsoft External Staff Moderator
    2026-02-05T15:14:20.6766667+00:00

    Hello @Kristian Ceranja (Span),

    Thanks for reaching out to Microsoft Q&A.

    As discussed, the issue was related to the NSG rule. The NSG rule works only with private IP addresses; however, the destination IP was configured with a public IP instead of a private IP. After updating the NSG rule to change the destination IP from public to private, you were able to access the application successfully.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    1 person found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.