Viva Engage Policy Acknowledgement Tracker

Overview

This flow turns a Viva Engage policy/announcement post into an auditable acknowledgement workflow. On a daily schedule it reads the reactions on a specific policy post, compares the reactors against a required audience held in Dataverse, logs each person's acknowledgement status, emails reminders to anyone outstanding, and reports the acknowledgement rate to compliance.

Why it matters: "We posted it" is not proof people read it. Tracking acknowledgement (a reaction on the post) against a defined audience, with automated reminders and a written log, gives compliance an auditable record.

Built as FlowLibs solution FlowLibs - Viva Engage Policy Acknowledgement Tracker. Flow ships Off — going live needs only connection authorization and env var configuration (community id, policy post id). Flow Checker: 0 errors / 0 warnings.

Use Case

HR / compliance posts a policy or important announcement to a Viva Engage community and needs documented acknowledgement from a defined audience. A reaction on the post counts as the acknowledgement signal; the flow chases non-acknowledgers and surfaces the rate.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Viva Engage	shared_yammer	GetMessagesInGroupV3
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

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.

Point at your post

Set flowlibs_VivaEngageCommunityId to the community id and flowlibs_PolicyMessageId to the policy post's message id.

Seed the audience

Add a row per required person to the Policy Audience table (flowlibs_name must match the person's Viva Engage display name; flowlibs_personemail for reminders; flowlibs_policyname = the policy).

Formal attestation

Swap the reaction signal for a Microsoft Forms response or an Approvals step if a click-through attestation is required.

Deadline / escalation

Add a manager escalation branch near the policy deadline.

Name-match precision

Matching is by display name against the post reactors; for large audiences switch to user-id matching using the liked_by user_id field.

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.

@string(coalesce(first(body('Filter_Policy_Post'))?['liked_by']?['names'], json('[]')))

@contains(outputs('Compose_Acknowledger_Names'), item()?['flowlibs_name'])

@div(mul(length(body('Filter_Acknowledged')),100), max(length(body('Load_Required_Audience')?['value']),1))

@body('Get_Community_Messages')?['body/value']

Customize & download