Microsoft Viva Engage AMA

Thank you for your reply. I think it is just a matter of being able to utilize Yammer/Viva Engage for both internal and external purposes. Intneral purposes implies that the discussions are going to be sensitive. External purposes might mean a community for a partner, vendor, supplier, etc. So, with internal communities, we would not want guests to be allowed at all. With external communities, partners, vendors, etc. would become guests of the community. So, without "per community settings", that will not be feasible. Another thing related to this problem is the fact that "Private" communities are still visible from the "All Communities" list. So, it should probably also be a "per community setting" for a community admin to decide if a "Private" community is visible for others to ask to join OR completely hidden so the community admin can explicity invite users to join. There are scenarios like that where the user experience of Yammer is a better fit than Teams...but that's not possible right now. Dynamic Group membership also doesn't really solve that problem.