SOLVED

[Solution] Parallel // Provider Exchange & Office 365 // Autodiscovery issue

%3CLINGO-SUB%20id%3D%22lingo-sub-251296%22%20slang%3D%22en-US%22%3E%5BSolution%5D%20Parallel%20%2F%2F%20Provider%20Exchange%20%26amp%3B%20Office%20365%20%2F%2F%20Autodiscovery%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251296%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EEDIT2%3A%20My%20apologies..%26nbsp%3BI%20took%20this%20in%20my%20feverish%20search%20for%20a%20solution%20as%20an%20offical%20support%20forum.%20I'm%20sorry.%20Thanks%20for%20reading%20and%20contribution%20as%20well.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EEDIT%20--%26gt%3B%20THE%20SOLUTION!!!%3C%2FSTRONG%3E%3CEM%3E.%26nbsp%3B%20%2F%2F%20NEXT%20THING%20TO%20COME%20--%26gt%3B%20THE%20PROPER%20SPF%20RECORD%20%3B)%3C%2Fimg%3E%3CSTRONG%3E*%3C%2FSTRONG%3E%3CBR%20%2F%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%5BHKEY_CURRENT_USER%5CSoftware%5CMicrosoft%5COffice%5C16.0%5COutlook%5CAutoDiscover%5D%3C%2FP%3E%3CP%3E%22EnableOffice365ConfigService%22%3Ddword%3A00000001%3CBR%20%2F%3E%22ExcludeLastKnownGoodURL%22%3Ddword%3A00000001%3CBR%20%2F%3E%22ExcludeHttpRedirect%22%3Ddword%3A00000001%3CBR%20%2F%3E%22ExcludeHttpsRootDomain%22%3Ddword%3A00000001%3CBR%20%2F%3E%22ExcludeHttpsAutoDiscoverDomain%22%3Ddword%3A00000001%3C%2FP%3E%3CP%3E%3CSTRONG%3EAND%20you%20must%20be%20logged%20in%20with%20the%20Office%20365%20Tenant%20in%20your%20Office%20Suite%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CEM%3Enot%20sure%20%3CSTRONG%3Ewhat%20exactly%20the%20proper%20key%20for%20surpressing%20this%20wrong%20autodiscvoery%20behaviour%20is%3C%2FSTRONG%3E...%2016.0%20in%20path%20of%20registry%20for%20Outlook%202016%20-%3CSTRONG%3E%20funny%20is%20when%20I%20delete%20the%20keys..%20and%20even%20reconfigure%20mailbox%20no%20autodiscovery%20popups%20are%20comming.%3C%2FSTRONG%3E%20Condition%20is%20that%20I'm%20logged%20in%20with%20the%20Microsoft%20O365%20tennant%20which%20is%20connected%20to%20the%20Mailbox%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EThe%20%3CDOMAIN%3E%20(DNS-record)%20is%20already%20in%20use%20for%20a%26nbsp%3BProvider%20based%20Exchange%20solution%3C%2FDOMAIN%3E%3C%2FSTRONG%3E.%20We%20have%20a%20subsidiary%20that%20%3CSTRONG%3Ewants%20to%20work%20almost%20independently%3C%2FSTRONG%3E.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH2%20id%3D%22toc-hId-1649230753%22%20id%3D%22toc-hId-1735360316%22%3E%3CSTRONG%3Egoal%3A%20have%20a%20%3CEM%3Eedit%3A%3C%2FEM%3E%20%22parallel%20scenario%22%20John%20over%26nbsp%3BO365%20direct%20%2F%20provider%20exchange%20still%20using%20its%20autodiscovery%20service%3C%2FSTRONG%3E%3C%2FH2%3E%3CP%3E%3CSTRONG%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20708px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F49657iE23E04E58716605C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222018-09-12-20-16-42_0001%202.jpg%22%20title%3D%222018-09-12-20-16-42_0001%202.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E(provider%20exchange%20and%20Office%20365%20Exchange)%20-%20DNS%20record%20could%20only%20be%20adjusted%20in%20that%20way%20that%20it%20doesn't%20interfere%20with%20full%20functionality%20of%20the%20Provider%20Exchange%20solution%20our%20Headquarter%20is%20using.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH1%20id%3D%22toc-hId--706412703%22%20id%3D%22toc-hId--620283140%22%3E%3CSTRONG%3EThe%20problem%3A%3C%2FSTRONG%3E%3C%2FH1%3E%3CP%3Eautodiscover.%3CDOMAIN%3E.%3CTLD%3E%26nbsp%3Bof%20the%20Provider%20based%20Exchange%20solution%20kicks%20in.%3C%2FTLD%3E%3C%2FDOMAIN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH1%20id%3D%22toc-hId-1036397632%22%20id%3D%22toc-hId-1122527195%22%3E%3CSTRONG%3Eworkaround%201%20-%20edit%20IP%20in%20hosts%20for%20autodiscover.%3CDOMAIN%3E.%3CTLD%3E%3A%3C%2FTLD%3E%3C%2FDOMAIN%3E%3C%2FSTRONG%3E%3C%2FH1%3E%3CP%3Eedit%20hosts%20vor%20autodiscover.%3CDOMAIN%3E.%3CTLD%3E%20so%20that%20Outlook%20get%20the%20right%20Konfiguration.%20As%20you%20see%20above%20the%20DNS%20of%20the%20%3CDOMAIN%3E%20should%20not%20interfere%20with%20full%20functionality%20for%20our%20HQ.%3C%2FDOMAIN%3E%3C%2FTLD%3E%3C%2FDOMAIN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eresult%20of%20ping%20autodiscover.%3CDOMAIN%3E.%3CTLD%3E%20showed%20the%20adjusted%20IP%20(autodiscover.outlook.com)%20but%20it%20didn't%20worked%20out.%3C%2FTLD%3E%3C%2FDOMAIN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Enslookup%26nbsp%3B%3CSPAN%3Eautodiscover.%3CDOMAIN%3E.%3CTLD%3E%20showed%20Provider%20Exchange%20solution%20-%20so%20it%20thought%20this%20old%20workaround%20did%20not%20work%20here..%3C%2FTLD%3E%3C%2FDOMAIN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH1%20id%3D%22toc-hId--1515759329%22%20id%3D%22toc-hId--1429629766%22%3E%3CSTRONG%3Eworkaround%202%20-%20adjust%20autodiscover%20values%3A%3C%2FSTRONG%3E%3C%2FH1%3E%3CP%3E%3CSTRONG%3EMaybe%20this%20could%20be%20some%20part%20of%20the%20solution%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2212902%2Funexpected-autodiscover-behavior-when-you-have-registry-settings-under%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Eadjust%20autodiscover%20behavior%20in%20registry.%20adjust%20values%20under%20HKEY_CURRENT_USER%5CSoftware%5CMicrosoft%5COffice%5C16.0%5COutlook%5CAutoDiscover%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3ESCP%20lookup%3C%2FLI%3E%3CLI%3EHTTPS%20root%20domain%20query%3C%2FLI%3E%3CLI%3EHTTPS%20Autodiscover%20domain%20query%3C%2FLI%3E%3CLI%3ELocal%20XML%20file%3C%2FLI%3E%3CLI%3EHTTP%20redirect%20method%3C%2FLI%3E%3CLI%3ESRV%20record%20query%3C%2FLI%3E%3CLI%3ECached%20URL%20in%20the%20Outlook%20profile%20(new%20for%20Outlook%202010%20version%2014.0.7140.5001%20and%20later%20versions)%3C%2FLI%3E%3CLI%3EDirect%20Connect%20to%20Office%20365%20(new%20for%20Outlook%202016%20version%2016.0.6741.2017%20and%20later%20versions)%3C%2FLI%3E%3C%2FUL%3E%3CH1%20id%3D%22toc-hId-227051006%22%20id%3D%22toc-hId-313180569%22%3E%3CSTRONG%3Eworkaround%203%3A%20seemed%20promising%3C%2FSTRONG%3E%3C%2FH1%3E%3CP%3Eafter%20I%20logged%20out%20with%20the%20Office%20365%20Account%20in%20Office%20which%20has%20the%20Mailbox%20connected%20and%20logged%20in%20again%20I%20somehow%20managed%20to%20get%20the%20login%20screen.%20%3CSTRONG%3EJust%20seems%20like%20Outlook%20then%20connects%20somehow%20directly%20to%20Office%20365%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3Ebut%26nbsp%3Bstill%20some%20popups%20for%20credentials%2C%20and%20some%20autodiscovery%20popup%20from%20the%20provider%20exchange%20solution.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EiOS%20Devices%20seems%20to%20use%20the%20or%20a%20direct%20method...%20there%20is%20no%20interference%20with%20the%20autodiscovery.%3CDOMAIN%3E.%3CTLD%3E%3C%2FTLD%3E%3C%2FDOMAIN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH1%20id%3D%22toc-hId-1969861341%22%20id%3D%22toc-hId-2055990904%22%3EPlease%20help%20me%20find%20a%20stable%20and%20Poupfree%20solution.%3C%2FH1%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreetings%2C%3C%2FP%3E%3CP%3EBenjamin%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-251296%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAutodiscovery%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%20O365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253372%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253372%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EMy%20apologies..%26nbsp%3BI%20took%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ethis%20in%20my%20feverish%20search%20for%20a%20solution%20as%20an%20offical%20support%20forum.%20I'm%20sorry.%20Thanks%20for%20reading%20and%20contribution%20as%20well.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252436%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252436%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F190433%22%20target%3D%22_blank%22%3E%40Benjamin%20Riedel%3C%2FA%3E%2C%20this%20is%20NOT%20a%20support%20forum%2Fchannel.%20We%20are%20just%20fellow%20IT%20Pros%20discussing%20different%20topic%20and%20occasionally%20helping%20each%20other.%20If%20you%20want%20to%20address%20specific%20issue%20to%20official%20Office%20365%20support%2C%20open%20a%20ticket%20from%20the%20portal%20or%20call%20them%20directly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGlad%20the%20issue%20was%20solved%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252408%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252408%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EFound%20it%20after%2018%20hours%20%3B)%3C%2Fimg%3E%20This%20was%20a%20very%20helpful%20link%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3211279%2Foutlook-2016-implementation-of-autodiscover%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EVERY%20HELPFUL%20LINK%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EEDIT%20--%26gt%3B%20THE%20SOLUTION!!!%20%2F%20it%20only%20works%20when%20login%20with%20the%20tenant..%20user%40xyz.onmicrosoft.com%20or%20when%20you%20changed%20primary%20email%20to%20user%40%3CDOMAIN%3E.%3CTLD.%3E%20it%20is%20till%20working.%20-------%26gt%3B%20AND!!!%20Made%20some%20registry%20tweaks%20see%20below%3CEM%3E%3CBR%20%2F%3E%3C%2FEM%3E%3C%2FTLD.%3E%3C%2FDOMAIN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CEM%3Enot%20sure%20what%20exactly%20the%20proper%20key%20is...%2016.0%20stands%20for%20Outlook%202016%20-%20funny%20is%20when%20I%20delete%20the%20keys..%20and%20even%20reconfigure%20mailbox%20no%20autodiscovery%20popups%20are%20comming.%20Condition%20is%20that%20I'm%20logged%20in%20with%20the%20Microsoft%20O365%20tennant%20which%20is%20connected%20to%20the%20Mailbox.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%5BHKEY_CURRENT_USER%5CSoftware%5CMicrosoft%5COffice%5C16.0%5COutlook%5CAutoDiscover%5D%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%22EnableOffice365ConfigService%22%3Ddword%3A00000001%22ExcludeLastKnownGoodURL%22%3Ddword%3A00000001%22ExcludeHttpRedirect%22%3Ddword%3A00000001%22ExcludeHttpsRootDomain%22%3Ddword%3A00000001%22ExcludeHttpsAutoDiscoverDomain%22%3Ddword%3A00000001%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252336%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252336%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20want%20to%20be%20rude%20or%20something%20like%20that..%20I%20already%20spent%2015%20hours%20on%20this%20issue..%20still%20no%20solution.%20And%20got%20only%20things%20told%20that%20I%20already%20did%20and%20wrote%20in%20my%20post.%3CBR%20%2F%3EI%20have%20a%20business%20running%20and%20I%20need%20professional%20%3CTIMESAVING%3E%20support.%20Is%20this%20an%20official%20Microsoft%20Support%20Forum.%20Or%20have%20I%20the%20wrong%20expectations%3F%3C%2FTIMESAVING%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252101%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252101%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20this%20behaviour%20in%20the%20following%20link%20I%20want%20-%20as%20here%20described%20it%20shows%20how%20to%20deactivate%20this%20behaviour!%20And%20it%20is%20still%20working%20and%20I%20don't%20wan't%20to%20deactivate%20this%20feature!%20I%20don't%20want%20to%20have%20the%20popups%20autodiscovery%20kicks%20in.%20%3CSTRONG%3ELike%20an%20inverted%20solution%20to%20this%20solution%20in%20the%20link.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.gothamweb.com%2Fportal%2Findex.php%2Fknowledgebase%2F8%2FOutlook-bypasses-AutoDiscover-and-connects-directly-to-Office-365-mailbox.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOutlook%20bypasses%20AutoDiscover%20and%20connects%20directly%20to%20Office%20365%20mailbox%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Every%20helpful%20too%20goot%20collection%20of%20helpful%20links%20but%20I%20don't%20got%20it%20working.%20Sad%2C%20so%20sad.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.anywherexchange.com%2F2014%2F05%2Fdisable-autodiscover-lookup-for-outlook.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EGood%20description%20of%20the%20behaviour%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20us%20see%20I%20did%20a%20lot%20of%20reading%203%20day%20ago%20but%20it%20didn't%20worked%20out.%20Maybe%20I%20did%20a%20wrong%20registry%20setup%3F%3F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F49665i73F4E35CAC4F4C9B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Screenshot%202018-09-13%2008.59.50.png%22%20title%3D%22Screenshot%202018-09-13%2008.59.50.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252091%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252091%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20than%20that%2C%20I%20can%20think%20of%26nbsp%3Bfew%20more%20factors%20that%20play%20a%20role%20with%20Outlook%202016%20as%20detailed%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3211279%2Foutlook-2016-implementation-of-autodiscover%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3211279%2Foutlook-2016-implementation-of-autodiscover%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20your%20case%20I%20would%20check%20for%2Fexclude%20the%20local%20and%20last%20know%20configuration%2C%20and%20maybe%20even%20force%20the%20%22O365%20as%20priority%22.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSTRONG%3EYes%2C%20I%20played%20already%20with%20the%20registry%20settings.%20An%20I%20read%20everything%20on%20the%20issue%20in%20several%20forums.%20Is%20there%20a%20way%20to%20escalate%20my%20request%20somehow%3F%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252087%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252087%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CBLOCKQUOTE%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20workaround%20is%20to%20simply%20configure%20the%20accounts%20via%20their%20user%40tenant.onmicrosoft.com%20account%20in%20Outlook.%20This%20way%20autodiscover%20should%20work%20correctly%2C%20and%20even%20if%20you%20see%20a%20credentials%20prompt%20it%20should%20be%20one-time%20only.%20Haven't%20played%20with%20this%20for%20a%20while%20though%2C%20so%20I'm%20not%20sure%20how%20it%20works%20with%20Modern%20auth%20in%20play...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%26gt%3B%26gt%3B%20answer%3A%20Yes%20I%20did%20already%20this%20because%20I%20got%20it%20working%20using%20the%20user%40tenant.onmicrosoft.com%20%3A)%3C%2Fimg%3E%20but%20still%20Popups.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS%3A%20But%20thanks%20for%20your%20fast%20reply%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252083%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252083%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20if%20I%20understand%20correctly%2C%20you%20are%20using%20the%20same%20domain%3F%20The%20easiest%20solution%20is%20to%20probably%20switch%20to%20a%20new%20domain%2Fnamespace%20and%20you%20should%20be%20even%20able%20to%20use%20a%20subdomain.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEven%20using%20the%20same%20domain%20should%20works%2C%20as%20long%20as%20you%20can%20update%20the%20targetaddress%20attribute%20of%20any%20of%20the%20affected%20users%20to%20point%20to%20user%40tenant.onmicrosoft.com%2C%20so%20that%20all%20Autodiscover%20requests%20hitting%20the%20hosted%20Exchange%20server%20are%20being%20redirected%20to%20O365.%20Problem%20is%2C%20this%20might%20not%20be%20possible%20in%20a%20hosted%20configuration%2C%20or%20will%20require%20you%20to%20work%20with%20the%20hoster%20support%20to%20configure%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnother%20workaround%20is%20to%20simply%20configure%20the%20accounts%20via%20their%20user%40tenant.onmicrosoft.com%20account%20in%20Outlook.%20This%20way%20autodiscover%20should%20work%20correctly%2C%20and%20even%20if%20you%20see%20a%20credentials%20prompt%20it%20should%20be%20one-time%20only.%20Haven't%20played%20with%20this%20for%20a%20while%20though%2C%20so%20I'm%20not%20sure%20how%20it%20works%20with%20Modern%20auth%20in%20play...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20case%20I'm%20not%20understanding%20the%20whole%20picture%2C%20a%20copy%20of%20the%20ExRCA%2FTest%20E-mail%20autoconfiguration%20wizards%20should%20clear%20up%20any%20confusion%2C%20so%20make%20sure%20to%20obtain%20them%20and%20attach%20them%20to%20the%20thread.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOther%20than%20that%2C%20I%20can%20think%20of%26nbsp%3Bfew%20more%20factors%20that%20play%20a%20role%20with%20Outlook%202016%20as%20detailed%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3211279%2Foutlook-2016-implementation-of-autodiscover%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3211279%2Foutlook-2016-implementation-of-autodiscover%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20your%20case%20I%20would%20check%20for%2Fexclude%20the%20local%20and%20last%20know%20configuration%2C%20and%20maybe%20even%20force%20the%20%22O365%20as%20priority%22.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252067%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252067%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20reply%20and%20your%20time%20you%20spend%20on%20my%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20I%20said%2C%20it%20is%20working%20-%20%3CSTRONG%3EJohn%20can%20send%20and%20receive%20mails%20with%20iOS%20devices%20because%20the%20use%20of%20the%20direct%20connection%20to%20O365!%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20still%20getting%20%3CSTRONG%3Epopups%3C%2FSTRONG%3E%20from%20Outlook%20because%20Outlook%20ist%20still%20looking%20for%20the%20%3CSTRONG%3Ewrong%20Autodiscovery-Server%3C%2FSTRONG%3E%20%3CSTRONG%3Ebeside%20it%20had%20it%20configured%20with%20direct%20connection%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20this%20direct%20connection%20is%20wanted%20because%20our%20Headquarter%20should%20be%20able%20to%20work%20independently.%3C%2FP%3E%3CP%3EAnd%20yes%20I%20tried%20everything.%20Including%20SARA.%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH3%20id%3D%22toc-hId-1452717248%22%20id%3D%22toc-hId--889193067%22%3EAnybody%20there%20who%20can%20tell%20me%20how%20to%20deactivate%20this%20continously%20accessing%20of%20Outlook%20to%20the%20wrong%20Autodiscovery-Server%20or%20have%20an%20different%20solution%20without%20interfering%20with%20the%20%22parallel%22%20Szenario%3F%3C%2FH3%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EAs%20I%20said%20Outlook%20of%20John%20is%20working%20fine%20and%20it%20was%20directly%20configured%20by%20a%20different%20method%20Outlook%20is%20using%20%26gt%3B%26gt%3B%20direct%20connection%20%26gt%3B%26gt%3B%20beside%3C%2FSTRONG%3E..%20I%20just%20have%20to%20click%20away%20the%20Popups.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20708px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F49651iDBDB3B544F7DA094%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222018-09-12-20-16-42_0001.jpg%22%20title%3D%222018-09-12-20-16-42_0001.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-252057%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-252057%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20still%20seems%20to%20be%20a%20DNS%20issue.%20Your%20clients%20(Outlook)%20seems%20to%20be%20getting%20the%20wrong%20autodiscover%20record%20and%20therefore%20are%20prompted%20for%20credentials.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20tried%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fexrca%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ERemote%20Connectivity%20Analyzer%20tools%3C%2FA%3E%26nbsp%3Bto%20check%20records%2C%20or%20%3CA%20href%3D%22https%3A%2F%2Fdiagnostics.outlook.com%2F%23%2F%3Fenv%3DExRCA%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESARA%3C%2FA%3E%26nbsp%3Bon%20your%20client%20PCs%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251846%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251846%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20708px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F49592iB9FF247D7FEF9A84%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222018-09-12-20-16-42_0001.jpg%22%20title%3D%222018-09-12-20-16-42_0001.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251730%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251730%22%20slang%3D%22en-US%22%3E%3CP%3EI%20got%20it%20working%20before%20I%20wrote%20my%20post%20(Headquarter%20still%20have%20the%20provider%20Exchange%20and%20we%20have%20the%20Office%20365%20Exchange)%26nbsp%3B%26nbsp%3B%3CSTRONG%3EBut%20still%20getting%20popups%20to%20enter%20credentials%20when%20Outlook%20Autodiscover%20(autodiscover.%3CDOMAIN%3E.%3CTLD%3E)%20kicks%20in.%20Why%20does%20it%20kick%20in%3F%20Why%20does%20it%20do%20the%20stuff%20to%20me%3F%3C%2FTLD%3E%3C%2FDOMAIN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EI%20knew%20before%20how%20to%20get%20Office%20365%20configured%20directly%20know%20even%20if%20autodiscover.%3CDOMAIN%3E.%3CTLD%3E%26nbsp%3Bis%20pointing%20to%20a%20provider%20Autodiscover-Server%20-%20Workaround%20as%20above.%20DNS%20record%20should%20be%20untouched%20in%20that%20way%20that%20nothing%20is%20interfering%20with%20Headquarter%20Exchange.%20Maybe%20adjusting%20SPF%20properly.%3C%2FTLD%3E%3C%2FDOMAIN%3E%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251530%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Provider%20Exchange%20an%20Office%20365%20Exchange%20environment%20-%20autodiscovery%20issue%20%2F%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251530%22%20slang%3D%22en-US%22%3E%3CP%3EFrom%20what%20I%20understood%2C%20your%20goal%20is%20not%20to%20have%20Exchange-Exchange%20Online%20hybrid%20configuration%20as%20it%20is%20usually%20understood.%20If%20you%20would%20build%20a%20real%20hybrid%2C%20you%20wouldn't%20need%20to%20worry%20about%20autodiscover%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyways%2C%20in%20your%20workaround%201%2C%20where%20did%20you%20change%20DNS%20record%3F%20Internal%20or%20external%20DNS%3F%20If%20they%20run%20on%20different%20servers%2C%20please%20double%20check%20that%20you%20have%20changed%20both%20records.%20It%20is%20also%20advisable%20to%20clear%20all%20DNS%20caches%20you%20might%20have%20(local%20computer%2C%20DNS%20server%2C%20etc.).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20like%20to%20test%26nbsp%3Bwhether%20the%20%22workaround%201%22%20works%2C%20you%20can%20also%20edit%20C%3A%5CWindows%5CSystem32%5Cdrivers%5Cetc%5Chosts%20-file%20to%20add%20autodiscover%20record%3A%3C%2FP%3E%3CPRE%3E40.101.65.200%20autodiscover.%26lt%3Bdomain%26gt%3B.%26lt%3Btld%26gt%3B%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

