Disable Sharing Outside of Private Group
I work in a large organization, and we have many private groups to avoid employees getting tired of seeing posts that are not relevant to them. However, it is difficult to tell whether a group is private or not, so users often end up sharing posts from private groups. Is there a way to disable the sharing option in our group? And could you please make it easier to see when a post is in a private group?
Viva Engage connection with MFA
I'm not able to connect to https://engage.cloud.microsoft/main/org/microsoft.com, where I'm was added as member of several communities (I received notifications with "You have been added on..."). I'm requested to log on using my work account. All options fail: Using passkey: "Something went wrong" Using Authenticator app: "Request wasn't sent" (I approved the request.) Using password: "Your account or password is incorrect." (I entered the correct password.) It could be something with connection between my company and Microsoft. My organization has passwordless logon. Is this something that Microsoft or my organization has to fix?Enhancements wanted for Viva Engage Event Experience
In the Event tab within Viva Engage Communities it would be great with some improvements to enhance the usage and customization of Events. Similar to Facebook and Workplace events where participants had the possibility to select "Attending" and "Not attending". We have cases where we plan in person events where it would be really helpful to get an overview of participants that are attending. Similar to Facebook and Workplace events where participants had the possibility to select "Attending" and "Not attending". Additionally, giving users the ability to add events directly to their calendars would help them stay organized and maintain a better overview of company activities. To summarize very wanted features are: The options for participants to click Attending/Not attending. Option to "Add to Calendar" directly from the event page The ability to mark the event as In Person Is this on Microsoft's Roadmap for enhancements, or could it be considered for future updates?
Inline images still not available for Discussions and Questions
I understand that "Articles" is a new premium feature for Viva Engage that allows inline images when creating an article. However, does anyone know why inline images are still not available in "Discussions" and "Questions" post options? This feature has been missing since day one for those post types. Although it became available last year with "Articles," it has yet to be integrated into the most frequently used post types in Engage, where it is desperately needed. What is the reasoning behind this?
Usage Of Custom Email Domain for Viva Engage communications
Can you use a custom domain for all Viva Engage communications? Currently there's security concerns that emails from Viva Engage can not be allow listed since they use the same domain other tenants use. We have security concerns this maybe exploited by attackers looking to exploit the platform in malicious email attacks. What controls are there (if any) to send engagements from our custom accepted domain for the tenant so our cybersecurity teams don't have security concerns? Also can you provide documentation that keeps the platform from being exploited by a threat actors from targeting other Microsoft 365 tenants? What controls have been implemented to keep this from being active exploited? Or has this been considered? This has legitimate concerns from our cybersecurity teams. Defender 365 solutions are not an acceptable answer.
Private Communities: Enable "Unlisted" Status and Hide Membership on Storylines
When using private communities in Viva Engage, it's not always desirable for these communities to be discoverable. A welcome addition would be the ability to set an Engage community as both private and unlisted, thereby removing the option for users to apply for membership. Currently, if a user is a member of a private community, this membership is visible to others on that user's storyline. This means it's possible to piece together the membership of private communities by viewing individual users' storylines.Users in "view-only mode" get stuck in the Acceptable Use Policy
Background I work with a company that is using Viva Engage. In some of their Communities, they have set restrictions so that only those who are Community Admins are allowed to post posts. When a Community Admin create a post and attaches an Excel file to the post, the Excel file is editable by all members of the Community. (Actually, it would have been optimal if the setting that limits who can post posts had also limited the ability to edit attached files, but that is not the case.) The setting i have tested Therefore, i tested "Manage user privileges with view-only mode in Viva Engage". As a Viva Engage administrator, I opened the Viva Admin Center and opened the "Governance and Compliance" tab. Under this tab there is an option called "User Management" where you can "adjust user settings surrounding the creation and visibility of contents". This sounded good, so I added the users that I wanted to limit these possibilities for so that they would basically only have read-only access to the community. The problem that arises This is where the strange problem arises. When these users, who I added under "User Management" now enter a community, the window with "Acceptable Use Policy" appears and it is completely OK but after that there is no possibility to accept, close or exit this window. Is this a bug or is there any additional setting that I have to turn on for this to work as intended?
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 - News in 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!
