P2S VPN connection status would be helpful

%3CLINGO-SUB%20id%3D%22lingo-sub-2220528%22%20slang%3D%22en-US%22%3EP2S%20VPN%20connection%20status%20would%20be%20helpful%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220528%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20P2S%20VPN%20up%20and%20running%20with%20Virtual%20WAN%20with%20connections%20incoming.%20Am%20I%20missing%20something%2C%20or%20are%20we%20limited%20to%20only%20seeing%20the%20total%20number%20of%20P2S%20connections%3F%20I'd%20really%20like%20to%20see%20which%20connections%20are%20incoming%20to%20help%20with%20troubleshooting.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I have P2S VPN up and running with Virtual WAN with connections incoming. Am I missing something, or are we limited to only seeing the total number of P2S connections? I'd really like to see which connections are incoming to help with troubleshooting.

2 Replies
I believe we can see only a number of connections as of now. would you mind sharing the design?

@ABWaheedIt turns out there are a couple Az Powershell commands which can provide a bit more info. I've tried the two I could find, Get-AzP2sVpnGatewayConnectionHealth and Get-AzP2sVpnGatewayDetailedConnectionHealth. I have not been able to get the latter to work yet, but the first one at least provides the client IPs in addition to the number of connections.

 

As far as the design goes, I created a Virtual WAN (connected to a Virtual Hub and vnet) with an IKEv2, machine cert authenticated user vpn configuration (p2s). Machines connect with always on vpn config and certs delivered by Intune. Not an easy set up by any means, but it works quite nicely.