"View all communities" button does not show all communities
If you're in Viva Engage, and you go to "Communities," and you click "View all communities" to see all the communities, it doesn't show you all of the communities - it shows you the recommended communities. If you want to see all of them all at once, you have to click the arrow next to "Recommended" and select "Alphabetical" or "Community size." Is there any way to make the default view "Alphabetical"? Most users will a) expect a view all communities option to show all communities, b) not think to use a drop-down filter and choose 'alphabetical' or 'size' as options to show 'missing' communities. This is a direct consequence of the behaviour of the button not matching the button labelling and as a result this is impacting the visibility and discovery of communities in our network.
Viva Engage Topics
Hi all, The org I work for is looking into creating a Values in Action employee recognition program in Viva Engage. From searching I have not been able to find clear answers on our requirements. The requirements are: One dedicated Viva Engage community Recognition-only posts (no general discussion) 5 organizational values Users must select one value when recognizing a colleague We would prefer to use Praise posts Reporting Can Viva Engage be configured to: Restrict users to only 5 approved Topics? Prevent users from creating additional Topics? Require a Topic/Value to be selected before posting? Require or default to Praise posts? If not natively supported, what governance or configuration approach is recommended?
In trouble with "Articles" again...
Hey, everyone! A while ago I had some issues using Engage because the "Article" option wasn't available for me (I spoke about it here). Now, only a few days later, it is happening again. I’ve already checked with my company's IT team, but it doesn't seem to be related to my license (as far as we could tell), anyone knows if is there any temporary service issue going on?
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?
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.
