Default Sharepoint Permissions Set to Everyone for Public Communities
In native mode, it appears that when a new community is created as public, the corresponding sharepoint site that is created gives "Everyone except external users" site member access. This means that even users who are restricted from using Viva Engage via the option to block unlicensed users are able to see files and resources that have been uploaded to that community. This is a particular problem in environments where some users need restricted access, such as Students in an education environment. Is there a way to change this behaviour, or set a default public group? The only solution we can think of is to either set all communities to private (which diminishes the user experience of Viva Engage), or to ensure that Sharepoint permissions are updated manually whenever a new community is created. Any help greatly appreciated.
Seeking recommended steps to delete "All Company"
I have a scenario where an existing dated "All Company" community exists in Viva Engage from Yammer days and dating back to 4 or so years ago. The contents of this community (including posts, members, etc) are no longer relevant to the organisation as it has evolved a lot since then. The organisation now wants to adopt Viva Engage as an ESN but with a "fresh start". So they are keen to delete all existing communities, including the All Company one. I would like to understand if there is a best practice way to deleting an "All Company" community in Viva Engage? This help article (https://learn.microsoft.com/en-us/viva/engage/manage-viva-engage-groups/all-company-community) seems to indicate that the "All Company" community can be treated like any other regular community: "You can delete All Company in Microsoft Entra ID, which takes it through a soft-delete and then a hard-delete process." However, people in this discussion thread - as recent as Oct 2024, have reported having difficulties: https://techcommunity.microsoft.com/discussions/viva_engage_administration/delete-default-all-company/4186461 The thread indicates that if someone deletes the All Company - the community continues to show as existing for users - leading to an experience where people click on the community only to find it is deleted. I am wondering if there is a recommended way to delete and re-creating the All Company community? For example should we delete the relevant M365 group from Entra? If yes - when we recreate the community - do we do it from Engage and then go to Entra to set some additional properties to indicate it is the new "All Company"?
Allowing guest accounts and/or multi tenant synced users to discover new communities in Viva Engage
Hi, We have performed a multi tenant syncronization with a company with the purpose of enabling more effective collaboration as if we belonged to the same tenant In Viva. We have invited the synced microsoft users to our Viva Engage portal. Because of the sync, the users are no longer marked as 'guests' in Viva Engage. However, the issue is, once synced the users (who are added to Viva as members, not guests) still cannot discover new communities in Viva that they have not been invited to (as if they where guests). Is there any way of enabling this? I was looking into setting of 'Native mode' / 'non-native mode' / 'hybrid-mode' and was hoping perhaps that could be of use. Big thank you in advance!🤘Join us for the annual Viva Engage Festival, hosted by Swoop Analytics! 🤘
We are thrilled to invite you to the annual Viva Engage Festival, a celebration of our incredible journey together hosted by Swoop! This year's event promises to be bigger and better, featuring inspiring customer stories from the start of adoption to successful launches, engaging leadership sessions, and an exclusive product leadership Q&A. ✨Why You Can't Miss This Event✨ Customer Stories: Hear firsthand experiences from other customers about their journey with Viva Engage, from initial adoption to successful implementation. Leadership Engagement:Connect with our product leaders and gain insights into the future of Viva Engage. Product Leadership Q&A: Get your questions answered by our product leaders in Ask me Anything interactive sessions. Check out the full agenda here. Networking Opportunities: Meet and network with other customers and industry experts. Recorded Sessions: All sessions will be recorded and shared afterwards, so you won't miss a thing! Here's a look back at the past sessions! 📅 Date: Wednesday, December 4, 2024 🔗 Register Here🔗 APAC EMEA AMER Don't miss out on joining this FREE event hosted by Swoop Analytics that celebrates our customer community, and the amazing progress we've made together. We look forward to seeing you there! The Swoop Benchmarking study is now available. Download it here! The report is also loaded with real-life case study examples so you can learn from the best!
Merge 2 communities in Viva engage and delete one
Hello Members, Please help me with this requirement below a) Remove/close this viva community - News - 6.2k users b) Continue with this community only - Newsin Exchange - 4.7k users When the News group is deleted, it would be good if the people that are in group a) are automatically added to group b) so they don´t need to enter another group on their own. Is there a proper process/solution for this? Thanks!Create feed from Viva Engage to intranet
Hi, We are upgrading our intranet and we want to include a feed from Viva Engage (e.g. JSON or XML) to our intranet from a particular channel that we have created. https://engage.cloud.microsoft/main/org/investni.com/groups/eyJfdHlwZSI6Ikdyb3VwIiwiaWQiOiIyMDYyODQ2NTI1NDQifQ/new How would I do that? Thank you for your time, OllieAssistance Required: Microsoft Viva Engage Native Mode Upgrade Failure (ID: MV906775)
Hello everyone, I’ve recently received an email from Microsoft with the subject "Microsoft Viva Engage Native Mode upgrade failed in your tenant" (ID: MV906775). However, I'm struggling to understand the issue and couldn’t find any clear details in the Microsoft 365 admin portal. The email mentioned the following: The network was upgraded to Native Mode but certain pre-conditions prevented the upgrade from being completed. It referenced previous communication (Message center post MC424414) regarding the upgrade from Non-Native Mode or hybrid Networks to Native Mode to align with Azure AD and Microsoft 365. As this issue needs action from my end to proceed with the upgrade, could someone help me with: What specific pre-conditions could cause this upgrade failure? How can I identify and resolve these issues in my tenant? If any previous users encountered this, what steps did you take to fix the issue? Any guidance would be greatly appreciated. Thank you in advance for your help! Best regards, Janak Khadka
