Use the modern Microsoft Graph to create a Community in Viva Engage instead of using the classic Yammer developer functionality

[haroldvandekamp]

Suggestion

To enhance the Provision Assist to stay up to date, I would like to request an enhancement of the creation a Viva Engage Community by switching to the Microsoft Graph API. Can this be implemented?

Classic route of creating a community in Viva Engage currently implemented in the Provision Assistant solution

The provision-assist-m365 documentation describes in Step 12 (Optional): Enable provisioning of Viva Engage Communities the old way of creating a community in Viva Engage, e.g. by referencing the previous product name Yammer and using the classic developer functionality of requesting the creation of a Yammer App Token during deployment of the solution. A great enhancement will be the use of the modern way of creating a Viva Engage Community by interacting with the Microsoft Graph API.

Suggested modern route of creating a community in Viva Engage to be implemented in the Provision Assistant solution

As described in the Microsoft Learn Documentation for Microsoft Graph at Use the Microsoft Graph API to work with Viva Engage (preview) under the /beta version of the the Microsoft Graph functionality is available to create a Viva Engage Community. The implementation steps including the App Registration in Microsoft Azure is described and depicted in Tech Community Blog Introducing the Community Creation API for Viva Engage on Microsoft Graph Beta. The following picture shows a community in Viva Engage created via the Microsoft Graph API.

Important: The Viva Engage API in Microsoft Graph is only supported for Viva Engage networks in native mode. You can't use this API to manage legacy or external Viva Engage networks.

[alexc-MSFT]

@haroldvandekamp nice enhancement! Yes we should definitely do this.

I will add it to the roadmap 😀