Azure VPN client conflicts with existing company VPNs?
Has anyone had issues with Azure Point-to-Site VPN conflicting with users who already need to use their own company VPN?
We are discussing secure access to an Azure customer environment, but management is worried that if customer users already use their internal company VPN, adding Azure VPN on top could create routing, DNS, or VPN client conflicts.
I am curious how common this actually is in practice. Do users usually manage both without problems, or does it become messy with split tunneling, default routes, DNS resolution, MFA, or VPN client compatibility?
Would be useful to hear real world experience and possible challenges.