EDIT2: My apologies.. I took this in my feverish search for a solution as an offical support forum. I'm sorry. Thanks for reading and contribution as well.

EDIT --> THE SOLUTION!!!.  // NEXT THING TO COME --> THE PROPER SPF RECORD ;)*

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover]

"EnableOffice365ConfigService"=dword:00000001
"ExcludeLastKnownGoodURL"=dword:00000001
"ExcludeHttpRedirect"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeHttpsAutoDiscoverDomain"=dword:00000001

AND you must be logged in with the Office 365 Tenant in your Office Suite

not sure what exactly the proper key for surpressing this wrong autodiscvoery behaviour is... 16.0 in path of registry for Outlook 2016 - funny is when I delete the keys.. and even reconfigure mailbox no autodiscovery popups are comming. Condition is that I'm logged in with the Microsoft O365 tennant which is connected to the Mailbox

 

The <domain> (DNS-record) is already in use for a Provider based Exchange solution. We have a subsidiary that wants to work almost independently

 

goal: have a edit: "parallel scenario" John over O365 direct / provider exchange still using its autodiscovery service

2018-09-12-20-16-42_0001 2.jpg

(provider exchange and Office 365 Exchange) - DNS record could only be adjusted in that way that it doesn't interfere with full functionality of the Provider Exchange solution our Headquarter is using.

 

