{"id":2672,"date":"2020-05-06T10:41:52","date_gmt":"2020-05-06T09:41:52","guid":{"rendered":"http:\/\/blog.repsaj.nl\/?p=2672"},"modified":"2020-05-06T10:42:21","modified_gmt":"2020-05-06T09:42:21","slug":"office365-outlook-keeps-asking-for-credentials-network-style","status":"publish","type":"post","link":"http:\/\/blog.repsaj.nl\/index.php\/2020\/05\/office365-outlook-keeps-asking-for-credentials-network-style\/","title":{"rendered":"[Office365] Outlook keeps asking for credentials, network-style"},"content":{"rendered":"<p>Please note that the solution below\u00a0<em>might not<\/em> apply to your situation, as there are a multitude of reasons why Outlook might keep prompting you for credentials. But I&#8217;ve found the following to work for to separate organizations now so I though it would be worth sharing.<\/p>\n<p>The issue is caused by Microsoft rolling out new policies which require the use of two factor authentication. But at the same time, your Exchange tenant is not set-up to allow the modern-style authentication. This throws users into an authentication loop which they cannot get out of without changing the Exchange configuration. So what do you need to do?<\/p>\n<ul>\n<li>Use the PowerShell Exchange cmdlets to connect to Exchange Online. The details for doing so can be found here:\u00a0<a href=\"https:\/\/docs.microsoft.com\/en-us\/powershell\/exchange\/exchange-online\/connect-to-exchange-online-powershell\/connect-to-exchange-online-powershell?redirectedfrom=MSDN&amp;view=exchange-ps\" target=\"_blank\" rel=\"noopener\">https:\/\/docs.microsoft.com\/en-us\/powershell\/exchange\/exchange-online\/connect-to-exchange-online-powershell\/connect-to-exchange-online-powershell?redirectedfrom=MSDN&amp;view=exchange-ps<\/a>.<\/li>\n<li>Note that you&#8217;ll need to connect with a user which has both administrative privileges over Exchange Online, as well as Azure Active Directory. Either one of those is not sufficient!<\/li>\n<li>Run the following cmdlet:\n<pre class=\"lang:ps decode:true\">Get-OrganizationConfig<\/pre>\n<p>And look for the setting named &#8220;<!--StartFragment --><strong>OAuth2ClientProfileEnabled<\/strong>&#8220;. Chances are that lists as &#8220;False&#8221;, being disabled.<\/p>\n<p><!--EndFragment --><\/li>\n<li>Run\n<pre class=\"lang:ps decode:true \">Set-OrganizationConfig -OAuth2ClientProfileEnabled $true<\/pre>\n<p>To <strong>enable<\/strong> this setting for your organization.<\/li>\n<\/ul>\n<p>This setting affects the ability to use the modern OAuth authentication pop-up (the one you know from the browser with the nice background) instead of the old-fashioned network-style login. And when using two-factor authentication, the modern pop-up is the only one which is compatible.<\/p>\n<p>I found that after enabling the setting it&#8217;s sometimes necessary to close Outlook and reopen it for the prompt to appear. In rare cases we needed to remove the account and re-add it to Outlook. But from that point on things usually started to work.<\/p>\n<p>Oh, and when you&#8217;re at it; enforce multi-factor authentication! Most users are used to it by now from consumer products \/ applications and it really boosts your level of security by a lot. Hope this helps!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Please note that the solution below\u00a0might not apply to your situation, as there are a multitude of reasons why Outlook might keep prompting you for credentials. But I&#8217;ve found the following to work for to separate organizations now so I though it would be worth sharing. The issue is caused by Microsoft rolling out new<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[34],"tags":[78,58],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p3KFR1-H6","_links":{"self":[{"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/posts\/2672"}],"collection":[{"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/comments?post=2672"}],"version-history":[{"count":0,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/posts\/2672\/revisions"}],"wp:attachment":[{"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/media?parent=2672"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/categories?post=2672"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/tags?post=2672"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}