Viva Engage Campaign Cross-Post Scheduler

Overview

This solution coordinates internal campaigns on Viva Engage from a single approved source. Approved campaign posts live in a Dataverse content-calendar table; on a schedule the Campaign Publisher flow publishes each due post to its target Viva Engage community, cross-posts to Teams, and marks it Published. A second Engagement Tracker flow runs daily, reads reaction counts from each published post's community, and logs an engagement snapshot for reporting.

Why it matters: Internal campaigns lose impact when posted inconsistently across communities. Driving them from one approved calendar with engagement tracked centrally ensures coordinated, measurable reach.

> Build note — Dataverse content calendar (not SharePoint). This build uses a Dataverse table (flowlibs_campaignpost) as the content calendar, the more portable connector-first choice. To use a SharePoint list instead, swap the Dataverse ListRecords/UpdateRecord actions for SharePoint GetItems/UpdateItem and point flowlibs_CampaignTable at the list.

> Viva pinning limitation. The Viva Engage (Yammer) connector has no "pin message" operation. The flowlibs_pinimportant flag is honored by flagging the cross-posted Teams message as a Pinned campaign; pinning inside Viva Engage itself must be done manually or via a Graph call if/when available.

Use Case

A comms team running internal campaigns maintains a content calendar of approved posts. They want each post published to the right communities on schedule, echoed into Teams, and engagement tracked automatically for a weekly report — without anyone hand-posting or hand-counting reactions.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Viva Engage	shared_yammer	PostMessage GetMessagesInGroupV3
Microsoft Teams	shared_teams	PostMessageToConversation
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord

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.

Approval gate

Add an Approvals StartAndWaitForAnApproval step before a post flips to Approved, or drive Status from a model-driven app.

Multiple communities per post

Replace the single flowlibs_communityid with a child table or a JSON array column and loop the PostMessage over each.

Cadence

Tighten or relax the Publisher recurrence (currently 15 min) and the Tracker recurrence (currently daily).

Engagement report

Add a weekly Recurrence flow that aggregates flowlibs_vivaengagement and emails a summary via Outlook.

True Viva pin

When a pin API is available, add it after Post_To_Viva_Community gated on flowlibs_pinimportant.

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.

lessOrEquals( coalesce(item.flowlibs_scheduledtime, utcNow()), utcNow() )

int(coalesce(item.flowlibs_communityid, first(json(EnvVar_TargetCommunities)), varDefaultCommunity))

equals( toLower(coalesce(item.flowlibs_crosspostteams,'no')), 'yes' )

equals( string(message.id), coalesce(item.flowlibs_messageid,'') )

Customize & download