The problem:

autodiscover.<domain>.<tld> of the Provider based Exchange solution kicks in.

 

workaround 1 - edit IP in hosts for autodiscover.<domain>.<tld>:

edit hosts vor autodiscover.<domain>.<tld> so that Outlook get the right Konfiguration. As you see above the DNS of the <domain> should not interfere with full functionality for our HQ.

 

result of ping autodiscover.<domain>.<tld> showed the adjusted IP (autodiscover.outlook.com) but it didn't worked out.

 

nslookup autodiscover.<domain>.<tld> showed Provider Exchange solution - so it thought this old workaround did not work here..

 

workaround 2 - adjust autodiscover values:

Maybe this could be some part of the solution?

adjust autodiscover behavior in registry. adjust values under HKEY_CURRENT_USER\Software\Microsoft\O...

 

  • SCP lookup
  • HTTPS root domain query
  • HTTPS Autodiscover domain query
  • Local XML file
  • HTTP redirect method
  • SRV record query
  • Cached URL in the Outlook profile (new for Outlook 2010 version 14.0.7140.5001 and later versions)
  • Direct Connect to Office 365 (new for Outlook 2016 version 16.0.6741.2017 and later versions)

workaround 3: seemed promising

after I logged out with the Office 365 Account in Office which has the Mailbox connected and logged in again I somehow managed to get the login screen. Just seems like Outlook then connects somehow directly to Office 365.

 

