Many if not all cloud data centers are making this a requirement of setting up IPSEC tunnels. So if you plan to sell to this market you need to add this PRONTO…

1 Like


We don’t have a solid plan to implement this right now but this is definitely on our road map. We will discuss more on this internally here and will provide a update accordingly.

Great… :frowning:

Hi Jeharlan,

One possible solution could be if you can spin up a virtual machine in the cloud service/datacenter, you could utilize Speedfusion VPN with Peplink and FusionHub hosted in the Cloud. This would also provide a much more resilient and seamless failover for connections to your cloud services/APPS when utilizing multiple WAN connections instead of using IPsec.


Hi Jarid. I have also received a request from a client that requires IKEv2 to connect to MS Azure. So it’s a +1 for this feature request.

Hello guys,

I’ve been receiving a lot of requests to connect Peplink to MS Azure infrastructure. This is only possible with IKEv2.

Please share the road map to have this feature available.


According to Azure documentation, their site to site IPsec VPN supports IKEv1, only Dynamic Routing require IKEv2, do you mean you need Dynamic Routing support instead?

1 Like

I agree with adding IKEv2.

And maybe a PepVPN/SpeedFusion resource to the Azure Marketplace, an unbreakable S2S PepVPN between Azure and on-premise.

or FusionHub on Azure Marketplace

I remember reading a documentation that said establishing a VPN to Azure via static routing is possible. I am not able to find anything related to that as well. Please help.


Look like you are looking at the configuration guide for IKEv1 policy-based site to site VPN between Peplink & Azure. Seem Azure is non-validated by Peplink, thus we don’t have the configuration guide for Azure.

Configuring IPSEC IKEv1 at Peplink device is a standard configuration. You may refer to the sample Peplink device IPSEC configuration using the URLs below:

For Azure IPSEC IKEv1 information please refer to the URL below:

Thank You

1 Like


We need IKE v2 support. Because tender specification document require IKE v2 support.
So Can you clarify roadmap?


Can PM me the tender details on IKEv2?

1 Like

are there any updates on when IKEv2 support might be added? It’s been a year since this thread was started so I would hope it would be done very soon. we have an urgent need to connect to an Azure network that is set to dynamic routing, and if Peplink cannot support this soon then we will likely have to get rid of our Peplink device and get something else.

This feature was scheduled after v6.4.0 or later.

Thank you.

What does that mean? Can you give us an estimated date? This year, next year, 2 years??

We have no ETA at the moment. This feature is in our queuing list with medium priority. Thank you for your concern.

It looks like we will have to move away from Peplink then unfortunately. This is standard functionality on any other firewall device, I don’t understand why the Peplink can’t do it. And it should be high priority, not medium.

Thanks for your feedback and we understand if you have to make that move. If it were something that was very simple we would have done it already, but obviously this will need some development resources. Our roadmap is based on demand and unfortunately this has only come up a few times. We appreciate your understanding and hope to win your business back in the future.

+1 to this feature