New
#220
Current Canary is 17624 compiled Mon. Thus for Skippers we are probably looking at 17628/17629 next Weds.
For any command line junkies out there, you'll be glad to know the JPSoftware's free TCC/LE command processor works on 17618 when it failed to run on earlier rs5 and even late rs4 builds. Thanks, Microsoft!
Are you geeks using two factor authentication? In that case, you must create an app password for Outlook.
It's the same with outlook.com / hotmail.com / live.com email addresses. If 2FA is enabled, the normal password does not work in email clients. You must use an app password instead.
Notice that app passwords are individual for each application, one app password for one application on one device. For instance, if you want to use a Gmail or Outlook.com email address both in Outlook 2016 and Windows Mail app, you must create separate app passwords for both, and again new ones if you add same accounts to Outlook 2016 and / or Windows Mail app on another device.
You can create Gmail app passwords signing in here: Account settings
App password for outlook.com or any other Microsoft's email address: Additional security options
Kari
Actually, if you use the 2fa paired with the Microsoft Authenticator app for Android, it works perfectly fine (in the Windows 10 email app) without needing to create a specific app password.
I'll test in Outlook 2016 (Insider Preview) tonight, but I suspect it will be no different.
I'll also test my GMail accounts, as they are set to 2FA with notifications coming directly to my registered Android phones (in basically the same way that the Microsoft Authenticator app works) but IIRC, it worked the last time I tried it before I went back to using the web interface for GMail.
As for iOS devices, I do not know if Microsoft has pushed a similar Authenticator app to them or not, and neither do I know if Google Accounts can be pushed for 2FA onto iOS devices through the Google app or not.