but still some popups for credentials, and some autodiscovery popup from the provider exchange solution.

 

iOS Devices seems to use the or a direct method... there is no interference with the autodiscovery.<domain>.<tld>

 

Please help me find a stable and Poupfree solution.

 

Greetings,

Benjamin

 

13 Replies
Highlighted

From what I understood, your goal is not to have Exchange-Exchange Online hybrid configuration as it is usually understood. If you would build a real hybrid, you wouldn't need to worry about autodiscover at all.

 

Anyways, in your workaround 1, where did you change DNS record? Internal or external DNS? If they run on different servers, please double check that you have changed both records. It is also advisable to clear all DNS caches you might have (local computer, DNS server, etc.).

 

If you like to test whether the "workaround 1" works, you can also edit C:\Windows\System32\drivers\etc\hosts -file to add autodiscover record:

40.101.65.200 autodiscover.<domain>.<tld>

 

Highlighted

I got it working before I wrote my post (Headquarter still have the provider Exchange and we have the Office 365 Exchange)  But still getting popups to enter credentials when Outlook Autodiscover (autodiscover.<domain>.<tld>) kicks in. Why does it kick in? Why does it do the stuff to me?

 

I knew before how to get Office 365 configured directly know even if autodiscover.<domain>.<tld> is pointing to a provider Autodiscover-Server - Workaround as above. DNS record should be untouched in that way that nothing is interfering with Headquarter Exchange. Maybe adjusting SPF properly.

