Forum Widgets
Latest Discussions
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.
Troubles with Embedded Viva Engage
Hello ! I am currently working on a platform for my organization, and I found a way to embed viva engage "officially" : https://engage.cloud.microsoft/embed/widget?domainRedirect=true The problem I have is that it seems I can't publish a "normal" post (seems I can ask questions, but not open a discussion). More, pictures aren't available into the feed. Any idea why ? Is the iframe limited ? Do I have to open some rights into Azure first ? Or is there an other way to embed properly Engage, to have a seamless experience ? Thanks a lot for your help ! Xavier
Email settings groups
Not sure if its Viva or not, but When I create a group in the admin 365, I can easily tick off the option of "send copies of og group conversations and events ot group members". When created a community within Viva, that group name cant do that. Unable to save the settings "Send copies of group conversations and events to group members' inboxes" and/or "Allow people outside your organization to send email to the group." Either the assigned product license does not include Exchange Online, or you recently created this group and it is not yet ready for processing. Where is the problem?
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?
