SOLVED

Move from Staged Hybrid Migration to full Exchange Online

%3CLINGO-SUB%20id%3D%22lingo-sub-105205%22%20slang%3D%22en-US%22%3EMove%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-105205%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20Day%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20moved%20and%20finalized%20approx%2060%20mailboxes%20from%20Exchange%202010%20On%20premisis%20to%20Exchange%20online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20all%20mail%20clients%20are%20pointing%20to%20Exchange%20online%2C%20however%20mail%20is%20still%20being%20delivered%20on-premise%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20following%20article%20on%20decomissioning%20on-premisis%20has%20been%20helpful%2C%20however%20just%20need%20to%20get%20a%20plan%20solidified.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn931280(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn931280(v%3Dexchg.150).aspx%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%2C%20no%20MX%20records%20have%20been%20changed%20to%20redirect%20mail%20permanently.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20still%20like%20to%20use%20ADSync%20after%20the%20cutover%20to%20unify%20password%20management%20between%20on%20premise%20and%20online%2C%20however%20I%20would%20like%20to%20do%20all%20exchange%20managent%20from%20portal%20administration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20like%20to%20completely%20decomission%20on-premise%20exchange%20post%20cutover.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20share%20any%20info%20on%20whether%20the%20scenario%20outlined%20is%20possible%20at%20all%20and%20what%20I%20need%20to%20do%20to%20accomplish%20it%3F%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-105205%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20Premise%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481081%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481081%22%20slang%3D%22en-US%22%3EOk%20ok%20guys!%20You%E2%80%99re%20just%20going%20back%20and%20forth%20here!%20Let%E2%80%99s%20just%20call%20it%20a%20day%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481071%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481071%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EI%20will%20type%20this%20ssssslllllllooooooooowwwwwwwlllllllyyyyyyy%20so%20you%20can%20understand%20it.%26nbsp%3B%20There%20is%20NOTHING%20in%20his%20post%20that%20said%20ANYTHING%20about%20wanted%20to%20sync%20users.%26nbsp%3B%20NOTHING.%26nbsp%3B%20Only%20passwords.%26nbsp%3B%20What%20seems%20to%20be%20happening%20now%20is%20that%20you%20may%20have%20realized%20that%20you%20have%20made%20a%20mistake%20but%20are%20too%20proud%20to%20simply%20bow%20out%20gracefully.%26nbsp%3B%20Here%20is%20entire%20post%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EGood%20Day%2C%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EI%20have%20moved%20and%20finalized%20approx%2060%20mailboxes%20from%20Exchange%202010%20On%20premisis%20to%20Exchange%20online.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECurrently%20all%20mail%20clients%20are%20pointing%20to%20Exchange%20online%2C%20however%20mail%20is%20still%20being%20delivered%20on-premise%20as%20well.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EThe%20following%20article%20on%20decomissioning%20on-premisis%20has%20been%20helpful%2C%20however%20just%20need%20to%20get%20a%20plan%20solidified.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn931280(v%3Dexchg.150).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn931280(v%3Dexchg.150).aspx%3C%2FA%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECurrently%2C%20no%20MX%20records%20have%20been%20changed%20to%20redirect%20mail%20permanently.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EI%20would%20still%20like%20to%20use%20ADSync%20after%20the%20cutover%20%3CSTRONG%3Eto%20unify%20password%20management%20between%20on%20premise%20and%20online%2C%20however%20I%20would%20like%20to%20do%20all%20exchange%20managent%20from%20portal%20administration.%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EI%20would%20like%20to%20completely%20decomission%20on-premise%20exchange%20post%20cutover.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECan%20anyone%20share%20any%20info%20on%20whether%20the%20scenario%20outlined%20is%20possible%20at%20all%20and%20what%20I%20need%20to%20do%20to%20accomplish%20it%3F%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EThanks%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480996%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480996%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20i%20will%20try%20one%20last%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHe%20wanted%20to%20sync%20users%2Fpasswords%20from%20his%20on-premise%20AD%20-%20yes%2C%20you%20can%20use%20AD%20Connect%20for%20that%20and%20no%20Exchange%20installation%20is%20needed%20for%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHe%20wanted%20to%20decomission%20his%20Exchange%20installation%20and%20still%20be%20able%20to%20sync%20on-premise%20users%2Fpasswords%20to%20Office%20365%20-%20yes%2C%20having%20only%20AD%20Connect%20is%20enough%20for%20that%20(although%20who%20would%20just%20sync%20users%3F%20Usually%20some%20other%20services%20like%20Exchange%2C%20SharePoint%2C%20OneDrive%2C%20etc.%20are%20used%20with%20these%20users).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHe%20wanted%20to%20decommission%20his%20Exchange%20installation%20and%20be%20able%20to%20manage%20Exchange%20in%20Office%20365%20Admin%20Center%20%26gt%3B%20Exchange%20Online%20console%20-%20you%20can%20change%20some%20settings%2C%20but%20you%20can't%20change%20user%20settings%20that%20are%20synced%20from%20on-premise%20AD%20like%20SMTP%20addresses.%20You%20will%20get%20a%20read-only%20error%20and%20will%20have%20to%20change%20these%20settings%20locally%20in%20your%20AD%20and%20then%20sync%20them%20to%20Exchange%20Online.%20You%20can%20use%20PowerShell%20or%20AD%20Users%20and%20Computers%20console%20to%20change%20these%20attributes%2C%20but%20Microsoft%20is%20calling%20a%20supported%20setup%20if%20you%20leave%20one%20Exchange%20server%20on-premises%20and%20do%20such%20changes%20via%20Exchange%20Admin%20Center%20(or%20Exchange%20Management%20Shell).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480871%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480871%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3EThank%20you%20for%20making%20my%20point.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480855%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480855%22%20slang%3D%22en-US%22%3E%22I%20would%20still%20like%20to%20use%20ADSync%20after%20the%20cutover%20to%20unify%20password%20management%20between%20on%20premise%20and%20online%2C%20however%20I%20would%20like%20to%20do%20all%20exchange%20managent%20from%20portal%20administration.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20like%20to%20completely%20decomission%20on-premise%20exchange%20post%20cutover.%22%3CBR%20%2F%3E%3CBR%20%2F%3EHe%20wanted%20to%20have%20both%20sync%20and%20be%20able%20to%20manage%20exchange%20from%20online%20portal.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480818%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480818%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3B%20The%20entire%20point%20of%20his%20post%20was%20that%20he%20wanted%20to%20decommission%20his%20exchange%20server%20but%20still%20wanted%20password%20sync.%26nbsp%3B%20Perhaps%20you%20misunderstood%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480814%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480814%22%20slang%3D%22en-US%22%3E%3CP%3EI%20will%20leave%20to%20readers%20of%20my%20posts%20to%20decide%20how%20they%20want%20to%20interpret%20Microsoft%20%22unsupported%22%20and%20what%20they%20hope%20to%20receive%2C%20but%20i%20won't%20omit%20such%20information.%20I%20haven't%20worked%20for%20Microsoft%2C%20so%20i%20can't%20imply%20anything.%20And%20how%20working%20at%20MS%20in%20the%20past%20proves%20something%20about%20current%20policies%3F%20I%20would%20love%20an%20official%20from%20MS%20to%20approve%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20know%20why%20you%20have%20emphasized%20password%20sync%20in%20particular%20when%20the%20main%20point%20of%20this%20thread%20is%20Exchange%20management.%20Yes%2C%20password%20sync%20will%20work%20with%20only%20having%20local%20AD.%20As%20with%20Exchange%20management%2C%20i%20also%20worked%20with%20a%20hybrid%20setup%20without%20Exchange%20on-premise%20(uninstalled%20after%20mailboxes%20migration)%20and%20last%20time%20i%20tried%20to%20change%20alias%20or%20SMTP%20of%20a%20synced%20user%20in%20Exchange%20Online%20admin%20center%20i%20was%20greeted%20with%20an%20error%20that%20my%20user%20directory%20is%20read-only%20and%20i%20should%20do%20changes%20in%20my%20local%20AD.%20Haven't%20seen%20any%20announcements%20about%20changes%20in%20this%20area%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480794%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480794%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3EDo%20you%20know%20how%20Microsoft%20defines%20%22supported%3F%22%26nbsp%3B%20I%20do%2C%20because%20I%20worked%20there%20for%2012%20years.%26nbsp%3B%20It%20is%20defined%20at%20%22we%20have%20tested%20this%20and%20can%20therefore%20guarantee%20a%20certain%20level%20of%20outcome.%22%26nbsp%3B%20Whenever%20said%20it%20was%20%22unsupported%22%20we%20still%20gave%20best%20effort.%26nbsp%3B%20Oh%20and%20just%20an%20FYI%2C%20have%20several%20clients%20with%20NO%20onsite%20exchange%20server%20and%20they%20are%20able%20to%20sync%20passwords%20with%20AD%2C%20without%20issue.%26nbsp%3B%20They%20also%20have%20no%20issue%20adding%20aliases%2C%20which%20is%20done%20in%20the%20cloud%2C%20where%20the%20mailbox%20resides.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480722%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480722%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20read%20what%20Vasil%20has%20provided%3F%20If%20you%20sync%20on-premise%20AD%20users%20with%20dirsync%2Fad%20connect%20and%20you%20use%20Exchange%20Online%20(topic's%20author%20IS%20using%20Exchange%2C%20so%20it%20IS%20relevant%20here)%2C%20how%20are%20you%20going%20to%20say%20add%20another%20alias%20or%20change%20current%20SMTP%20address%20or%20any%20other%20Exchange%20attribute%20of%20a%20user%2C%20so%20it%20would%20reflect%20in%20his%2Fher%20EO%20mailbox%3F%20You%20have%20to%20do%20this%20on-premise.%20You%20can%20use%20AD%20Users%20console%2FPowerShell%20for%20that.%20But%20Microsoft%20might%20decline%20to%20provide%20you%20support%2C%20if%20you%20have%20no%20local%20Exchange%20server%20in%20such%20setup%2C%20because%20for%20now%20having%20local%20Exchange%20server%20when%20using%20hybrid%20setup%20is%20the%20only%20officially%20supported%20way%20(not%20technically%2C%20but%20from%20a%20support%20eligibility%20standpoint).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480653%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480653%22%20slang%3D%22en-US%22%3E%3CP%3EY%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%20You%20seem%20upset%2C%20how%20bout%20you%20take%20a%20chill%20pill.%26nbsp%3B%20No%20one%20said%20ANYTHING%20about%20exchange%20properties.%26nbsp%3B%20In%20fact%2C%20the%20whole%20point%20of%20the%20post%20was%20getting%20RID%20of%20exchange%20altogether.%26nbsp%3B%20Doing%20this%2C%20have%20all%20of%20your%20exchange%20functions%20handled%20in%20O%20365%20and%20leave%20you%20with%20only%20syncing%20passwords%20with%20AD.%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CBR%20%2F%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480646%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480646%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20are%20you%20reviving%20an%20old%20topic%20with%20redundant%20and%20somewhat%20misleading%20information%3F%20It%20was%20already%20stated%2C%20that%20you%20can%20use%20dirsync%20(ad%20connect%20is%20just%20a%20new%20version%20of%20that)%20without%20a%20local%20exchange%20server%20and%20using%20other%20tools%20to%20manage%20exchange%20properties%2C%20but%20this%20will%20be%20deemed%20as%20unsupported%20setup%20by%20MS%20support.%20So%20you%20do%20this%20at%20your%20own%20risk.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480598%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480598%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F69266%22%20target%3D%22_blank%22%3E%40Keith%20Caines%3C%2FA%3EActually%2C%20this%20is%20not%20longer%20the%20case.%26nbsp%3B%20Because%20now%20there%20is%20ad%20connect.%20Ad%20Connect%20allows%20you%20to%20sync%20passwords%20only%2C%20without%20an%20exchange%20server.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-105833%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-105833%22%20slang%3D%22en-US%22%3E%3CP%3EThey're%20looking%20into%20it%2C%20at%20least%20that's%20the%20answer%20we%20get%20anytime%20we%20raise%20this%20topic%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-105689%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-105689%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%20wrote%3A%3CBR%20%2F%3E%3CP%3EEvery%20configuration%20involving%20dirsync%2C%20including%20password%20sync%2C%20requires%20you%20to%20keep%20an%20Exchange%20box%20for%20management%20purposes.%20Otherwise%20you%20will%20be%20in%20%22unsupported%22%20configuration.%20You%20dont%20have%20to%20follow%20the%20Microsoft%20recommendations%20on%20it%2C%20you%20can%20manage%20the%20objects%20just%20fine%20with%20other%20tools%2C%20but%20you%20riks%20being%20denied%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20an%20example%20article%20that%20goes%20into%20more%20detail%3A%20%3CA%20href%3D%22https%3A%2F%2Fblogs.msdn.microsoft.com%2Fvilath%2F2015%2F05%2F25%2Foffice-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.msdn.microsoft.com%2Fvilath%2F2015%2F05%2F25%2Foffice-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises%2F%3C%2FA%3E%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EThank%20you%20for%20sharing%20that%20thread.%20Wow.%20You%20were%20not%20kidding.%20I%20wonder%20why%20MS%20hasn't%20provided%20what%20seems%20to%20be%20a%20very%20simple%20solution%20to%20an%20obvious%20pain%20point!%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-105641%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-105641%22%20slang%3D%22en-US%22%3E%3CP%3EEvery%20configuration%20involving%20dirsync%2C%20including%20password%20sync%2C%20requires%20you%20to%20keep%20an%20Exchange%20box%20for%20management%20purposes.%20Otherwise%20you%20will%20be%20in%20%22unsupported%22%20configuration.%20You%20dont%20have%20to%20follow%20the%20Microsoft%20recommendations%20on%20it%2C%20you%20can%20manage%20the%20objects%20just%20fine%20with%20other%20tools%2C%20but%20you%20riks%20being%20denied%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20an%20example%20article%20that%20goes%20into%20more%20detail%3A%20%3CA%20href%3D%22https%3A%2F%2Fblogs.msdn.microsoft.com%2Fvilath%2F2015%2F05%2F25%2Foffice-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.msdn.microsoft.com%2Fvilath%2F2015%2F05%2F25%2Foffice-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-105484%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-105484%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20AD%20Sync%20configured%20on%20on-premisis%20domain%20controller.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20not%20realize%20that%20in%20order%20to%20syncronize%20passwords%20I%20would%20have%20to%20keep%20my%20exchange%20box%20around.%20Is%20this%20correct%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20want%20to%20completly%20decomission%20my%20exchange%20server.%20If%20this%20means%20that%20I%20lose%20the%20ability%20to%20sync%20passwords%20then%20so%20be%20it.%20Just%20seems%20strange.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20easlily%20%22enable%22%20management%20from%20the%20Admin%20Portal%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-105376%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-105376%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20cannot%20have%20both.%20You%20either%20manage%20the%20accounts%20directly%20in%20O365%2C%20which%20means%20no%20password%20sync%2C%20or%20use%20dirsync%2Fpassword%20sync%2C%20but%20manage%20them%20on-premises.%20The%20latter%20also%20requires%20you%20to%20keep%20one%20Exchange%20box%20for%20management%20purposes%2C%20if%20you%20want%20to%20stay%20in%20%22supported%22%20scenario.%20If%20you%20don't%20care%20about%20that%20part%2C%20you%20can%20just%20manage%20them%20via%20ADUC%2FPowerShell%2Fwhatever.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-812342%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-812342%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F325027%22%20target%3D%22_blank%22%3E%40sfbtech%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOMG%2C%20you%20didn%C2%B4t%20understand%20anything...%20He%20wants%20to%20stay%20with%20his%20local%20AD%2C%20so%20he%20needs%20ADConnect.%20But%20with%20ADConnect%20and%20not%20Azure%20AD%20Pure%20online%2C%20you%20will%20need%20to%20have%20an%20Exchange%20installation%20to%20edit%20your%20Exchange%20specific%20Attributes%20in%20your%20local%20AD%2C%20which%20then%20will%20get%20synced%20to%20AAD.%20If%20you%20have%20ADConnect%2C%20local%20AD%20is%20the%20leading%20Authentication%20Provider.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps%20any%20new%20Readers%2C%20Oleg%20is%20absolutely%20correct%20with%20his%20statements.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-812365%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20from%20Staged%20Hybrid%20Migration%20to%20full%20Exchange%20Online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-812365%22%20slang%3D%22en-US%22%3EBTW%2C%20you%20can%20clean%20up%20your%20Exchange%20Server%20Databases%2C%20shrink%20your%20Disks%2C%20etc.%20You%20only%20need%20a%20small%20VM%20after%20that%2C%20just%20in%20case%20you%20need%20to%20edit%20User%20Settings.%20Maybe%20you%20can%20migrate%20it%20to%20Azure%20and%20use%20Azure%20Automation%20to%20start%20it%20regularly%20for%2030%20minutes%20and%20than%20shut%20it%20down%20to%20save%20costs.%20Just%20to%20get%20a%20connect%20to%20your%20DCs.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Good Day,

 