Highlighted

It still seems to be a DNS issue. Your clients (Outlook) seems to be getting the wrong autodiscover record and therefore are prompted for credentials.

 

Have you tried Remote Connectivity Analyzer tools to check records, or SARA on your client PCs?

Highlighted

Thanks for your reply and your time you spend on my issue. 

 

As I said, it is working - John can send and receive mails with iOS devices because the use of the direct connection to O365!

 

But still getting popups from Outlook because Outlook ist still looking for the wrong Autodiscovery-Server beside it had it configured with direct connection.

 

And this direct connection is wanted because our Headquarter should be able to work independently.

And yes I tried everything. Including SARA. ;)

 

Anybody there who can tell me how to deactivate this continously accessing of Outlook to the wrong Autodiscovery-Server or have an different solution without interfering with the "parallel" Szenario?

 

As I said Outlook of John is working fine and it was directly configured by a different method Outlook is using >> direct connection >> beside.. I just have to click away the Popups. 

 

2018-09-12-20-16-42_0001.jpg

 

Highlighted

So if I understand correctly, you are using the same domain? The easiest solution is to probably switch to a new domain/namespace and you should be even able to use a subdomain.

 

Even using the same domain should works, as long as you can update the targetaddress attribute of any of the affected users to point to user@tenant.onmicrosoft.com, so that all Autodiscover requests hitting the hosted Exchange server are being redirected to O365. Problem is, this might not be possible in a hosted configuration, or will require you to work with the hoster support to configure it.

 

