Hello Amal Karunakaran
I understand that you are experiencing a significant issue with your Azure P2S VPN after upgrading to the VpnGw1 SKU and changing to IKEv2/OpenVPN.
Azure VPN Gateway does not specifically mention a 10–15-minute timeout, but OpenVPN and IKEv2 connections can be affected by NAT timeouts or idle session limits set on client-side firewalls or routers.
Make sure UDP ports 500 and 4500 (for IKEv2) and TCP 443 (for OpenVPN) remain open and are not closed too soon by NAT devices or firewalls.
At times, incorrect MTU (Maximum Transmission Unit) settings may cause fragmentation problems and lead to disconnects. Lowering the MTU value, such as to 1400 or 1300, might help stabilize the connection. Also, setting the MSS (Maximum Segment Size) to just below your MTU can be beneficial.
Also, please try removing and reconfiguring a P2S certificate. Download the latest client file and deploy it on your client machines.
Please make sure that all clients are using OpenVPN 2.4 or later or the Azure VPN Client with TLS version 1.2 or 1.3 enabled.
Check the reference document:
https://learn.microsoft.com/en-us/azure/vpn-gateway/ikev2-openvpn-from-sstp
If PFS is enabled on your on-premises VPN device, it could cause disconnection problems. Try disabling it and update your IPsec policy as needed.
collect the packet captures and check whether the disconnects are caused by NAT timeout, TLS renegotiation, or IKE rekeying. And collect logs and check where this disconnection is occurring.
Check the below document for troubleshooting:
https://learn.microsoft.com/en-us/azure/vpn-gateway/troubleshoot-vpn-with-azure-diagnostics
Hope the above answer helps! Please let us know do you have any further queries.
Please do not forget to "up-vote” wherever the information provided helps you, this can be beneficial to other community members.