Viva Engage: Designated experts in Communities

We are introducing the Community Expert feature in Microsoft Viva Engage to enhance the trust and utility of knowledge in your communities. Experts will be able to endorse accurate and credible answers and be recognized as community experts with a special label next to their name.

A community expert is a member of a community who is assigned or approved by a community admin to serve as a subject matter expert within a specific community. A community expert has special capabilities, such as marking the best answer, marking a verified answer (coming separately and soon after with the launch of Community Experts), and pinning posts. However, a community expert does not have the ability to manage members, assign roles, and so on like a community admin. Additionally, they are given a label strictly within that community that says “Community Expert.” 

Note: Community expertise is determined by community admins within your organizations, not Microsoft. Microsoft does not have the ability to define a community expert in your organization. 

This message is associated with Microsoft 365 Roadmap ID 408164.

General Availability (Worldwide): We will begin rolling out early January 2025 and expect to complete by late February 2025. 

How this will affect your organization:

This will be available for all customers as part of the seeded Viva Engage experience. 

What you need to do to prepare:

Tips for identifying community experts: 

• Engaged existing users: Identify individuals who consistently participate in community discussions, whether by providing answers, verifying information, or sharing relevant resources. 
• Peer recommendations: Consider recommendations from peers who regularly consult these individuals for guidance on specific topics. It could be as simple as putting up a poll in a community and asking people to respond.  

We will provide a blog post and documentation on how to best use this feature in the future.

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.