Hello @Selvaraj
If you have successfully established a Site-to-Site (S2S) VPN connection between your Azure virtual network and your on-premises network, but you are unable to ping the Service Fabric Cluster (SFC) VMSS instance IP address from the on-premises firewall, there are a few things you can check:
Check the network security group (NSG) rules: Make sure that the NSG rules for the SFC VMSS instance allow inbound traffic from the on-premises network. You may need to create a new NSG rule to allow traffic from the on-premises network.
Check the routing table: Make sure that the routing table for the SFC VMSS instance is configured correctly. The routing table should include a route to the on-premises network through the VPN gateway.
Check the VPN gateway configuration: Make sure that the VPN gateway is configured correctly and that the on-premises firewall is configured to allow traffic from the Azure virtual network. You may need to configure the VPN gateway to allow traffic from the on-premises network.
Check the on-premises firewall configuration: Make sure that the on-premises firewall is configured to allow traffic from the Azure virtual network. You may need to create a new firewall rule to allow traffic from the Azure virtual network.
Check the VPN connection status: Make sure that the VPN connection is established and that there are no errors or warnings in the VPN connection logs. You can check the VPN connection status in the Azure portal.
If you have checked all of these items and are still unable to ping the SFC VMSS instance IP address from the on-premises firewall, you may need to contact Microsoft support for further assistance.
If this does answer your question, please accept it as the answer as a token of appreciation.