I have moved and finalized approx 60 mailboxes from Exchange 2010 On premisis to Exchange online.

 

Currently all mail clients are pointing to Exchange online, however mail is still being delivered on-premise as well.

 

The following article on decomissioning on-premisis has been helpful, however just need to get a plan solidified.

https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx

 

Currently, no MX records have been changed to redirect mail permanently.

 

I would still like to use ADSync after the cutover to unify password management between on premise and online, however I would like to do all exchange managent from portal administration.

 

I would like to completely decomission on-premise exchange post cutover.

 

Can anyone share any info on whether the scenario outlined is possible at all and what I need to do to accomplish it?

 

Thanks

19 Replies
Highlighted

You cannot have both. You either manage the accounts directly in O365, which means no password sync, or use dirsync/password sync, but manage them on-premises. The latter also requires you to keep one Exchange box for management purposes, if you want to stay in "supported" scenario. If you don't care about that part, you can just manage them via ADUC/PowerShell/whatever.

Highlighted

I have AD Sync configured on on-premisis domain controller. 

 

I did not realize that in order to syncronize passwords I would have to keep my exchange box around. Is this correct?

 

I want to completly decomission my exchange server. If this means that I lose the ability to sync passwords then so be it. Just seems strange.

 

Is there a way to easlily "enable" management from the Admin Portal?

 

 

 

 

