We're consolidating Yammer networks

%3CLINGO-SUB%20id%3D%22lingo-sub-196650%22%20slang%3D%22en-US%22%3EWe're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-196650%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FEM%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22font-medium%20mc-fnt-fmly-sl%20mc-actn-msg%22%3EAction%20required%20by%20September%2025%2C%202018%3C%2FDIV%3E%3CP%3E%3C!--%20%20%20end%20ngIf%3A%20message.ActionType%20%3D%3D%3D%20'Action'%20%20%20--%3E%3C!--%20%20%20ngIf%3A%20showDirectLink%20%20%20--%3E%3C%2FP%3E%3CDIV%20class%3D%22mc-cnt-top%22%3E%3CDIV%20class%3D%22font-medium%20mc.fnt-fmly-sl%20f-txtalgn-jstfy%20f-pad-top-20px%20mc-msg-clr%22%3EStarting%20September%2026%2C%202018%2C%20Yammer%20will%20no%20longer%20support%20multiple%20internal%20Yammer%20networks%20associated%20with%20one%20Office%20365%20tenant.%20We%20will%20be%20consolidating%20your%20internal%20Yammer%20networks%20into%20a%20parent%20Yammer%20network.%20During%20this%20process%2C%20content%20will%20no%20longer%20be%20available%20from%20the%20subsidiary%20networks.%20We%20recommend%20you%20migrate%20your%20own%20networks%20prior%20to%20September%2026.%3CBR%20%2F%3EThis%20change%20does%20not%20impact%20external%20Yammer%20networks.%3CBR%20%2F%3E%3CBR%20%2F%3EQuestion%3A%3CBR%20%2F%3EI%20have%20one%20tenant%26nbsp%3Band%20multiple%20domain%26nbsp%3B%3CBR%20%2F%3EHow%20do%20I%20know%20how%20many%20internal%20and%20external%20I%20have%3F%3CBR%20%2F%3EWhich%20one%20is%20parent%20and%20subsidiary%20network%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-196650%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197670%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197670%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20you%20merge%2Fconsolidate%20the%20networks%20and%20only%20have%201%20network%20left%2C%20then%20in%20September%20Microsoft%20can't%20consolidate%20multiple%20networks%20for%20you.%20They%20won't%20support%20multiple%20networks%20going%20forward%2C%20which%20means%20that%20new%20accounts%20will%20automatically%20be%20created%20in%20the%20network%20you%20already%20have.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can't%20really%20%22delete%22%20a%20network.%20You%20have%20to%20use%20the%20network%20merge%20wizard.%20You%20could%20remove%20the%20domain%20from%20your%20tenant%2C%20but%20I%20wouldn't%20recommend%20doing%20that.%20You%20mentioned%20having%20the%20same%20users%20on%20both%20networks.%20This%20happens%20when%20your%20users%20have%20multiple%20email%20accounts%20with%20different%20domains%20or%20when%20emails%20sent%20to%20a%20different%20email%20address%20end%20up%20in%20their%20email%20inbox.%20Merging%20the%20networks%20will%20result%20in%20duplicate%20accounts.%20You%20have%20to%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fenforce-office-365-identity-for-yammer-users-008f940b-6bec-47fc-bcc6-9c6133467562%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Eenforce%20Office%20365%20identities%3C%2FA%3E%20in%20your%20parent%20network%20to%20address%20this.%20This%20will%20deactivate%20accounts%20not%20associated%20with%20an%20Office%20365%20account%20and%20remove%20them%20from%20search.%20The%20external%20networks%20will%20be%20connected%20to%20your%20parent%20network%2C%20but%20they%20won't%20have%20access%20to%20them%26nbsp%3Bbecause%20their%20accounts%20will%20be%20deactivated.%20As%20an%20admin%2C%20you%20have%20access%20to%20all%20external%20networks%20after%20the%20merge%2C%20allowing%20you%20to%20give%20the%20correct%20account%20admin%20priveledges.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20still%20imagine%20that%20you%20can%20end%20up%20having%20multiple%20networks%20before%20September.%20As%20an%20example%3A%20when%20you%20add%20a%20new%20domain%20to%20the%20tenant%20and%20users%20can%20use%20that%20email%20address%20to%20sign%20up%20for%20an%20account%20on%20Yammer%2C%20this%20will%20result%20in%20a%20new%20network.%20Another%20scenario%20is%20that%20you%20already%20have%20an%20additional%20domain%2C%20but%20users%20never%20signed%20up%20for%20an%20account%20on%20Yammer%20using%20that%20email%20address.%20This%20problem%20shouldn't%20be%20there%20anymore%20after%20September%20as%20they%20will%20stop%20supporting%20multiple%20networks.%20Would%20recommend%20monitoring%20this%20and%20figuring%20out%20why%20you%20have%20multiple%20networks%20with%20the%20same%20accounts.%20All%20the%20subsidiary%20networks%20you%20merge%20into%20your%20primary%20network%20can't%20be%20created%20anymore.%20You%20can%20see%20all%20the%20domains%20connected%20to%20your%20network%20when%20you%20access%20the%20network%20merge%20wizard.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197647%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197647%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%2F2144%22%20target%3D%22_blank%22%3E%40Pooya%20Obbohat%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20do%20you%20mean%20by%20%22%3CSPAN%3Ethis%20will%20work%20as%20per%20MS%20said%22%3F%20Can%20you%20provide%20a%20link%20or%20screenshot%20of%20what%20MS%20has%20said%3F%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EI%20was%20refereeing%20to%20O365%20message%20%22consolidating%20yammer%20networks%22%26nbsp%3B%3CBR%20%2F%3EI%20mean%20i%20have%202%20internal%20network%20if%20I%20delete%20one%20internal%20network%20I%20will%20be%20left%20with%20only%20one%20internal%20network%20in%20my%20tenant%20So%2C%20I%20am%20no%20longer%20applied%20to%20yammer%20consolidation.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197645%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197645%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20do%20you%20mean%20by%20%22%3CSPAN%3Ethis%20will%20work%20as%20per%20MS%20said%22%3F%20Can%20you%20provide%20a%20link%20or%20screenshot%20of%20what%20MS%20has%20said%3F%20Personally%2C%20I%20don't%20consider%20Microsoft%20Teams%20as%20a%20replacement%20for%20Yammer.%20Microsoft%20Teams%20is%20missing%20the%20algorithm%2Ffeed%2C%20the%20all%20company%20group%2C%20it%20has%20a%20limit%20of%202%2C500%20members%2C%20requires%20users%20to%20join%20the%20Team%20to%20see%20the%20conversations%20etc.%20Microsoft%20is%20also%20adding%20new%20features%20to%20Yammer%2C%20such%20as%20live%20broadcasting.%20My%20recommendation%20would%20be%20not%20to%20switch%20to%20Microsoft%26nbsp%3BTeams%2C%20but%20use%20both%20applications.%20Use%20Microsoft%20Teams%20primarily%20to%20collaborate%20on%20projects%20(private%20Teams)%20and%20use%20Yammer%20for%20the%20communities%20(public%20groups).%20There%20is%20some%20redundancy%20between%20the%20applications%2C%20but%20there%20are%20too%20many%20differences%20IMHO%20to%20only%20select%20one%20of%20them.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20am%20familiar%20with%20Microsoft%20Teams%20and%20there%20is%20no%20feature%20to%20import%20data%20from%20Yammer.%20Migrating%20data%20from%20social%20networks%20isn't%20supported%20because%20this%20would%20require%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20using%20the%20same%20account%20to%20create%20the%20post%2Fcomments%20or%20they%20won't%20receive%20notifications%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20the%20timestamps%20need%20to%20be%20correct%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWould%20recommend%20watching%20this%20video%20from%20Ignite.%20It%20explains%20the%20differences%20between%20the%20applications.%20%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dqjv5VoSNdXw%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dqjv5VoSNdXw%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F34868iB118FFE901DF9D5C%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22yammerteams.PNG%22%20title%3D%22yammerteams.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%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-197633%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197633%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Pooya%20Obbohat%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20extremely%26nbsp%3Bgrateful%20for%20your%20clear%20explanation%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EAs%20I%20said%20before%20I%20have%202%20internal%20network%3C%2FP%3E%3CUL%3E%3CLI%3ENetwork1%20with%20less%20data%20and%20frequently%20used%3C%2FLI%3E%3CLI%3ENetwork2%20has%20larger%20number%20of%20users%20%26amp%3B%20data%20and%20daily%20used%26nbsp%3B%3C%2FLI%3E%3C%2FUL%3E%3CP%3EBut%20both%20network%20has%20the%20same%20users%20so%20I%20have%20decided%20to%20export%20Network1%20data%20and%20delete%20the%20Network1%20and%20replace%20them%20with%20Microsoft%20Team%20(Please%20confirm%20this%20will%20work%20as%20per%20MS%20said)%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EI%20hope%20you%20are%20familiar%20with%20Microsoft%20Teams%20Is%20anyway%20possible%20to%20import%2Fmove%20those%20yammer%20group%20to%20Microsoft%20Team%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThanks%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197192%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197192%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20problem.%20Understand%20the%20disappointment%20as%20losing%20data%20is%20the%20last%20thing%20you%20want%20to%20confront%20users%20with%2C%20but%20I%20wouldn't%20ditch%20Yammer%20because%20of%20this.%26nbsp%3BYou%20could%20use%20Microsoft%20Teams%2C%20but%20there%20is%20a%20limit%20of%202%2C500%20members.%20Yammer%20also%20has%20an%20algorithm%20to%20surface%20relevant%20conversations%2C%20something%20you%20won't%20find%20in%20another%20application%20in%20Office%20365.%20Yammer%20is%20the%20best%20application%20for%20communities%20IMHO.%20You're%20also%20not%20losing%20the%20external%20networks%2C%20they%20will%20all%20be%20connected%20to%20the%20parent%20network%20after%20the%20merge.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20lot%20of%20companies%20are%20not%20aware%20that%20they%20have%20multiple%20Yammer%20networks.%20This%20is%20because%20of%20the%20freemium%20design%20of%20Yammer%2C%20which%20was%20already%20there%20before%20the%20acquisition%20in%202012.%20They%20are%20addressing%20this%20now%20by%20consolidating%20multiple%20networks%20in%20September%20and%20not%20supporting%26nbsp%3Bthem%20going%20forward.%20This%20is%20the%20only%20time%20they%20will%20be%20confronted%20with%20data%20loss.%20The%20longer%20you%20wait%20with%20merging%20the%20networks%2C%20the%20more%20data%20will%20be%20lost%20and%20waiting%20for%20Microsoft%20to%20do%20it%20means%20losing%20data%20without%20any%20notice.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20some%20tips%20that%20could%20help%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Explain%20to%20the%20users%20why%20you%20have%20multiple%20networks%20(i.e.%20Yammer%20freemium%20design)%3C%2FP%3E%3CP%3E-%20Explain%20that%20Microsoft%20will%20merge%20the%20networks%20in%20September%20automatically%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Explain%20how%20important%20it%20is%20to%20have%20everyone%20connect%20to%20the%20same%20network%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Consider%20following%26nbsp%3Bthis%20up%20with%20a%20network%20launch%20(set%20up%20governance%20and%20improve%20the%20experience)%3C%2FP%3E%3CP%3E-%20Tell%20them%20to%20capture%20the%20members%20of%20their%20group%2C%20making%20it%20easier%20to%20add%20them%20later%3C%2FP%3E%3CP%3E-%20There%20are%20some%20instructions%20in%20this%20forum%20on%20how%20to%20get%20the%20members%20of%20large%20groups%3C%2FP%3E%3CP%3E-%20They%20can%20upload%20the%20files%20without%20creating%20new%20posts%20(click%20on%20the%20files%20tab%20and%20upload%20them%20there)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20helped%20several%20companies%20with%20merging%20their%20Yammer%20networks.%20The%20messaging%20to%20the%20users%20is%20key.%20Users%20won't%20like%20losing%20data%2C%20but%20they%20will%20understand%20when%20you%20share%20the%20bigger%20picture.%20This%20is%20why%20I%20go%20the%20extra%20mile%20to%20post%20an%20announcement%20in%20the%20all%20company%20group%20in%20their%20network%20as%20I%20prefer%20to%20be%20as%20transparent%20as%20possible%20during%20this%20process.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197180%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197180%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%2F2144%22%20target%3D%22_blank%22%3E%40Pooya%20Obbohat%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EThe%20network%20merge%20wizard%20is%20available%20on%20a%20network%20if%20you%20have%20an%20O365%20global%20admin%20account%20with%20an%20emails%20address%20from%20that%20domain.%20You%20can%20get%20it%20to%20appear%20on%20any%20network%20you%20want%2C%20but%20you%20should%20only%20use%20it%20on%20the%20network%20you%20want%20to%20keep.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMerging%20networks%20isn't%26nbsp%3Bthe%20same%20as%20migrating%20them.%20There%20are%20no%20migration%20options%20for%20Yammer.%20The%20data%20on%20the%20networks%20you%20merge%20into%20you%20parent%20network%20will%20be%20lost.%20All%20this%20does%20is%20connect%20your%20users%20to%20a%20different%20network.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20other%20things%20to%20keep%20in%20mind%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20I%20prefer%26nbsp%3Bhaving%20an%20admin%20account%20on%20all%20the%20networks.%20This%20allows%20me%20to%20post%20an%20announcement%20in%20the%20all%20company%20group%20to%20give%20them%20a%20heads-up%26nbsp%3Band%20answer%20any%20questions%20they%20might%20have.%20You%20can%20also%20use%20the%20report%20(O365%20admin%20center%20-%20reports)%20to%20get%20their%20info%20and%20send%20them%20an%20email.%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Recommend%20giving%20the%20users%20some%20time%20to%20create%20a%20backup%20of%20conversation%2Ffiles%20(they%20have%20to%20do%20this%20manually.%20You%20can%20export%20the%20data%20as%20an%20admin%2C%20but%20there%20are%20no%20options%20to%20import%20data.%20You%20would%20have%26nbsp%3Bto%20dive%20into%20the%20files%20to%20find%20what%20they%20need%20which%20will%20take%20a%20lot%20of%20time.%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Users%20get%20a%20%22welcome%20email%22%20when%20they%20are%20connected%20to%20a%20different%20Yammer%20network.%20You%20can%20temporarily%20block%20Yammer%20emails%20in%20Exchange%20when%20you%20are%20using%20the%20network%20merge%20wizard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CBR%20%2F%3EThanks%20for%20the%20clear%20explanation%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ESo%2C%20you%20can%20merge%20only%20users%20not%20data%3F%20What%20an%20idiotic%20move!!%26nbsp%3BWhat%20would%20I%20do%20with%20the%20backup%20which%20can't%20be%20imported%20back%20to%20yammer%3F%20So%20its%20likely%20we%20will%20lose%20all%20valuable%20conversations%20and%20datas%3CBR%20%2F%3E%3CBR%20%2F%3EVery%20disappointed...Time%20has%20come%20to%20ditch%20yammer%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197155%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197155%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20network%20merge%20wizard%20is%20available%20on%20a%20network%20if%20you%20have%20an%20O365%20global%20admin%20account%20with%20an%20emails%20address%20from%20that%20domain.%20You%20can%20get%20it%20to%20appear%20on%20any%20network%20you%20want%2C%20but%20you%20should%20only%20use%20it%20on%20the%20network%20you%20want%20to%20keep.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMerging%20networks%20isn't%26nbsp%3Bthe%20same%20as%20migrating%20them.%20There%20are%20no%20migration%20options%20for%20Yammer.%20The%20data%20on%20the%20networks%20you%20merge%20into%20you%20parent%20network%20will%20be%20lost.%20All%20this%20does%20is%20connect%20your%20users%20to%20a%20different%20network.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20other%20things%20to%20keep%20in%20mind%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20I%20prefer%26nbsp%3Bhaving%20an%20admin%20account%20on%20all%20the%20networks.%20This%20allows%20me%20to%20post%20an%20announcement%20in%20the%20all%20company%20group%20to%20give%20them%20a%20heads-up%26nbsp%3Band%20answer%20any%20questions%20they%20might%20have.%20You%20can%20also%20use%20the%20report%20(O365%20admin%20center%20-%20reports)%20to%20get%20their%20info%20and%20send%20them%20an%20email.%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Recommend%20giving%20the%20users%20some%20time%20to%20create%20a%20backup%20of%20conversation%2Ffiles%20(they%20have%20to%20do%20this%20manually.%20You%20can%20export%20the%20data%20as%20an%20admin%2C%20but%20there%20are%20no%20options%20to%20import%20data.%20You%20would%20have%26nbsp%3Bto%20dive%20into%20the%20files%20to%20find%20what%20they%20need%20which%20will%20take%20a%20lot%20of%20time.%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Users%20get%20a%20%22welcome%20email%22%20when%20they%20are%20connected%20to%20a%20different%20Yammer%20network.%20You%20can%20temporarily%20block%20Yammer%20emails%20in%20Exchange%20when%20you%20are%20using%20the%20network%20merge%20wizard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197121%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197121%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Pooya%20Obbohat%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20your%20reply%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EJust%20now%20I%20confirmed%20both%20my%20internal%20network%20are%20in%20same%20domain%20which%20is%20primary%20domain%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENetwork%20migration%20wizard%20is%20available%20for%20Network1%20only%20but%20not%20network2%20So%20as%20per%20your%20saying%20I%20can%20merge%20network2%20from%20network1%20and%20after%20I%20can%20able%20to%20access%20all%20the%26nbsp%3Bnetwork2%20data%20from%20network1%20url.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%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-196753%22%20slang%3D%22en-US%22%3ERe%3A%20We're%20consolidating%20Yammer%20networks%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-196753%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20need%20an%20O365%20global%20admin%20account%20on%20the%20same%20domain%20as%20the%20parent%20network%20(the%20network%20you%20want%20to%20keep).%20You%20can%20find%20a%20network%20merge%20wizard%20in%20the%20admin%20settings%20of%20that%20network%20and%20the%20networks%20you%20can%20%22migrate%22%20to%20the%20parent%20network%20will%20be%20listed%20there.%20You%20can%20create%20a%20ticket%20with%20MSFT%20support%20if%20you%20want%20to%20change%20the%20URL%20after%20performing%20the%20merge.%20This%20does%20require%20you%20to%20verify%20the%20domain%20in%20O365%20first.%20The%20reporting%20feature%20in%20the%20O365%20admin%20center%20has%20the%20info%20you%20need%20regarding%20the%20different%20networks%2Fstatistics%20(i.e.%20export%20user%20list%20and%20look%20at%20their%20email%20domains).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

                                                 

Action required by September 25, 2018

Starting September 26, 2018, Yammer will no longer support multiple internal Yammer networks associated with one Office 365 tenant. We will be consolidating your internal Yammer networks into a parent Yammer network. During this process, content will no longer be available from the subsidiary networks. We recommend you migrate your own networks prior to September 26.
This change does not impact external Yammer networks.

Question:
I have one tenant and multiple domain 
How do I know how many internal and external I have?
Which one is parent and subsidiary network?

Thanks


9 Replies

You need an O365 global admin account on the same domain as the parent network (the network you want to keep). You can find a network merge wizard in the admin settings of that network and the networks you can "migrate" to the parent network will be listed there. You can create a ticket with MSFT support if you want to change the URL after performing the merge. This does require you to verify the domain in O365 first. The reporting feature in the O365 admin center has the info you need regarding the different networks/statistics (i.e. export user list and look at their email domains). 

Hi Pooya Obbohat,

Thanks for your reply 

Just now I confirmed both my internal network are in same domain which is primary domain 

 

Network migration wizard is available for Network1 only but not network2 So as per your saying I can merge network2 from network1 and after I can able to access all the network2 data from network1 url. 

Thanks

 

 

 

The network merge wizard is available on a network if you have an O365 global admin account with an emails address from that domain. You can get it to appear on any network you want, but you should only use it on the network you want to keep. 

 

Merging networks isn't the same as migrating them. There are no migration options for Yammer. The data on the networks you merge into you parent network will be lost. All this does is connect your users to a different network. 

 

Some other things to keep in mind:

 

- I prefer having an admin account on all the networks. This allows me to post an announcement in the all company group to give them a heads-up and answer any questions they might have. You can also use the report (O365 admin center - reports) to get their info and send them an email. 

- Recommend giving the users some time to create a backup of conversation/files (they have to do this manually. You can export the data as an admin, but there are no options to import data. You would have to dive into the files to find what they need which will take a lot of time. 

- Users get a "welcome email" when they are connected to a different Yammer network. You can temporarily block Yammer emails in Exchange when you are using the network merge wizard

 

Hope this helps. 

 


@Pooya Obbohat wrote:

The network merge wizard is available on a network if you have an O365 global admin account with an emails address from that domain. You can get it to appear on any network you want, but you should only use it on the network you want to keep. 

 

Merging networks isn't the same as migrating them. There are no migration options for Yammer. The data on the networks you merge into you parent network will be lost. All this does is connect your users to a different network. 

 

Some other things to keep in mind:

 

- I prefer having an admin account on all the networks. This allows me to post an announcement in the all company group to give them a heads-up and answer any questions they might have. You can also use the report (O365 admin center - reports) to get their info and send them an email. 

- Recommend giving the users some time to create a backup of conversation/files (they have to do this manually. You can export the data as an admin, but there are no options to import data. You would have to dive into the files to find what they need which will take a lot of time. 

- Users get a "welcome email" when they are connected to a different Yammer network. You can temporarily block Yammer emails in Exchange when you are using the network merge wizard

 

Hope this helps. 

 



Thanks for the clear explanation 

So, you can merge only users not data? What an idiotic move!! What would I do with the backup which can't be imported back to yammer? So its likely we will lose all valuable conversations and datas

Very disappointed...Time has come to ditch yammer  

  

No problem. Understand the disappointment as losing data is the last thing you want to confront users with, but I wouldn't ditch Yammer because of this. You could use Microsoft Teams, but there is a limit of 2,500 members. Yammer also has an algorithm to surface relevant conversations, something you won't find in another application in Office 365. Yammer is the best application for communities IMHO. You're also not losing the external networks, they will all be connected to the parent network after the merge. 

 

A lot of companies are not aware that they have multiple Yammer networks. This is because of the freemium design of Yammer, which was already there before the acquisition in 2012. They are addressing this now by consolidating multiple networks in September and not supporting them going forward. This is the only time they will be confronted with data loss. The longer you wait with merging the networks, the more data will be lost and waiting for Microsoft to do it means losing data without any notice.

 

Here are some tips that could help:

 

- Explain to the users why you have multiple networks (i.e. Yammer freemium design)

- Explain that Microsoft will merge the networks in September automatically 

- Explain how important it is to have everyone connect to the same network 

- Consider following this up with a network launch (set up governance and improve the experience)

- Tell them to capture the members of their group, making it easier to add them later

- There are some instructions in this forum on how to get the members of large groups

- They can upload the files without creating new posts (click on the files tab and upload them there)

 

Have helped several companies with merging their Yammer networks. The messaging to the users is key. Users won't like losing data, but they will understand when you share the bigger picture. This is why I go the extra mile to post an announcement in the all company group in their network as I prefer to be as transparent as possible during this process. 

 

Hi Pooya Obbohat,

I am extremely grateful for your clear explanation

As I said before I have 2 internal network

  • Network1 with less data and frequently used
  • Network2 has larger number of users & data and daily used 

But both network has the same users so I have decided to export Network1 data and delete the Network1 and replace them with Microsoft Team (Please confirm this will work as per MS said) 

I hope you are familiar with Microsoft Teams Is anyway possible to import/move those yammer group to Microsoft Team?


Thanks 

 

What do you mean by "this will work as per MS said"? Can you provide a link or screenshot of what MS has said? Personally, I don't consider Microsoft Teams as a replacement for Yammer. Microsoft Teams is missing the algorithm/feed, the all company group, it has a limit of 2,500 members, requires users to join the Team to see the conversations etc. Microsoft is also adding new features to Yammer, such as live broadcasting. My recommendation would be not to switch to Microsoft Teams, but use both applications. Use Microsoft Teams primarily to collaborate on projects (private Teams) and use Yammer for the communities (public groups). There is some redundancy between the applications, but there are too many differences IMHO to only select one of them. 

 

I am familiar with Microsoft Teams and there is no feature to import data from Yammer. Migrating data from social networks isn't supported because this would require:

 

- using the same account to create the post/comments or they won't receive notifications 

- the timestamps need to be correct

 

Would recommend watching this video from Ignite. It explains the differences between the applications. https://www.youtube.com/watch?v=qjv5VoSNdXw

 

yammerteams.PNG

 

 

 

Tired of "what to use when"? Stop in for a refreshing dose of "HOW and WHY" and judge if it's right for you. Simon Denton of Mott MacDonald and Melanie Hoher...

@Pooya Obbohat wrote:

 

What do you mean by "this will work as per MS said"? Can you provide a link or screenshot of what MS has said? 


I was refereeing to O365 message "consolidating yammer networks" 
I mean i have 2 internal network if I delete one internal network I will be left with only one internal network in my tenant So, I am no longer applied to yammer consolidation.  

When you merge/consolidate the networks and only have 1 network left, then in September Microsoft can't consolidate multiple networks for you. They won't support multiple networks going forward, which means that new accounts will automatically be created in the network you already have. 

 

You can't really "delete" a network. You have to use the network merge wizard. You could remove the domain from your tenant, but I wouldn't recommend doing that. You mentioned having the same users on both networks. This happens when your users have multiple email accounts with different domains or when emails sent to a different email address end up in their email inbox. Merging the networks will result in duplicate accounts. You have to enforce Office 365 identities in your parent network to address this. This will deactivate accounts not associated with an Office 365 account and remove them from search. The external networks will be connected to your parent network, but they won't have access to them because their accounts will be deactivated. As an admin, you have access to all external networks after the merge, allowing you to give the correct account admin priveledges. 

 

Can still imagine that you can end up having multiple networks before September. As an example: when you add a new domain to the tenant and users can use that email address to sign up for an account on Yammer, this will result in a new network. Another scenario is that you already have an additional domain, but users never signed up for an account on Yammer using that email address. This problem shouldn't be there anymore after September as they will stop supporting multiple networks. Would recommend monitoring this and figuring out why you have multiple networks with the same accounts. All the subsidiary networks you merge into your primary network can't be created anymore. You can see all the domains connected to your network when you access the network merge wizard.