Viva Engage New Community Member Onboarding

Overview

This flow onboards new Viva Engage community members. On a schedule it detects newly joined members, posts a public welcome in the Viva community, sends a starter pack (pinned resources, norms, who to follow) to the community Teams channel, records each member in a Dataverse roster table, and notifies the community manager in Teams.

Why it matters: New members often lurk and disengage. A warm, resource-rich welcome helps them get value and participate faster.

Build status: Built and verified (Flow Checker 0 errors / 0 warnings). Ships Off (demo). Going live requires only connection authorization and environment-variable configuration.

Design note — membership polling: The Viva Engage connector (shared_yammer) has no join trigger and no membership-read operation. A Viva Engage community is backed by a Microsoft 365 group, so the flow polls membership with the Microsoft Entra ID connector's GetGroupMembers operation against the community's AAD group, and diffs the result against the Dataverse roster to find new members. Two identifiers are used: flowlibs_CommunityAadGroupId (the AAD object id, for GetGroupMembers) and flowlibs_VivaCommunityGroupId (the Yammer numeric group id, for the Viva welcome post).

Use Case

A community manager wants every new joiner welcomed and oriented automatically, with a durable roster record and a manager FYI — no manual watching of the member list.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Entra ID	shared_azuread	GetGroupMembers
Viva Engage	shared_yammer	PostMessage
Microsoft Teams	shared_teams	PostMessageToConversation
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Buddy match

Pair each new member with a community buddy (add a lookup into a buddy roster + an @mention in the welcome post).

First-post prompt

Add a follow-up Viva post inviting the member to introduce themselves.

Re-engage

Add a scheduled child flow that follows up if a member is inactive after two weeks (track flowlibs_joinedon).

Manager via email

Swap Notify_Community_Manager for an Outlook SendEmailV2 if the manager prefers email.

Filter member types

Add a Filter array on @odata.type to onboard only real users (skip nested groups / service principals).

Cadence

Change the Recurrence frequency/interval to poll more or less often.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@equals(length(body('Check_Existing_Roster')?['value']), 0)

@coalesce(items('Apply_to_each_Member')?['mail'], items('Apply_to_each_Member')?['userPrincipalName'], 'unknown')

@int(parameters('EnvVar_VivaCommunityGroupId'))

@guid()

Customize & download