Hello @Pawaskar, Riyanka Digambar ,
I understand that you have configured forced tunneling on your Azure point-to-Site VPN and are unable to access Internet from your client machine.
You can direct all traffic to the VPN tunnel by advertising 0.0.0.0/1 and 128.0.0.0/1 as custom routes to the clients but please note that Internet connectivity is not provided through the VPN gateway. As a result, all traffic bound for the Internet is dropped.
Hence, you need to introduce another resource such as Azure Firewall or a NVA (Network Virtual Appliance) which can take care of the Internet connectivity.
But there is another limitation on the traditional VPN gateway (when I say traditional VPN gateway, I mean a VPN gateway without Virtual WAN solution, which is deployed directly into a Vnet) as below:
Traditional VPN gateways do not have the EnableInternetSecurity
flag option. This flag is needed and must be set to true for your clients to be properly configured for forced-tunneling/accessing Internet via the VPN gateway.
The P2S VPN gateway under Virtual WAN Hub has the EnableInternetSecurity
option.
So, in order to reach the Internet via Azure P2S VPN gateway, you need to deploy a secured virtual hub with Azure firewall manager and add the P2S VPN Gateway to allow your egress traffic that will be controlled by a firewall policy.
Refer: https://learn.microsoft.com/en-us/azure/firewall-manager/secure-cloud-network
When you secure Internet traffic via Azure Firewall (Firewall Manager), you can advertise the 0.0.0.0/0 route or any custom route to your VPN clients. This makes your clients send the Internet bound traffic to Azure for inspection. Then, firewall SNATs the packet to the Public IP of Azure Firewall for egress to Internet.
To do this, you need to setup an Azure Firewall & then configure a Policy to allow P2S traffic to Internet.
You can also use a NVA instead of Azure Firewall as per your requirement.
To advertise custom route to your VPN clients, refer:
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-p2s-advertise-custom-routes
You can also add the route directly in your downloaded azurevpnconfig.xml file as below:
<clientconfig>
<includeroutes>
<route>
<destination>1.2.3.4</destination><mask>32</mask>
</route>
</includeroutes>
</clientconfig>
You can refer the below doc which explains how to configure forced tunneling for Virtual WAN Point-to-site VPN and take inputs on the configuration: https://learn.microsoft.com/en-us/azure/virtual-wan/how-to-forced-tunnel
Another reference for you: https://learn.microsoft.com/en-us/answers/questions/1178804/public-ip-of-azure-vpn-p2s-and-internet-access-via
Kindly let us know if the above helps or you need further assistance on this issue.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.