@MatthiasG If Hyper-V can create a NAT interface based of Pulse client virtual adapter, then it should be possible to make the connection from the Hyper-V guests through that NAT connection or you can bind the virtual adapter to a dummy interface like MSFT loopback interface and then share the internet through inbuilt Internet Connection Sharing service.
@MatthiasG Yeah. bridging with virtual interface will not help to get another IP address for the VM, as there's no DHCP thing to get you another IP from VPN. Hence, VM doesn't get IP address from the internal network like your host does.
As far I see, NAT'ing is the only way of making your VM to communicate with domain network over VPN tunnel through your host machine, otherwise you have to connect to VPN from the VM itself which I think you don't want to.
@shimmer VPN tunnel is enforcing a mode called "Tunnel route precedence" meaning the local subnet routes on the host machine would get pointed over to the tunnel network so no local network access is possible until we disconnect the VPN i.,e, all the traffic destined to the host from the local network are being replied over the virtual interface.
It's a server side configuration which is used to prevent network sharing/file sharing with local devices.
