Late this afternoon, Microsoft pushed out Windows 10 Mobile Build 15250 to the phones of Fast Ring Windows Insiders across the globe. This build brings the usual list of fixes but also brings a new two-factor authentication unlock mechanism feature, and some improvements to VPN, and AppLocker. Here is what you need to know.
- Two factor Authentication: We are excited to announce that we’ve introduced a two factor authentication unlock mechanism for Windows 10 Mobile. With two factor unlock, an enterprise can enforce an additional security layer to their sensitive data via an MDM policy. Once two factor unlock is enabled, a phone user will have to enter a numeric pin followed by an enterprise-defined factor to unlock the phone. An example of an enterprise-defined factor is a companion device such as an NFC tag which can be used to unlock a phone using our Companion Device Framework sample app and documentation.
- AppLocker Improvements: A number of customers have provided feedback on the warning prompts for apps that are blocked by enterprise policies. We’ve improved the UX and updated the MDM SyncML scripts associated with the policies. Application restrictions can be configured by either the ApplicationManagement CSP or AppLocker CSP.
- VPN Improvements: In the modern corporate workplace, mobility is mainstream and secure access to corporate data via VPN has become the norm. We are bringing a range of improvements and features that enhance the reliability of VPN on Windows 10 Mobile.
- We fixed a regression that was introduced in build 15245 where the fingerprint reader on the HP Elite X3 did not turn on the screen. You needed to turn on the screen before you could use Windows Hello.
- We fixed some issues where the Maps app navigation would start navigating a route and after performing a reroute, would present a list of possible routes instead of adjusting to the current route.
- We also improved map-matching particularly for routes using ferries.
- We fixed an issue where an app using the routing engine (e.g. Maps) would timeout on providing the route if suspended for more than 30 seconds.
- We fixed an issue where tiles on the Start screen would occasionally be blank.
- We fixed an issue where a VPN profile that was created via the VPN Management API would always be a dial-up profile.
- We fixed an issue with the MDM policy used to control Build Flighting by Mobile Enterprise.
- We fixed a couple of navigation issues when changing from highway to highway (occasionally, signposts were copied from the original highway to the destination highway) and highway to non-highway (erroneous instruction to “enter highway”).
- We fixed a rare issue where the user’s call history was shown as corrupt after an upgrade.
As you can tell, the list of fixes is a bit long, this week so Microsoft is obviously working to perfect the Windows 10 Mobile version of the Windows 10 Fall Creators Update. It’s also fitting to see some new features for Windows 10 Mobile for once, even if they are security and enterprise related. Keep your feedback coming to Microsoft! We wish you well in your downloading and invite you to drop us a comment to let us know how the experience is going for you.Further reading: build 15250, Fast Ring, Windows 10 Mobile, Windows Insider