“Intra ID / Microsoft 365 group visibility in Viva Engage (Yammer) for Education A3 plan”

Hi Abhiram Bajpai

I have conducted some research about your concern, and the information below might help from my perspective

Regarding your first question: Is it possible for existing Intra ID / M365 groups to appear in Viva Engage?

The answer from my research is NO, currently there isn’t a supported “convert or surface an existing Microsoft 365 group as a Viva Engage community” path. Microsoft’s own notes around community provisioning explicitly state that creating a Viva Engage community for an existing Microsoft 365 group is out of scope, and the documented flow is primarily community-first (create in Engage --> group gets created/connected).

For more information: https://m365admin.handsontek.net/viva-engage-community-creation-api-is-now-available-on-ms-graph-beta/

Note: This information is provided as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

Next one, your second question: What steps are required to make the group visible?

Since direct conversion isn’t supported, the supported steps are to create the community in Viva Engage. This is the standard method for getting a Viva Engage community (and, when eligible, a Microsoft 365–connected community)

And for the last question: What is the official workaround for running discussions in Viva Engage using Intra ID groups in a school tenant?

You can create the Viva Engage community and then manage membership via Microsoft 365 / Entra ID (so the same people are in the community). Microsoft documents managing community membership at scale (including bulk processes) and also supports dynamic groups so Entra attribute-based membership can flow into an Engage-connected group (requires Entra ID P1/P2 per requirements).

You can read here for more information:

Create a community in Viva Engage

Dynamic groups in Viva Engage

Hope my answer will help you.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

1. Existing Microsoft 365 groups (created in Microsoft Entra ID / Microsoft 365 admin center) do not automatically become Viva Engage communities. The documented relationship is the other way around: when a Viva Engage community is connected to Microsoft 365 Groups, the associated Microsoft 365 group and its resources (SharePoint site, OneNote, Planner, etc.) are available from Viva Engage.
2. The context only describes how to recognize and use Viva Engage communities that are already connected to Microsoft 365 Groups, not how to surface an arbitrary pre-existing Microsoft 365 group in Viva Engage. It states that:
   • A Viva Engage community is considered “connected” if the Microsoft 365 Resources section appears in the community.
   • Connected communities then gain access to Microsoft 365 services such as a SharePoint site, document library, OneNote notebook, and Planner plan, and can use features like dynamic membership, naming policies, and expiration policies.
   There is no documented procedure in the provided context to “attach” an existing Microsoft 365 group (created outside Viva Engage) so that it appears as a Viva Engage community. Therefore, based on the available documentation, there is no supported, documented way here to make an arbitrary Entra ID / Microsoft 365 group like “Abhiram” or “USERTEST” show up in Viva Engage.
3. For running discussions in a school tenant using Microsoft 365 groups and Viva Engage, the documented pattern is:
   • Create or use Viva Engage communities that are connected to Microsoft 365 Groups.
   • Those connected communities then:
     • Expose Microsoft 365 resources (SharePoint, OneNote, Planner, etc.) directly from Viva Engage.
     • Can use dynamic membership based on Microsoft Entra ID.
     • Follow Microsoft 365 Groups naming policies and expiration policies.
   In practice, this means creating the discussion space in Viva Engage as a Microsoft 365–connected community, and then managing membership and policies via Microsoft 365/Entra ID. The Microsoft 365 group that backs the community is created/managed as part of that connection rather than starting from an arbitrary pre-existing group and expecting it to appear in Viva Engage.

References:

• Viva Engage and Microsoft 365 Groups
• Manage Viva Engage users across their lifecycle from Microsoft 365
• Microsoft 365 inter-tenant collaboration
• Viva Engage FAQ
• Microsoft Entra ID security groups