Another workaround is to simply configure the accounts via their user@tenant.onmicrosoft.com account in Outlook. This way autodiscover should work correctly, and even if you see a credentials prompt it should be one-time only. Haven't played with this for a while though, so I'm not sure how it works with Modern auth in play...

 

In case I'm not understanding the whole picture, a copy of the ExRCA/Test E-mail autoconfiguration wizards should clear up any confusion, so make sure to obtain them and attach them to the thread.

 

Other than that, I can think of few more factors that play a role with Outlook 2016 as detailed here: https://support.microsoft.com/en-us/help/3211279/outlook-2016-implementation-of-autodiscover

 

In your case I would check for/exclude the local and last know configuration, and maybe even force the "O365 as priority".

 

Highlighted

@Vasil Michev wrote:

 

Another workaround is to simply configure the accounts via their user@tenant.onmicrosoft.com account in Outlook. This way autodiscover should work correctly, and even if you see a credentials prompt it should be one-time only. Haven't played with this for a while though, so I'm not sure how it works with Modern auth in play...

 

>> answer: Yes I did already this because I got it working using the user@tenant.onmicrosoft.com :) but still Popups.

 

PS: But thanks for your fast reply


Highlighted

@Vasil Michev wrote:

 

Other than that, I can think of few more factors that play a role with Outlook 2016 as detailed here: https://support.microsoft.com/en-us/help/3211279/outlook-2016-implementation-of-autodiscover

 

