Microsoft Viva Engage connector

Use your Microsoft Viva Engage data for reporting, automation and AI.

Data Panda brings the community, conversation and storyline metadata from your Viva Engage tenant together with the data from the rest of your business. From one place we turn it into dashboards, automations, AI workflows and small apps that comms, HR and the leadership office use, instead of leaving the engagement story on a quarterly slide.

About Microsoft Viva Engage

The social fabric of Microsoft 365, with a leadership corner on top.

Viva Engage is the enterprise social network that lives inside Microsoft 365 and Microsoft Teams, built on what used to be Yammer. Yammer started in 2008 as a side product at the genealogy site Geni and grew into a standalone enterprise social network under founder David Sacks. Microsoft acquired Yammer in 2012 and folded it into Office 365. In August 2022 the Communities app inside Teams was renamed to Viva Engage as part of the Microsoft Viva employee experience platform, and on 13 February 2023 Microsoft announced the full rebrand from Yammer to Viva Engage, with the Yammer apps and yammer.com URLs migrating across the rest of the year.

Today the product centres on a few moving parts: communities (each one backed by a Microsoft 365 group, a SharePoint site, a OneNote and a Planner plan), open and threaded conversations inside those communities, the personal storyline feed that surfaces in Viva Connections, Teams and Outlook, the Leadership Corner where executives post and run Ask Me Anything sessions, and Town Halls for company-wide broadcasts with Q&A. Microsoft Graph exposes the community and role surface through the engagement API on tenants in native mode, so a connector can read the community inventory, membership and admin roles in a supported way. Pulled into a warehouse next to the rest of Microsoft 365 and the line-of-business stack, that surface answers the questions a Yammer-era admin export never really did: which leadership posts moved a real audience, which communities live or die after the launch wave, and where the stated culture programme lands inside the company.

What your Microsoft Viva Engage data is for

What you get once Microsoft Viva Engage is connected.

Community and leadership reporting

Communities, members, posts and reach on one page across the tenant, instead of a screenshot from the Engage admin centre stitched onto a slide.

Active versus dormant communities per business unit and country
Leadership Corner posts ranked by views, replies and unique audience reached
Storyline reach per executive and per topic, against the editorial calendar

Comms and lifecycle automation

Let community and post events trigger the housekeeping the comms and IT teams would otherwise do by hand.

Community-archive proposals when a community has no posts or replies for 90 days
Owner reassignment when a community admin leaves the tenant
Translation, captioning and republish workflows for high-reach Leadership Corner posts

AI workflows

Put the conversation and reach surface behind AI that reads tone, topic and audience together.

Topic clustering across communities to find what the workforce talks about that no programme owns
Sentiment summary on Leadership Corner threads after major announcements
Recommender that points new joiners at the communities their team and role family already use

Custom apps on your data

Small internal tools on Engage metadata for comms, HR and works-council audiences.

Comms editorial cockpit with reach per channel, audience and topic
Leadership-office view of post performance per executive, per quarter
Engagement health board that pairs Engage activity with HiBob attrition signals

Use cases

Use cases we deliver with Microsoft Viva Engage data.

A list of concrete reports, automations and AI features we have built on Microsoft Viva Engage data. Pick the one that matches your situation.

Community inventoryTotal communities, active versus dormant, per business unit and country.

Membership mapMembers per community, with overlap between communities and the org chart.

Leadership reachViews, replies and unique audience per Leadership Corner post and per executive.

Storyline performanceStoryline post reach per author, surfaced through Engage, Teams, Connections and Outlook.

Town Hall attendanceRegistered, attended and replay views per Town Hall, with Q&A counts.

AMA engagementAsk Me Anything sessions ranked by audience, questions asked and questions answered.

Announcement uptakeReach and reply rate on tenant-wide announcements per audience segment.

Owner coverageCommunities with an active admin versus communities whose admin has left the tenant.

Topic mapConversation topics across communities, clustered to surface programmes that have no owner.

Joiner community guideTop communities per role family, based on peer membership.

Native-mode readinessTenant share of communities running in native mode versus legacy mode, by business unit.

Real business questions

Answers you will finally get.

Which communities still live and which ones are paying for storage?

Active versus dormant community counts per business unit, with the cut-off you choose (30, 60 or 90 days of no posts or replies). Internal comms see which communities still have a heartbeat and which ones sit on a connected SharePoint site, OneNote and Planner plan that nobody opens, instead of guessing from a one-off Engage admin export.

Did the CEO post land inside the business?

