Outlook not asking for password how to#
Outlook not asking for password password#
Outlook not asking for password windows#

Leave a comment below or follow me on Twitter ( for additional posts and information on Office 365. As with any Office 365 feature, wait a bit and it will improve… So in the current implementation, it doesn’t look like MFA prompts and the token refresh may be as controlled as people might expect.

MFA prompts will not reoccur on a device until the refresh token is invalid.

Outlook not asking for password password#

Federated password changes do not invalidate the refresh token.A user that acquired a refresh token on the corporate network and then goes off-network will maintain a valid refresh token.The refresh token may be valid up to 90 days.The article “ Frequently Asked Questions about Modern Authentication in Office 2013” provides some important details such as: While the article “ Session Timeouts for Office 365” provides a decent overview on the token process, there are some details missing. Important to understand is how the token refresh works with Modern Authentication. If you’re using AD FS claims, you’ll want to understand how Modern Authentication will impact those rules. If you’re using AD FS, you’ll want to check out KB3052203 for some additional configuration items. On the client side, Office 2016 will use Modern Authentication as first priority and Office 2013 will require a registry change to make it priority. SharePoint Online is enabled by default, Exchange Online can be enabled by tenant administrators and Skype for Business requires a ticket to Microsoft. It appears that Modern Authentication is enabled per-workload in Office 365. In March 2015, a public preview was announced and now the functionality can be enabled on your own and comes with production support. Initially, the list of incompatibilities was pretty lengthy but it’s since been reduced significantly. In the past year or so, updates have been announced where the service side was being updated or the clients were being updated. Going back to early 2014, we’ve been hearing about “Modern Authentication” and how it will solve some of the above issues.

Outlook not asking for password how to#

Discover how to empower innovation from non-traditional developers with the Microsoft Power Platform. Unleash the Potential of Power Platform With a Center of Excellenceīusiness innovation often comes from within. So instead of being able to use the Azure Multi-Factor Authentication feature, your only option is the stop-gap “ App Passwords” feature which is far from great. I refuse to accept that saving credentials in the credential manager is true “single sign-on”, especially given that you’ve entered your login more than once (seemingly breaking the definition of “single”).Īn additional difficulty with the current authentication process is that it doesn’t allow for a good way to implement multi-factor authentication (MFA). The user will have “reduced sign-on” until the next password change at which point the saved credentials are no longer valid.

So upon the next launch of Outlook, the user is not prompted for credentials again but it is because the credentials are stored.

Outlook not asking for password windows#

After the user enters the login and password, there is an option to “save” the credentials using the Windows credential manager.

This is because Outlook is actually doing “basic authentication” to Office 365 and if you look at the traffic flows, Exchange Online is authenticating to your on-premises AD FS on behalf of the user. In the current process, a user launches Outlook and is prompted for his/her Office 365 credentials. Last week Microsoft somewhat quietly updated documentation around “Modern Authentication” which gets us closer to “true” single sign-on.īelow is a link-filled overview of Modern Authentication and how it gets us closer to “true” single sign-on… While it is true that AD FS provides single sign-on for some workloads, I’ve often argued that Outlook, possibly the most popular application used with Office 365, is not single sign-on under any scenario. Many will provide the statement that if you implement AD FS, then you have single sign-on. One of the Office 365 concepts that gets glossed over a bit is “single sign-on”, in particular when it comes to Outlook.