SOLVED

Exchange 2016 Hybrid with Exchange Online Archiving

%3CLINGO-SUB%20id%3D%22lingo-sub-271276%22%20slang%3D%22en-US%22%3EExchange%202016%20Hybrid%20with%20Exchange%20Online%20Archiving%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-271276%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20customer%20has%20Exchange%20Server%202016%20CU6%20deployed%20with%20a%20hybrid.%20Archiving%20is%20currently%20not%20working%20to%20Exchange%20Online%20Archives%20for%20all%20users%20(it%20was%20working%20prior%20to%20migrating%20to%20Exchange%202016)%2C%20with%20the%20following%20error%20being%20received%3A%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CEM%3EException%3A%20Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcEwsException%3A%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EELC%20EWS%20failed%20with%20error%20type%3A%20'ArchiveExchangeWebServiceNotAvailable'.%20Message%3A%20Archive%20EWS%20url%20is%26nbsp%3B%3C%2FEM%3E%3CEM%3Eunknown%3C%2FEM%3E.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EI%20found%20a%20link%20to%20a%20Docs%20article%20that%20references%20Exchange%202013%20and%20states%20the%20OAuth%20authentication%20must%20be%20configured%20between%20Exchange%20on-premises%20and%20Exchange%20Online%20(found%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fusing-oauth-authentication-to-support-archiving-in-an-exchange-hybrid-deployment-exchange-2013-help%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E)%2C%20but%20nothing%20about%20Exchange%202016.%20Should%20I%20just%20assume%20this%20is%20the%20case%20for%20Exchange%202016%20as%20well%3F%3C%2FP%3E%3CP%3EI've%20been%20through%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-au%2Foffice365%2Fenterprise%2Fconfigure-exchange-server-for-hybrid-modern-authentication%23add-on-premises-web-service-urls-as-spns-in-azure-ad%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%3C%2FA%3E%20Docs%20article%20and%20confirmed%20that%20OAuth%20is%20not%20configured%20between%20on-premises%20Exchange%20and%20Exchange%20Online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-271276%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-271424%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20Hybrid%20with%20Exchange%20Online%20Archiving%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-271424%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20run%20the%20Hybrid%20Wizard%20to%20get%20Oauth%20enabled.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Our customer has Exchange Server 2016 CU6 deployed with a hybrid. Archiving is currently not working to Exchange Online Archives for all users (it was working prior to migrating to Exchange 2016), with the following error being received: 

Exception: Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcEwsException:
ELC EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'. Message: Archive EWS url is unknown.

I found a link to a Docs article that references Exchange 2013 and states the OAuth authentication must be configured between Exchange on-premises and Exchange Online (found here), but nothing about Exchange 2016. Should I just assume this is the case for Exchange 2016 as well?

I've been through this Docs article and confirmed that OAuth is not configured between on-premises Exchange and Exchange Online.

 

Thanks

1 Reply
Highlighted
Best Response confirmed by Michel de Rooij (MVP)
Solution

Yes, run the Hybrid Wizard to get Oauth enabled.