Modern Hybrid with no external access

%3CLINGO-SUB%20id%3D%22lingo-sub-2705621%22%20slang%3D%22en-US%22%3EModern%20Hybrid%20with%20no%20external%20access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2705621%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All.%20We%20have%20an%20on-prem%20Exchange%202016%20infrastructure%20with%20no%20https%20connectivity%20from%20external.%20We%20setup%20the%20Hybrid%20agent%20in%20full%20'modern'%20mode%20for%20this%20reason%20and%20it%20seems%20to%20work%20OK.%20We%20had%20to%20do%20some%20adjustments%20on%20the%20Inbound%20and%20Outbound%20connectors%20to%20route%20mail%20correctly%20and%20have%20successfully%20done%20test%20mailbox%20migrations%20to%20and%20from%20O365.%20We%20aren't%20scheduled%20to%20move%20any%20mailboxes%20to%20the%20cloud%20at%20present%20so%20everything%20is%20staying%20on-prem.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20also%20deployed%20Teams%20to%20a%20pilot%20group%2C%20however%20there%20is%20no%20Calendar%20integration%20and%20users%20cannot%20delegate%20a%20Teams%20meeting%20on%20behalf%20of%20another.%20I%20believe%20(after%20many%20hours%20reading%20various%20posts)%20that%20for%20these%20to%20work%20we%20need%20to%20publish%20our%20internal%20autodiscover%20and%20EWS%20records%20externally%3F%3C%2FP%3E%3CP%3EMy%20question%20then%20is%20can%20this%20be%20worked%20around%20using%20the%20Hybrid%20agent%20somehow%20or%20is%20the%20above%20the%20only%20option%2C%20in%20which%20case%20the%20Modern%20Hybrid%20is%20not%20usable%20and%20we%20might%20as%20well%20use%20Classic%20Hybrid%2C%20assuming%20we%20can%20even%20get%20approval%20to%20publish%20these%20URL's%20externally.%3C%2FP%3E%3CP%3ECheers%20Peter%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2705621%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Emodern%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOAuth%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi All. We have an on-prem Exchange 2016 infrastructure with no https connectivity from external. We setup the Hybrid agent in full 'modern' mode for this reason and it seems to work OK. We had to do some adjustments on the Inbound and Outbound connectors to route mail correctly and have successfully done test mailbox migrations to and from O365. We aren't scheduled to move any mailboxes to the cloud at present so everything is staying on-prem. 

We have also deployed Teams to a pilot group, however there is no Calendar integration and users cannot delegate a Teams meeting on behalf of another. I believe (after many hours reading various posts) that for these to work we need to publish our internal autodiscover and EWS records externally?

My question then is can this be worked around using the Hybrid agent somehow or is the above the only option, in which case the Modern Hybrid is not usable and we might as well use Classic Hybrid, assuming we can even get approval to publish these URL's externally.

Cheers Peter

0 Replies