In your case I would check for/exclude the local and last know configuration, and maybe even force the "O365 as priority".


Yes, I played already with the registry settings. An I read everything on the issue in several forums. Is there a way to escalate my request somehow?

Highlighted

Yeah, this behaviour in the following link I want - as here described it shows how to deactivate this behaviour! And it is still working and I don't wan't to deactivate this feature! I don't want to have the popups autodiscovery kicks in. Like an inverted solution to this solution in the link.

Outlook bypasses AutoDiscover and connects directly to Office 365 mailbox

 

very helpful too goot collection of helpful links but I don't got it working. Sad, so sad.

Good description of the behaviour

 

As us see I did a lot of reading 3 day ago but it didn't worked out. Maybe I did a wrong registry setup??

Screenshot 2018-09-13 08.59.50.png

Highlighted

 

I don't want to be rude or something like that.. I already spent 15 hours on this issue.. still no solution. And got only things told that I already did and wrote in my post.
I have a business running and I need professional <timesaving> support. Is this an official Microsoft Support Forum. Or have I the wrong expectations?

Highlighted
Best Response confirmed by Benjamin Riedel (Occasional Contributor)
Solution

Found it after 18 hours ;) This was a very helpful link:

VERY HELPFUL LINK

EDIT --> THE SOLUTION!!! / it only works when login with the tenant.. user@xyz.onmicrosoft.com or when you changed primary email to user@<domain>.<tld.> it is till working. -------> AND!!! Made some registry tweaks see below

not sure what exactly the proper key is... 16.0 stands for Outlook 2016 - funny is when I delete the keys.. and even reconfigure mailbox no autodiscovery popups are comming. Condition is that I'm logged in with the Microsoft O365 tennant which is connected to the Mailbox.

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover]

"EnableOffice365ConfigService"=dword:00000001
"ExcludeLastKnownGoodURL"=dword:00000001
"ExcludeHttpRedirect"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeHttpsAutoDiscoverDomain"=dword:00000001

Highlighted

@Benjamin Riedel, this is NOT a support forum/channel. We are just fellow IT Pros discussing different topic and occasionally helping each other. If you want to address specific issue to official Office 365 support, open a ticket from the portal or call them directly.

 

Glad the issue was solved :)

Highlighted

My apologies.. I took this in my feverish search for a solution as an offical support forum. I'm sorry. Thanks for reading and contribution as well.