How is this new again?

[vitaprimo]

For years we've been using condition-, location-, connection-triggered Always-On VPN on iOS and some other devices, and, the backend to that was no other than Server 2012 R2...well, at least until it got replace for a lighter platform. The only thing new in these pages is that they tone down a little the relentless push of Azure services. IKEv2 (and related) though good is far from perfect, it has issues with multicast, Dead Peer Detection ironically dies, and a manual redial or change of networks is needed to bring the link back up. Eventually it got replaced for ADFS when it got a tad more user-friendly in WS2016.

Instead of rebranding old technologies, harden Active Directory, make it resilient to the network edge so we can stop adding otherwise unnecessary complexity and expense to our networks.

By the way, if this is official documentation, it's extremely vague. There's a dozen pages more-or-less repeating the same.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4c50c357-dbcc-c94e-e445-b023bd92b586
• Version Independent ID: 7953a501-32bb-e482-e62f-a5a881d6a355
• Content: Feature Comparison of Always On VPN and DirectAccess
• Content Source: WindowsServerDocs/remote/remote-access/vpn/vpn-map-da.md
• Product: windows-server-threshold
• GitHub Login: @shortpatti
• Microsoft Alias: pashort

[ghost]

@MihaiSP, can you triage this issue?

[IngridAtMicrosoft]

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close

[IngridAtMicrosoft]

#please-close