SOLVED

Exchange ActiveSync issue auto redirection

%3CLINGO-SUB%20id%3D%22lingo-sub-2177722%22%20slang%3D%22en-US%22%3EExchange%20ActiveSync%20issue%20auto%20redirection%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2177722%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Tech%20Community%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20recently%20setup%20Exchange%20Hybrid%20with%20on-premises%20Exchange%202013%20with%20CU23%20for%20a%20customer.%20Customer%20has%20on-premises%20Active%20Directory%20as%20%3CEM%3Eabc.local%3C%2FEM%3E%20and%20two%20primary%20SMTP%20domains%20as%20%3CEM%3Eabc.com%3C%2FEM%3E%20and%20%3CEM%3Exyz.com%3C%2FEM%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEmail%20flow%2C%20mailbox%20move%20and%20rest%20of%20the%20things%20look%20pretty%20good%20but%20for%20users%20having%20SMTP%26nbsp%3B%3CEM%3Eabc.com%3C%2FEM%3E%20can't%20get%20their%20mobile%20app%20auto%20redirected%20to%20Office%20365%20URL.....%20meaning%2C%20as%20soon%20as%20we%20move%20users%20to%20office%20365%20their%20mobile%20devices%20stop%20receiving%20emails%20while%20users%20who%20are%20using%20%3CEM%3Exyz.com%3C%2FEM%3E%20domain%20they%20are%20not%20facing%20this%20issue%20regardless%20of%20Android%20or%20iOS%20device.%20Please%20note%2C%20these%20mobile%20devices%20are%20on%20latest%20OS%20and%20using%20native%20app%20and%20Microsoft%20Outlook%20app.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDuring%20troubleshooting%2C%20we%20found%20out%20that%20Exchange%20Target%20OWA%20URL%20which%20was%20setup%20by%20Hybrid%20Wizard%20is%20appearing%20as%3A%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Foultook.office.com%2Fxyz.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Foultook.office.com%2Fxyz.com%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20suggest%2C%20what%20could%20be%20the%20issue%3F%20Thanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2177722%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2187761%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20ActiveSync%20issue%20auto%20redirection%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2187761%22%20slang%3D%22en-US%22%3EMy%20first%20hunch%20would%20be%20DNS%20-%20I'd%20suggest%20having%20a%20look%20at%20the%20autodiscover.abc.com%20DNS%20record%20to%20see%20if%20that%20resolves%20to%20your%20Exchange%20server%20and%20then%20seeing%20if%20you%20have%20an%20autodiscover.xyz.com%20DNS%20record%20in%20place.%20It%20may%20be%20a%20A%20record%20if%20you%20have%20autodiscover.xyz.com%20on%20your%20Exchange%20server%20certificate%20or%20an%20SRV%20record%20if%20you%20don't.%20Also%20worth%20checking%20out%20if%20you%20have%20any%20autodiscover%20entries%20in%20an%20internal%20DNS%20zone%20if%20you%20are%20using%20split%20DNS.%3CBR%20%2F%3E%3CBR%20%2F%3ECertainly%20worth%20running%20the%20ActiveSync%20and%20DNS%20tests%20from%20the%20connectivity%20analyser%3A%20%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2Fo365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2Fo365%3C%2FA%3E%20to%20see%20if%20it%20kicks%20up%20any%20useful%20information.%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%20worth%20identifying%20if%20there%20is%20any%20issues%20with%20new%20profiles%20on%20the%20mobile%20devices%20and%2For%20connectivity%20with%20Outlook.%20You%20may%20find%20with%20ActiveSync%20that%20the%20credentials%20have%20been%20specified%20as%20domain%5Cusername%20rather%20than%20firstname.lastname%40xyz.com%20which%20Office%20365%20would%20require%20to%20connect.%20In%20which%20case%20either%20update%20the%20credentials%20in%20the%20correct%20format%20or%20possibly%20easier%20for%20users%20-%20delete%20and%20recreate%20the%20profile.%3C%2FLINGO-BODY%3E
Contributor

Hi Tech Community,

 

I recently setup Exchange Hybrid with on-premises Exchange 2013 with CU23 for a customer. Customer has on-premises Active Directory as abc.local and two primary SMTP domains as abc.com and xyz.com.

 

Email flow, mailbox move and rest of the things look pretty good but for users having SMTP abc.com can't get their mobile app auto redirected to Office 365 URL..... meaning, as soon as we move users to office 365 their mobile devices stop receiving emails while users who are using xyz.com domain they are not facing this issue regardless of Android or iOS device. Please note, these mobile devices are on latest OS and using native app and Microsoft Outlook app.

 

During troubleshooting, we found out that Exchange Target OWA URL which was setup by Hybrid Wizard is appearing as: http://oultook.office.com/xyz.com

 

Please suggest, what could be the issue? Thanks.

 

2 Replies
My first hunch would be DNS - I'd suggest having a look at the autodiscover.abc.com DNS record to see if that resolves to your Exchange server and then seeing if you have an autodiscover.xyz.com DNS record in place. It may be a A record if you have autodiscover.xyz.com on your Exchange server certificate or an SRV record if you don't. Also worth checking out if you have any autodiscover entries in an internal DNS zone if you are using split DNS.

Certainly worth running the ActiveSync and DNS tests from the connectivity analyser: https://testconnectivity.microsoft.com/tests/o365 to see if it kicks up any useful information.

Also worth identifying if there is any issues with new profiles on the mobile devices and/or connectivity with Outlook. You may find with ActiveSync that the credentials have been specified as domain\username rather than firstname.lastname@xyz.com which Office 365 would require to connect. In which case either update the credentials in the correct format or possibly easier for users - delete and recreate the profile.
best response confirmed by M. Sheeraz Ansari. (Contributor)
Solution
Thanks for your suggestion, Well, it turns out to be "Default Email address policy" issue. What we observed - as soon as user is migrated to Exchange Online, on-premises user mailbox gets converted to "mail enabled user" …….. due to this, it was getting additional non-routable proxy address as Primary SMTP which was "abc.local"

Interestingly that default policy was not applied but in the background, it was getting applied. Following is reference article that may help someone. Thanks.

Reference link: https://msexperttalk.com/incorrect-email-address-applied-after-mailbox-migrated-to-office-365/