Highlighted
Best Response confirmed by Keith Caines (Occasional Contributor)
Solution

Every configuration involving dirsync, including password sync, requires you to keep an Exchange box for management purposes. Otherwise you will be in "unsupported" configuration. You dont have to follow the Microsoft recommendations on it, you can manage the objects just fine with other tools, but you riks being denied support.

 

Here's an example article that goes into more detail: https://blogs.msdn.microsoft.com/vilath/2015/05/25/office-365-and-dirsync-why-should-you-have-at-lea...

Highlighted

@Vasil Michev wrote:

Every configuration involving dirsync, including password sync, requires you to keep an Exchange box for management purposes. Otherwise you will be in "unsupported" configuration. You dont have to follow the Microsoft recommendations on it, you can manage the objects just fine with other tools, but you riks being denied support.

 

Here's an example article that goes into more detail: https://blogs.msdn.microsoft.com/vilath/2015/05/25/office-365-and-dirsync-why-should-you-have-at-lea...


Thank you for sharing that thread. Wow. You were not kidding. I wonder why MS hasn't provided what seems to be a very simple solution to an obvious pain point!?

Highlighted

They're looking into it, at least that's the answer we get anytime we raise this topic :)

Highlighted

@Keith CainesActually, this is not longer the case.  Because now there is ad connect. Ad Connect allows you to sync passwords only, without an exchange server. 

