{"id":11111,"date":"2016-07-07T12:07:51","date_gmt":"2016-07-07T19:07:51","guid":{"rendered":"https:\/\/www.microsoft.com\/insidetrack\/blog\/?p=11111"},"modified":"2023-06-16T16:00:29","modified_gmt":"2023-06-16T23:00:29","slug":"enabling-remote-access-with-windows-hello-for-business-in-windows-10","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/insidetrack\/blog\/enabling-remote-access-with-windows-hello-for-business-in-windows-10\/","title":{"rendered":"Enabling remote access with Windows Hello for Business in Windows 10"},"content":{"rendered":"
\n
\n
<\/div>\n

This content has been archived, and while it was correct at time of publication, it may no longer be accurate or reflect the current situation at Microsoft.<\/p>\n<\/div>\n<\/div>\n

During the internal deployment of Windows 10 November update, Microsoft Digital implemented a new credential, Windows Hello, for strong authentication. We were able to easily incorporate the new credential for use within our existing VPN infrastructure, creating a streamlined sign-in experience for remote access among Windows 10 users.<\/p>\n

With the Windows 10 November update, Microsoft IT enabled Windows Hello as an enterprise credential for our users. Our security policies already enforced secure remote sign in using multi-factor authentication, with smart card or phone verification as the second factor, to connect to corporate resources using VPN (virtual private network).<\/p>\n

On any given weekday at Microsoft, there are roughly 35,000 to 45,000 users connected to the corporate network using VPN. There are 25,000 to 35,000 users connected on the weekends and during non-peak hours. We needed to easily incorporate Windows Hello for Business and enable:<\/p>\n