SOLVED

#Joined Notification in Yammer

%3CLINGO-SUB%20id%3D%22lingo-sub-2119%22%20slang%3D%22en-US%22%3E%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2119%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%201100%20user%20tenant.%20I%20heard%20%23Joined%20messages%20were%20going%20away%20for%20large%20orgs%20but%20were%20still%20seeing%20them.%20Any%20timeline%20on%20when%20they%20will%20stop%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2119%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEnterprise%20Social%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-103635%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-103635%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20further%20word%20on%20removing%20this%20-%20or%20making%20it%20optional%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'd%20much%20rather%20have%20a%20feed%20full%20of%20queries%20and%20collaboration%20rather%20than%20a%20static%20message%20that%20tells%20me%20something%20that%20cannot%20be%20actioned.%20And%20then%2C%20notifies%20all%20users%20by%20email.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegardless%20of%20'testing%20done'%20in%20controlled%20user%20groups%20-%20there%20is%20a%20chance%20their%20thoughts%20aren't%20applicable%20globally.%20If%20you%20really%20need%20this%20feature%2C%20could%20you%20give%20our%20O365%20admins%20the%20ability%20to%20disable%20the%20welcome%20%2F%20joined%20post%20and%20subsequent%20all%20company%20email%20notification%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70519%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70519%22%20slang%3D%22en-US%22%3E%3CP%3ETom%2C%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20having%20an%20issue%20with%20the%20flow.%20When%20the%20Flow%20posts%20the%20message%20to%20the%20new%20group%2C%20it%20also%20reposts%20the%20%23Joined%20topic.%20Because%20I%20am%20following%20the%20topic%2C%20the%20flow%20sees%20it%20in%20the%20new%20group%2C%20and%20gets%20itself%20into%20a%20never%20ending%20loop%20of%20creating%2Fdeleting%20the%20messages%2C%20and%20each%20time%20it%20does%20this%20it%20adds%20another%20iteration%20of%20my%20name%20to%20the%20post.%20then%20deletes%20the%20post.%20then%20posts%20again!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20suggetions%20on%20how%20to%20correct%3F%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20735px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F14707i765441A7CC88A923%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22flow.PNG%22%20title%3D%22flow.PNG%22%20%2F%3E%3C%2FSPAN%3Eing%2Fdeleting%20the%20messages.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61658%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61658%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Microsoft%2C%3C%2FP%3E%3CP%3Ecan%20you%20please%20specify%20the%20number%20of%20user%20since%20which%20the%20%23joined%20message%20will%20be%20not%20visibile%20anymore%3F%3C%2FP%3E%3CP%3EFrom%20my%20company%20experience%20it%20has%20been%20something%20around%201750%20user%20more%20or%20less.%3C%2FP%3E%3CP%3EFor%20sure%20it%20was%20not%201100.%3C%2FP%3E%3CP%3ECan%20you%20please%20some-one%20tell%20to%20us%20the%20PROPER%20number%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThanks%3C%2FP%3E%3CP%3ELAura%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-13855%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-13855%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20also%20put%20in%20a%20mail%20transport%20rule%20to%20block%20these%20messages%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%E2%80%A2%20Welcome%20to%20Yammer%20email%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBlock%20if%3A%3CBR%20%2F%3EFrom%20Domain%3A%20Yammer.com%3CBR%20%2F%3ESubject%20Contains%3A%20welcome%20to%20the%20%3CCOMPANY%20name%3D%22%22%3E%20network%20on%20Yammer%3C%2FCOMPANY%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2165%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2165%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20empirical%20experience%20is%20that%20the%20joined%20messages%20will%20stop%20at%201000%20users%2C%20but%20let%20us%20know%20what%20your%20expereince%20is%2C%20since%20there%20are%20no%20official%20annoucements.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2141%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2141%22%20slang%3D%22en-US%22%3E%3CP%3EThere's%20never%20been%20official%20word%20on%20what%20the%20new%20limit%20is%2C%20but%20when%20the%20network%20achieves%20this%20number%2C%20then%20the%20posts%20stop.%26nbsp%3B%20Until%20then%2C%20you%20are%20welcome%20to%20try%20my%20method%20for%20using%20Flow%26nbsp%3Bto%20move%20messages%20however%20you%20would%20choose.%26nbsp%3B%20(Attached)%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-2136%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2136%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Robert%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere's%20a%20post%20from%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3506%22%20target%3D%22_blank%22%3E%40Juliet%20Wei%3C%2FA%3E%20(Yammer%20product%20team).%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%22Yammer%20is%20now%20growing%20faster%20than%20ever%20and%20as%20such%20we've%20received%20feedback%20from%20our%20fastest%20growing%20networks%20that%20the%20All%20Company%20group%20is%20getting%20overwhelmed%20by%20the%3CA%20class%3D%22yammer-object%22%20dir%3D%22auto%22%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fitpronetwork%2Ftopics%2F6258528%22%20data-yammer-object%3D%22tag%3A4382272%22%20data-resource-id%3D%224382272%22%20data-resource-model%3D%22tag%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%23joined%3C%2FA%3E%20messages%20from%20new%20users.%20While%20these%20messages%20have%20proven%20useful%20at%20introducing%20new%20members%20to%20your%20networks%2C%20we%20realize%20that%20with%20the%20increased%20pace%20of%20growth%2C%20we%20need%20a%20better%20way%20to%20manage%20this%20process.%20%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3ESeveral%20weeks%20ago%2C%20we%20ran%20some%20experiments%20to%20determine%20the%20effect%20of%20removing%20the%3CA%20class%3D%22yammer-object%22%20dir%3D%22auto%22%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fitpronetwork%2Ftopics%2F6258528%22%20data-yammer-object%3D%22tag%3A4382272%22%20data-resource-id%3D%224382272%22%20data-resource-model%3D%22tag%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%23joined%3C%2FA%3E%20message%20for%20different%20sized%20networks.%20Initial%20findings%20from%20our%20experiments%20showed%20that%20turning%20%3CA%20class%3D%22yammer-object%22%20dir%3D%22auto%22%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fitpronetwork%2Ftopics%2F6258528%22%20data-yammer-object%3D%22tag%3A4382272%22%20data-resource-id%3D%224382272%22%20data-resource-model%3D%22tag%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%23joined%3C%2FA%3E%20messages%20off%20for%20smaller%20networks%20negatively%20impacted%20engagement%2C%20which%20led%20to%20the%20decision%20to%20keep%20%3CA%20class%3D%22yammer-object%22%20dir%3D%22auto%22%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fitpronetwork%2Ftopics%2F6258528%22%20data-yammer-object%3D%22tag%3A4382272%22%20data-resource-id%3D%224382272%22%20data-resource-model%3D%22tag%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%23joined%3C%2FA%3E%20messages%20enabled%20for%20networks%20smaller%20than%2020%2C000%20active%20users.%20%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3ESince%20then%20we've%20heard%20feedback%20and%20seen%20that%20the%20%3CA%20class%3D%22yammer-object%22%20dir%3D%22auto%22%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fitpronetwork%2Ftopics%2F6258528%22%20data-yammer-object%3D%22tag%3A4382272%22%20data-resource-id%3D%224382272%22%20data-resource-model%3D%22tag%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%23joined%3C%2FA%3E%20message%20is%20also%20noisy%20in%20smaller%20networks%20during%20periods%20of%20accelerated%20growth.%20Based%20on%20that%20feedback%20and%20the%20fact%20we%20plan%20to%20replace%20this%20solution%20with%20a%20more%20scalable%20solution%20in%20the%20future%2C%20we've%20decided%20to%20lower%20the%20network%20size%20limit%20to%20a%20much%20smaller%20number%2C%20which%20means%20that%20most%20networks%20will%20now%20see%20no%20more%20new%20%3CA%20class%3D%22yammer-object%22%20dir%3D%22auto%22%20href%3D%22https%3A%2F%2Fwww.yammer.com%2Fitpronetwork%2Ftopics%2F6258528%22%20data-yammer-object%3D%22tag%3A4382272%22%20data-resource-id%3D%224382272%22%20data-resource-model%3D%22tag%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%23joined%3C%2FA%3E%20messages%20in%20All%20Company.%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3EWe%20hope%20you%20find%20this%20change%20useful%20and%20truly%20appreciate%20the%20feedback%20we've%20received%20from%20our%20customer%20base%20to%20date.%20We'll%20continue%20monitoring%20customer%20feedback%20and%20our%20engagement%20numbers%20to%20refine%20the%20cut%20off%20logic%20as%20needed%20over%20the%20coming%20months.%22%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%2C%20if%20you%20are%20still%20seeing%20%23joined%20messages%20please%20open%20a%20support%20ticket.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI've%20also%20attached%26nbsp%3Ba%20document%20created%20by%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F55%22%20target%3D%22_blank%22%3E%40Tom%20Kretzmer%3C%2FA%3E%26nbsp%3Bon%20how%20to%20move%26nbsp%3Bjoined%20messages%20with%20Flow.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899242%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899242%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F452%22%20target%3D%22_blank%22%3E%40Robert%20Woods%3C%2FA%3E%26nbsp%3BHi%20all%2C%20removing%20the%20dust%20from%20this%20discussion.%20Any%20update%20on%20this%20subject%20and%20specifically%20on%20the%20number%20of%20users%20who%20have%20to%20join%20Yammer%20before%20the%20%23joined%20messages%20are%20disabled%20in%20the%20%23AllCompany%20feed%3F%20(I'm%20aware%20of%20the%20workaround%20with%20Flow)%20Thx!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899638%22%20slang%3D%22en-US%22%3ERe%3A%20%23Joined%20Notification%20in%20Yammer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899638%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F159270%22%20target%3D%22_blank%22%3E%40Joris%20Kok%3C%2FA%3E%26nbsp%3BUnfortunately%20we%20were%20never%20able%20to%20get%20the%20users%20to%20engage%20with%20Yammer%2C%20we%20eventually%20disabled%20the%20service%20because%20it%20was%20just%20a%20page%20of%20Joined%20messages%20that%20new%20users%20always%20questioned.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Super Contributor

Hello, 1100 user tenant. I heard #Joined messages were going away for large orgs but were still seeing them. Any timeline on when they will stop?

9 Replies
best response confirmed by Robert Woods (Super Contributor)
Solution

Hi Robert, 

 

Here's a post from @Juliet Wei (Yammer product team). 

 

"Yammer is now growing faster than ever and as such we've received feedback from our fastest growing networks that the All Company group is getting overwhelmed by the#joined messages from new users. While these messages have proven useful at introducing new members to your networks, we realize that with the increased pace of growth, we need a better way to manage this process.

Several weeks ago, we ran some experiments to determine the effect of removing the#joined message for different sized networks. Initial findings from our experiments showed that turning #joined messages off for smaller networks negatively impacted engagement, which led to the decision to keep #joined messages enabled for networks smaller than 20,000 active users.

Since then we've heard feedback and seen that the #joined message is also noisy in smaller networks during periods of accelerated growth. Based on that feedback and the fact we plan to replace this solution with a more scalable solution in the future, we've decided to lower the network size limit to a much smaller number, which means that most networks will now see no more new #joined messages in All Company.

We hope you find this change useful and truly appreciate the feedback we've received from our customer base to date. We'll continue monitoring customer feedback and our engagement numbers to refine the cut off logic as needed over the coming months."

 

So, if you are still seeing #joined messages please open a support ticket. 

 

I've also attached a document created by @Tom Kretzmer on how to move joined messages with Flow. 

There's never been official word on what the new limit is, but when the network achieves this number, then the posts stop.  Until then, you are welcome to try my method for using Flow to move messages however you would choose.  (Attached)

 

 

My empirical experience is that the joined messages will stop at 1000 users, but let us know what your expereince is, since there are no official annoucements.

You can also put in a mail transport rule to block these messages:

 

• Welcome to Yammer email

 

Block if:
From Domain: Yammer.com
Subject Contains: welcome to the <company name> network on Yammer

Hi Microsoft,

can you please specify the number of user since which the #joined message will be not visibile anymore?

From my company experience it has been something around 1750 user more or less.

For sure it was not 1100.

Can you please some-one tell to us the PROPER number?


Thanks

LAura

Tom, 

I am having an issue with the flow. When the Flow posts the message to the new group, it also reposts the #Joined topic. Because I am following the topic, the flow sees it in the new group, and gets itself into a never ending loop of creating/deleting the messages, and each time it does this it adds another iteration of my name to the post. then deletes the post. then posts again!

 

Any suggetions on how to correct?flow.PNGing/deleting the messages. 

Any further word on removing this - or making it optional?

 

I'd much rather have a feed full of queries and collaboration rather than a static message that tells me something that cannot be actioned. And then, notifies all users by email.

 

Regardless of 'testing done' in controlled user groups - there is a chance their thoughts aren't applicable globally. If you really need this feature, could you give our O365 admins the ability to disable the welcome / joined post and subsequent all company email notification?

 

@Robert Woods Hi all, removing the dust from this discussion. Any update on this subject and specifically on the number of users who have to join Yammer before the #joined messages are disabled in the #AllCompany feed? (I'm aware of the workaround with Flow) Thx!

@Joris Kok Unfortunately we were never able to get the users to engage with Yammer, we eventually disabled the service because it was just a page of Joined messages that new users always questioned.