Views, replies and unique audience per Leadership Corner post and per executive, broken down by audience segment and country. The leadership office sees whether a strategy update reached the floor it was written for or stalled in the head-office bubble, and the comms team can stop reporting reach as a single number that hides where the post moved people.

Are the communities the comms team launched the same ones the workforce uses?

Topic clustering across community conversations, ranked by member overlap and reply volume. You see where the official communities map onto the topics employees talk about, where two officially-separate communities have effectively merged, and where a topic is bubbling up that no programme owns. Useful before the next round of community sponsorship is decided.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Microsoft 365 spend lined up against active Engage usage. The CFO sees which business units use the social fabric they pay for inside the Microsoft 365 bundle, and the SaaS-spend deck stops treating Engage as a free side-effect of the licence.

For sales leaders

Internal sales communities and supplier-engagement spaces become a number rather than a feeling. Sales operations sees which account teams use the platform to share field intel and which deal rooms have stopped posting weeks before pipeline numbers reflect it.

For operations

Internal comms, HR and the leadership office finally see reach, audience and reply data on the same page as the workforce data. Programme launches, change campaigns and town halls get measured on actual impact instead of on a screenshot from the Engage admin centre.

Ideas

What you can automate with Microsoft Viva Engage.

Pair with HubSpot

Surface HubSpot customer wins inside the right Engage community

Closed-won deals, expansion bookings and key customer milestones in HubSpot post into the matching account, region or product community in Viva Engage, with deal value range, owner and key fields attached. Sales and customer-success leaders celebrate wins where the team already gathers, and the leadership office sees a real activity baseline for revenue communities instead of an empty space.

Pair with HiBob

Welcome HiBob joiners into the communities their role family already uses

New joiner records in HiBob trigger a Viva Engage community-suggestion message in the joiner's storyline or onboarding channel, based on the communities peers in the same role family and country are most active in. Onboarding stops shipping a static intranet link and the new hire lands in the rooms where their team talks, with the leaver flow archiving membership cleanly when an exit record posts.

Pair with monday.com

Post monday.com programme milestones into the right community

Status changes, milestone completions and risk flags on monday.com programme boards post into the matching change or transformation community in Viva Engage, with item owner, due date and status attached. The programme office gets a visible heartbeat in the room sponsors already follow, and stakeholders read progress without opening the board.

Pair with Salesforce

Push Salesforce key-deal moments to the account community

Stage changes on strategic Salesforce opportunities, lost-deal post-mortems and renewals at risk post into the account or region community in Viva Engage, with deal context attached. Account teams replay the moments that matter inside the community where the territory leadership already reads, and the leadership office sees community activity tracking real revenue motion.

Pair with Exact Online

Share Exact Online financial close milestones in the finance community

Period-close completions, audit-ready flags and key reporting milestones from Exact Online post into the finance or group-controlling community in Viva Engage, with entity, period and owner attached. Finance leadership gives recognition where the team already gathers, and group controlling stops chasing close status across email and calls.

Pair with Slack

Bridge tenant-wide Engage announcements into Slack-first teams

Leadership Corner announcements and Town Hall recaps from Viva Engage cross-post into the matching Slack channel for teams that live primarily in Slack (typically engineering or product orgs after an acquisition). The acquired team reads the same leadership message as the rest of the company without being forced into a second daily client, and comms reports unified reach across both surfaces instead of guessing the Slack-side audience.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Microsoft Viva Engage data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Microsoft Viva Engage to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Microsoft Viva Engage connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Does the connector pull message bodies or just community metadata?

The default pull through the Microsoft Graph engagement API stays at community and role metadata: community id, name, description, privacy setting, member and admin counts, the connected Microsoft 365 group, and the Viva Engage role assignments inside the tenant. Message bodies and storyline post content are not part of the standard scope, which keeps the warehouse focused on tenant topology, leadership reach and community health rather than on free-text conversation analytics. Reading post content is a separate conversation about works-council scope, retention and privacy, and is not how we recommend most customers start.

Does the connector work on legacy Yammer networks or only on native mode?

Microsoft's engagement API in Microsoft Graph is supported only on Viva Engage networks running in native mode, where each community is backed by a Microsoft 365 group, a SharePoint site, OneNote and Planner plan. Tenants still on legacy or external Yammer networks need to migrate to native mode before the supported Graph surface lights up, and the connector reflects that scope. We can still report on what the legacy admin surface exposes during a migration, but the long-term picture lives on native mode.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Microsoft Viva Engage setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors