Hello @Hiran ,
The problem where you are successfully connected to Azure Point to Site VPN but are unable to access the Azure resources via their Private IPs may occur if your VPN client does not get the routes from Azure VPN gateway.
You can browse to %AppData%\Microsoft\Network\Connections\Cm*yourGuid*\routes.txt (C:\Users\userID\AppData\Roaming\Microsoft\Network\Connections\Cm*VPNGuid*\routes.txt) in your client machine and check if you have the routes for your connected Azure Vnet & P2S client address pool added here.
In case you do not see the Azure Vnet address space added here, you can reset Azure VPN gateway to get the routes added. In case you have configured virtual network peering with another Vnet, you have to re-download & re-install the Point-to-Site VPN client on your machine to make sure that the new routes are being used.
Kindly let us know if the above helps or you need further assistance on this issue.
----------------------------------------------------------------------------------------------------------------
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.