Feedback by UserVoice

Rob Hardman

My feedback

  1. 484 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    101 comments  ·  Yammer  ·  Flag idea as inappropriate…  ·  Admin →

    This isn’t currently prioritized, but we’re considering it. Feel free to tell us more about why this would be important to you – it’s helpful for us to have context as we discuss it. Thank you!

    An error occurred while saving the comment
    Rob Hardman commented  · 

    Bump! Feature still not available, lack of feature still causing unnecessary 365 Group sprawlage...

    Rob Hardman supported this idea  · 
    An error occurred while saving the comment
    Rob Hardman commented  · 

    I can't believe it's still not implemented! If you consider that most organisations start with O365 groups (or latterly, perhaps Teams) and not Yammer, it's preposterous to think that creating a duplicate O365 SP site for a Yammer community could somehow be superior that just allowing the admin to choose which existing SP site to connect the new Yammer community to.

    It's a complete blocker to Yammer adoption for us... it's hard enough to educate users to when to Teams and when to Yammer... telling them "this {dept} SP site, not that {dept} SP site" will bewilder them! 🤦🏻‍♂️

    An error occurred while saving the comment
    Rob Hardman commented  · 

    It's incredibly frustrating that this isn't even on the backlog yet. We have established O365 groups with associated Teams, SP Sites, Plans etc. Duplicating an O365 group on Yammer group creation creates nothing but confusion and a needless duplication of resources.

    It's actually killed our Yammer deployment! We are forced to retain, at additional cost, Facebook Workplace (which ironically, does allow the connection of a SharePoint library to an existing group.) :\

Feedback and Knowledge Base

User Voice Terms of Service & Privacy Policy