The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
here is my current config
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
We are currently in a hybrid configuration E2019CU15 with O365, trying to migrate mailboxes to O365 we are seeing the error below on all mailboxes we are trying to migrate.
Error: CommunicationErrorTransientException: The call to https://owa.xyz.com/EWS/mrsproxy.svc failed. --> The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate, NTLM'. --> The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate, NTLM'.
Get-WebServicesVirtualDirectory | FL Identity,InternalAuthenticationMethods,ExternalAuthenticationMethods,MRSProxyEnabled
Identity : EXCH01\EWS (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
MRSProxyEnabled : True
Get-WebServicesVirtualDirectory | FL Identity, MRSProxyEnabled Identity : EXCH01\EWS (Default Web Site) MRSProxyEnabled : True
Get-HybridConfiguration | FL Features
Features : {FreeBusy, MoveMailbox, Mailtips, MessageTracking, OwaRedirection, OnlineArchive, SecureMail, Photos}
Thank you!
The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
here is my current config
Hi nettech,
Thank you for posting your question in the Microsoft Q&A forum.
From your description, you’ve already reviewed the relevant MRS settings suggested by Q&A Assist and they look correct so the migration should work, but the error persists. Based on this older but still relevant thread: https://stackoverflow.com/questions/15570108/the-http-request-is-unauthorized-with-client-authentication-scheme-negotiate, the issue may be tied to the EWS authentication configuration in IIS.
Important: This link will take you to Stackoverflow, which is outside Microsoft’s domain. Please note that Microsoft is not responsible for the accuracy, security, or advertising on external sites.
Please open IIS Windows authentication > Providers… and verify that both Negotiate and NTLM are present. Then adjust the provider order (place NTLM at the top), restart IIS (iisreset), and test the migration again.
If the issue persists or you run into any difficulty with these settings, please update this thread and we can help you troubleshoot further.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
The error message you are encountering, "The HTTP request is unauthorized with client authentication scheme 'Negotiate'", typically indicates an issue with the authentication settings for the Exchange Web Services (EWS) in your hybrid environment. Here are some steps you can take to troubleshoot and potentially resolve this issue:
Get-WebServicesVirtualDirectory | FL Identity, MRSProxyEnabled
Make sure the MRSProxyEnabled parameter is set to True.ExternalAuthenticationMethods to ensure that they include methods that are compatible with your setup. You can set the authentication methods using:
Set-WebServicesVirtualDirectory -Identity "EXCH01\EWS (Default Web Site)" -ExternalAuthenticationMethods Ntlm, WSSecurity, OAuth
Get-HybridConfiguration | FL Features
Ensure that the MoveMailbox feature is listed.ServiceModelReg.exe -r command to reinstall the handler mappings in IIS, which can sometimes resolve authentication issues.If you continue to experience problems after these steps, consider consulting the Microsoft Community or Exchange TechNet Forums for further assistance.
References: