Hi Gamal Joseph,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
This suggests that there's a routing issue or a missing configuration that's preventing the traffic from reaching the VM.
Possible causes:
- Missing route propagation: Ensure that the routes from the on-premises network are being propagated to Azure via BGP. Verify that the BGP peering is established, and the routes are being advertised correctly.
- Incorrect subnet configuration: Double-check that the subnet configuration in Azure is correct, and the VM is properly associated with the subnet. Ensure that the subnet is configured to use the correct route table and that the route table is propagating the routes correctly.
- Azure Firewall or NVA configuration: If you're using an Azure Firewall or a Network Virtual Appliance (NVA), ensure that it's configured to allow traffic from the on-premises network to the VM.
- Ensure that the VM's IP address is not private and is reachable from the on-premises network. If the VM's IP address is private, you may need to configure a public IP address or use a load balancer to expose the VM to the on-premises network.
If you are still facing any further issues, please don't hesitate to reach out to us. We are happy to assist you.
Looking forward to your response and appreciate your time on this.
If the above response helps answer your question, remember to "Accept Answer" and "Upvote it" so that others in the community facing similar issues can easily find the solution.
Your contribution is highly appreciated.
Regards,
Ganesh