Highlighted

Why are you reviving an old topic with redundant and somewhat misleading information? It was already stated, that you can use dirsync (ad connect is just a new version of that) without a local exchange server and using other tools to manage exchange properties, but this will be deemed as unsupported setup by MS support. So you do this at your own risk.

Highlighted

Y@Oleg K You seem upset, how bout you take a chill pill.  No one said ANYTHING about exchange properties.  In fact, the whole point of the post was getting RID of exchange altogether.  Doing this, have all of your exchange functions handled in O 365 and leave you with only syncing passwords with AD.




 

Highlighted

Have you read what Vasil has provided? If you sync on-premise AD users with dirsync/ad connect and you use Exchange Online (topic's author IS using Exchange, so it IS relevant here), how are you going to say add another alias or change current SMTP address or any other Exchange attribute of a user, so it would reflect in his/her EO mailbox? You have to do this on-premise. You can use AD Users console/PowerShell for that. But Microsoft might decline to provide you support, if you have no local Exchange server in such setup, because for now having local Exchange server when using hybrid setup is the only officially supported way (not technically, but from a support eligibility standpoint).

Highlighted

@Oleg KDo you know how Microsoft defines "supported?"  I do, because I worked there for 12 years.  It is defined at "we have tested this and can therefore guarantee a certain level of outcome."  Whenever said it was "unsupported" we still gave best effort.  Oh and just an FYI, have several clients with NO onsite exchange server and they are able to sync passwords with AD, without issue.  They also have no issue adding aliases, which is done in the cloud, where the mailbox resides.  

Highlighted

I will leave to readers of my posts to decide how they want to interpret Microsoft "unsupported" and what they hope to receive, but i won't omit such information. I haven't worked for Microsoft, so i can't imply anything. And how working at MS in the past proves something about current policies? I would love an official from MS to approve that.

 

I don't know why you have emphasized password sync in particular when the main point of this thread is Exchange management. Yes, password sync will work with only having local AD. As with Exchange management, i also worked with a hybrid setup without Exchange on-premise (uninstalled after mailboxes migration) and last time i tried to change alias or SMTP of a synced user in Exchange Online admin center i was greeted with an error that my user directory is read-only and i should do changes in my local AD. Haven't seen any announcements about changes in this area yet.

Highlighted

@Oleg K  The entire point of his post was that he wanted to decommission his exchange server but still wanted password sync.  Perhaps you misunderstood?

Highlighted
"I would still like to use ADSync after the cutover to unify password management between on premise and online, however I would like to do all exchange managent from portal administration.

I would like to completely decomission on-premise exchange post cutover."

He wanted to have both sync and be able to manage exchange from online portal.
Highlighted

@Oleg KThank you for making my point.

Highlighted

Ok, i will try one last time.

 

He wanted to sync users/passwords from his on-premise AD - yes, you can use AD Connect for that and no Exchange installation is needed for that.

 

He wanted to decomission his Exchange installation and still be able to sync on-premise users/passwords to Office 365 - yes, having only AD Connect is enough for that (although who would just sync users? Usually some other services like Exchange, SharePoint, OneDrive, etc. are used with these users).

 

He wanted to decommission his Exchange installation and be able to manage Exchange in Office 365 Admin Center > Exchange Online console - you can change some settings, but you can't change user settings that are synced from on-premise AD like SMTP addresses. You will get a read-only error and will have to change these settings locally in your AD and then sync them to Exchange Online. You can use PowerShell or AD Users and Computers console to change these attributes, but Microsoft is calling a supported setup if you leave one Exchange server on-premises and do such changes via Exchange Admin Center (or Exchange Management Shell).

Highlighted

@Oleg K 

I will type this ssssslllllllooooooooowwwwwwwlllllllyyyyyyy so you can understand it.  There is NOTHING in his post that said ANYTHING about wanted to sync users.  NOTHING.  Only passwords.  What seems to be happening now is that you may have realized that you have made a mistake but are too proud to simply bow out gracefully.  Here is entire post 

 

 

Good Day,

 

I have moved and finalized approx 60 mailboxes from Exchange 2010 On premisis to Exchange online.

 

Currently all mail clients are pointing to Exchange online, however mail is still being delivered on-premise as well.

 

The following article on decomissioning on-premisis has been helpful, however just need to get a plan solidified.

https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx

 

Currently, no MX records have been changed to redirect mail permanently.

 

I would still like to use ADSync after the cutover to unify password management between on premise and online, however I would like to do all exchange managent from portal administration.

 

I would like to completely decomission on-premise exchange post cutover.

 

Can anyone share any info on whether the scenario outlined is possible at all and what I need to do to accomplish it?

 

Thanks

Highlighted
Ok ok guys! You’re just going back and forth here! Let’s just call it a day :)

Adam
Highlighted

@sfbtech 

 

OMG, you didn´t understand anything... He wants to stay with his local AD, so he needs ADConnect. But with ADConnect and not Azure AD Pure online, you will need to have an Exchange installation to edit your Exchange specific Attributes in your local AD, which then will get synced to AAD. If you have ADConnect, local AD is the leading Authentication Provider.

 

Hope this helps any new Readers, Oleg is absolutely correct with his statements.

Highlighted
BTW, you can clean up your Exchange Server Databases, shrink your Disks, etc. You only need a small VM after that, just in case you need to edit User Settings. Maybe you can migrate it to Azure and use Azure Automation to start it regularly for 30 minutes and than shut it down to save costs. Just to get a connect to your DCs.