btahz.blogg.se

The following issues are indications of Microsoft account conflicts:

SYMPTOMS AND VERIFICATION OF THE MICROSOFT ACCOUNT CONFLICT You either have to remove the association between your Hosted Exchange email address and the Microsoft account, or put a registry key in place to tell Outlook NOT to look for Autodiscover settings from Microsoft servers if it has the email address is associated with Microsoft account. To correct this situation, you have two choises. In these cases, Outlook is attempting to redirect to Microsoft’s own Office 365 servers, due to the user’s email address being associated to a Microsoft account. The reason for this is that October update changed the way Microsoft Outlook handdles the Exchange Autodiscover. After the October update Outlook has problems connecting to their original mailbox or setting it up in the first place. For example we have clients who have setup a Microsoft account with their email address (mailbox hosted elsewhere) to use the Microsoft app store, Skype, Volume Licensing Service Center etc. For more information about the Extended protection feature, see Extended Protection for Authentication Overview.We have found that a recent update (October) to Microsoft Outlook 2016 included in Office 365 package, has caused Outlook to insist that IF your email address is linked to a Microsoft account then you must be trying to connect to a Microsoft hosted mailbox instead of one hosted by your service provider or your company. The Extended Protection feature was introduced by a security update in Windows KB970430 and KB973917 to avoid the Credential relay attack or Man in the middle attack. Reset the value of Extended Protection and restart the IIS on Exchange Server 2010:įor example: Set-OWAvirtualdirectory -Server Exch10 -ExtendedProtectionFlags $null -ExtendedProtectionSPNList $null More information The Extended Protection feature is enabled on Exchange Server 2010. Exchange Server 2016 users aren’t affected.įor example, Exchange Server 2010 users trying to sign in to OWA continually receive prompts for credentials, but if all Exchange virtual directories URLs point to Exchange Server 2010, users can sign in to OWA normally.Īdditionally, “401,401,ProtocolError” error is logged in Exchange Server 2016 HttpProxy logs. Services like Autodiscover, Outlook on the web (OWA), Exchange Web Services (EWS) won’t work correctly for users with mailboxes hosted in Exchange Server 2010. In a Microsoft Exchange Server 2010 and Exchange Server 2016 coexistence environment, all Exchange virtual directories URLs point to Exchange Server 2016 (for example, ).

Exchange Server 2016 Exchange Server 2010 More.