Cisco ASA to Azure virtual network gateway VPN frequent connectivity drop outs

[microensure]

We have an issue where we have setup a VPN between our on-prem network to our new Azure test environment, 

We use a Cisco ASA 5512 on-Prem and connect via Policy based VPN to Azure over the Virtual network gateway, connect comes up and we are able to ping, RDP etc to our VMs.

Every 30 - 60 seconds the connection drops out and we lose RDP, this can be anywhere from 1 second to several minutes.

Sometimes even when the connection comes back up and we try to initiate a ping from Azure VM back to on-prem server it does not work, but When we initiate the ping from on-prem to Azure ping the ping starts working from the other direction.

I have checked the config, removed it and re-added it but are experiencing exactly the same thing.

To add some extra info, we have exactly the same setup to another Azure tenant and subscription from the same ASA and we do not get these dropouts.

Nothing obvious seems to be appearing in the logs, any ideas/clues would be appreciated :)

[Sheraz.Salim]

if you using ikev1 than make sure your life time are same. also you have to make sure you are the initiator and also if possible set up a keep alive from your site. means once the tunnel is up and running from the server the one is specified in interesting traffic set up/run continuous ping to other side. 

[microensure]

I dont believe you can set lifetime on the inbuilt Azure VPN.

Funnily enough when I looked at my logs this morning Im getting these errors:

5	Jul 22 2019	09:30:39	713120	Group = 51.140.227.217, IP = 51.140.227.217, PHASE 2 COMPLETED (msgid=558d3085)
6	Jul 22 2019	09:30:53	713905	Group = 51.140.227.217, IP = 51.140.227.217, Skipping dynamic map SYSTEM_DEFAULT_CRYPTO_MAP sequence 65535: cannot match peerless map when peer found in previous map entry.
3	Jul 22 2019	09:30:53	713061	Group = 51.140.227.217, IP = 51.140.227.217, Rejecting IPSec tunnel: no matching crypto map entry for remote proxy 172.16.0.0/255.255.0.0/0/0 local proxy 192.168.2.0/255.255.255.0/0/0 on interface outside
3	Jul 22 2019	09:30:53	713902	Group = 51.140.227.217, IP = 51.140.227.217, QM FSM error (P2 struct &0x00007fffded33c30, mess id 0x80000000)!
3	Jul 22 2019	09:30:53	713902	Group = 51.140.227.217, IP = 51.140.227.217, Removing peer from correlator table failed, no match!