Forum Discussion
"New" to Viva Engage, with over 100 existing M365 Groups (private) - how to approach communities?
Hi,
I have used Yammer in the past (pre 2016) and have refrained and not encouraged usage in our organization due to the very disconnected user experience and also not having the ressources to manage yet another channel of communications.
I want revisit the current Viva Engage situation. I've let the Yammer Support reprovision our network for EU data residency, so it's completely empty. By reading the documentation I would assume we're about as aligend to M365 as is possible.
It seems like I can create Communities that are connected to M365 Groups by-default, but I haven't found the other way around.
What am I todo with our existing 100 private M365 Groups that mostly represent organizational departments, project teams, larger organizational topics/interests?
Are we expected to re-create all these groups? Are there any useful "migration" paths/ideas for this scenario?
I'm really not a fan of M365 Groups clutter and also do not allow the creation of groups outside of administrator for this very reason.
any help or further links to other resources are high appreciated.
2 Replies
- Many of your M365 Groups are not good candidates for a VE community (e.g. project team). Large topics or organizations would be more applicable.
Note that an M365 Group can have email and/or Teams but can't also have Viva Engage. M365 Groups created by creating a community in VE don't get the email / teams features. So, if the team members are using email/teams, then they likely will need to keep those rather than having everything for the M365 group flow to VE. Yeah so all communities will be M365 groups!
Unfortunately you will need to reprovision those groups if you want to have them as Yammer communities!
Easiest way of doing this identifying them, and recreate them via API using Power automate and then moving all the files and adding those users!I know it's not Ideal
