2 Yammers for 1 office 365 tenant?

%3CLINGO-SUB%20id%3D%22lingo-sub-17344%22%20slang%3D%22en-US%22%3E2%20Yammers%20for%201%20office%20365%20tenant%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-17344%22%20slang%3D%22en-US%22%3E%3CP%3EToday%20I%20helped%20one%20of%20our%20end%20users%20join%20yammer%20by%20opening%20the%20waffle%20in%20the%20top%20left%20hand%20corner%20and%20clicking%20on%20yammer.%20Once%20he%20was%20in%20we%20saw%20that%20he%20was%20not%20in%20the%20main%20Yammer%20for%20our%20organization%2C%20but%20some%20sort%20of%20alternate%20yammer%20environment%20with%20a%20different%20name%20then%20ours.%20Can%20you%20help%20me%20figure%20out%20why%20this%20is%20happening%20and%20how%20to%20move%20the%20users%20that%20are%20in%20the%20other%20environment%20over%20to%20our%20appropriate%20one%3F%20Need%20to%20make%20sure%20in%20the%20future%20when%20people%20join%20yammer%20they%20are%20put%20in%20the%20appropriate%20environment%20and%20get%20rid%20of%20the%20alternate%20one%20completely.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-17344%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-17544%22%20slang%3D%22en-US%22%3ERe%3A%202%20Yammers%20for%201%20office%20365%20tenant%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-17544%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4803%22%20target%3D%22_blank%22%3E%40Amy%20Straley%3C%2FA%3E%2C%20I%20found%20this%20Migration%20Guide%20online.%20Since%20we%20were%20not%20worried%20about%20retaining%20the%20data%20in%20the%20false%20networks%20we%20migrated%20users%20pretty%20easily.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-gb%2Farticle%2FNetwork-migration-Consolidate-multiple-Yammer-networks-a22c1b20-9231-4ce2-a916-392b1056d002%3Fui%3Den-US%26amp%3Brs%3Den-GB%26amp%3Bad%3DGB%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-gb%2Farticle%2FNetwork-migration-Consolidate-multiple-Yammer-networks-a22c1b20-9231-4ce2-a916-392b1056d002%3Fui%3Den-US%26amp%3Brs%3Den-GB%26amp%3Bad%3DGB%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-17543%22%20slang%3D%22en-US%22%3ERe%3A%202%20Yammers%20for%201%20office%20365%20tenant%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-17543%22%20slang%3D%22en-US%22%3E%3CP%3EWeve%20had%20several%20situations%20where%20folks%20were%20logging%20on%20with%20a%20different%20email%20domain%20(still%20our%20company's%2C%20but%20not%20the%20same%20as%20our%20internal%20network).%20They%20were%20getting%20sent%20to%20a%20separate%20yammer%20network%20for%20that%20domain.%20I%20had%20to%20get%20a%20dummy%20email%20address%20from%20each%20of%20our%20domains%20and%20be%20set%20as%20the%20admin%2C%20then%20suspend%20them%20in%20those%20other%20networks%20and%20re-invite%20them%20to%20the%20network%20with%20the%26nbsp%3Bcorrect%20email%20address.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-17504%22%20slang%3D%22en-US%22%3ERe%3A%202%20Yammers%20for%201%20office%20365%20tenant%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-17504%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20probably%20don't%20have%20your%20primary%20network%20associated%20with%20your%20Office%20365%20tenant%2C%20it's%20important%20that%20you%20do%20for%20all%20the%20new%20features%20to%20light%20up%20as%20well.%20More%20on%20this%20is%20described%20here%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-gb%2Farticle%2FAbout-Yammer-networks-and-Office-365-tenants-85516b0c-79ad-4483-8534-4477c8d26e1a%3Fui%3Den-US%26amp%3Brs%3Den-GB%26amp%3Bad%3DGB%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-gb%2Farticle%2FAbout-Yammer-networks-and-Office-365-tenants-85516b0c-79ad-4483-8534-4477c8d26e1a%3Fui%3Den-US%26amp%3Brs%3Den-GB%26amp%3Bad%3DGB%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Super Contributor

Today I helped one of our end users join yammer by opening the waffle in the top left hand corner and clicking on yammer. Once he was in we saw that he was not in the main Yammer for our organization, but some sort of alternate yammer environment with a different name then ours. Can you help me figure out why this is happening and how to move the users that are in the other environment over to our appropriate one? Need to make sure in the future when people join yammer they are put in the appropriate environment and get rid of the alternate one completely.

3 Replies

You probably don't have your primary network associated with your Office 365 tenant, it's important that you do for all the new features to light up as well. More on this is described here

 

https://support.office.com/en-gb/article/About-Yammer-networks-and-Office-365-tenants-85516b0c-79ad-...

 

 

Weve had several situations where folks were logging on with a different email domain (still our company's, but not the same as our internal network). They were getting sent to a separate yammer network for that domain. I had to get a dummy email address from each of our domains and be set as the admin, then suspend them in those other networks and re-invite them to the network with the correct email address. 

@Amy Straley, I found this Migration Guide online. Since we were not worried about retaining the data in the false networks we migrated users pretty easily. 

https://support.office.com/en-gb/article/Network-migration-Consolidate-multiple-Yammer-networks-a22c...