Integrating Social Media Engagement with Dynamics 365 Customer Insights – Journeys: What Actually Works in 2026
Most content on this topic points to a native "social posting" module inside Dynamics 365 Marketing/Customer Insights – Journeys, or a plug-and-play Hootsuite connector, as if either were still the recommended path. Neither is, as of mid-2026. Here's the current state, what's been deprecated, what's still actively maintained versus just still findable, and the architecture that holds up.
The native path is being retired
Customer Insights – Journeys used to ship a built-in social-posting calendar: schedule and publish to Facebook, LinkedIn, and X directly from the app, with a marketing calendar view for at-a-glance tracking. That capability sat inside the outbound marketing module.
Status, straight from Microsoft's docs
- Outbound marketing is being phased out. Guidance is explicit: stop building new outbound marketing assets and migrate to real-time journeys instead. No fixed end-of-life date has been published, but the direction is one-way.
- Social posting and LinkedIn lead-generation have already been removed from Customer Insights – Journeys as part of that transition — not "planned," already done.
Stop and check first
If you're scoping a build around the native "Social posts" screen, stop. It's not the durable option, and in many tenants it's already gone.
What's actually still alive on the vendor side — and what isn't
Hootsuite announced a Microsoft Dynamics 365 integration in 2020, and it's still the top search result for "Hootsuite Dynamics 365 integration." Worth being precise about what that was and what's true today.
Hootsuite → Customer Engagement
The 2020 integration targeted Sales, Service, and Omnichannel for lead/case enrichment. No documentation or changelog activity found past roughly 2021. Not confirmed dead — but no evidence of being touched in years.
Amplify by Hootsuite for Teams
Help docs last updated May 2024 — genuinely current. But it's employee advocacy (staff sharing approved content), not customer engagement or Journeys data. Different problem entirely.
Sprinklr → Customer Service
Documented connector creates/updates cases from social and messaging channels and syncs profile data to contacts. That's Customer Service/omnichannel case management — not Customer Insights – Journeys or marketing.
The pattern across every vendor checked: the social integrations that are actually alive today live in Customer Service (case enrichment) or in Teams (employee advocacy). None of them plug social engagement straight into Customer Insights – Journeys as a marketing signal.
Before you evaluate any third-party app
Confirm its current AppSource listing and ask the vendor directly which Dynamics product it targets — "Dynamics 365" alone is not specific enough to trust a five-year-old press release.
The connector layer has thinned out too, and the cost picture has moved
If the fallback plan was "just use Power Automate to pull social data," two things have changed underneath it.
The cost reality for X/Twitter
- Power Automate's Twitter/X connector lost its Microsoft-managed shared app years ago — it now only works via a bring-your-own-app registration against X's developer platform.
- As of February 2026, X moved new developers to pay-per-use pricing by default — priced per post read and per post created — and closed the old flat-rate Basic ($200/month) and Pro ($5,000/month) tiers to new signups entirely.
- Enterprise access (full-archive search, serious streaming volume) starts at roughly $50,000/month, scaled by usage.
- Community reports describe ongoing reliability problems with the connector, independent of the pricing question.
These figures move often enough that you should verify current rates directly with X before budgeting — including this one.
None of this makes Power Automate useless as an orchestration layer — it's still reasonable for moving data between a webhook and Dataverse — but "free, five-minute integration" is no longer an accurate way to describe it for X/Twitter specifically. Facebook, Instagram, and LinkedIn connectors have tightened in similar (if less extreme) ways as each platform has locked down API access.
The architecture that actually works
Given the above, the realistic pattern for tying social engagement into Customer Insights – Journeys has three documented entry points, not one.
The pattern
Treat the social platform as the event source, not the plug-in
Use Hootsuite, Sprinklr, Sprout Social, Brandwatch, or native platform APIs to capture engagement — mentions, comments, DMs, campaign clicks, sentiment. Hootsuite, for example, exposes this through its own Analytics/external API for syncing into BI and downstream tools. Pull from there via the vendor's own API, not through a Dynamics-branded connector.
Feed it into Journeys through one of three Microsoft-documented mechanisms
Which one depends on how real-time you need it. See the three cards below.
Custom triggers
A user-defined trigger that's technically a Dataverse Custom API under the hood, complete with an ingestion key. Fire it from a website snippet (client-side) or server-side — from an Azure Function that received a webhook from your social tool, for instance. The right mechanism for "customer engaged with our post, react immediately."
Security note: the ingestion key uniquely identifies your Journeys instance — anyone holding it can fire spurious triggers, so protect it like any API secret.
Dataverse record-change trigger
Land social engagement events into a Dataverse table (via Power Automate or Azure Logic Apps calling the social platform's webhook or API), then let Journeys react to record creation or updates on that table. Lower-effort than custom triggers if you're already comfortable in Power Automate.
Customer Insights-Data real-time API
Still labeled preview as of this writing. Available via the native "Dynamics 365 Customer Insights" Power Platform connector (no-code, premium license required) or by calling the API directly.
Limitation: activities added this way do not update segments, measures, or enrichments, and don't flow to Power BI exports. Great for the activity timeline; not sufficient alone for segmentation.
03 · Pick the mechanism based on what the journey needs to do
What to verify before you build
Pre-build checklist
- ✓Confirm in your own tenant whether outbound marketing/social posting is still present or already gone — this varies by provisioning date and release wave.
- ✓Don't scope a project around any third-party "Dynamics 365" social connector on the strength of a press release alone; confirm current AppSource status and ask which specific Dynamics product it targets.
- ✓Price out per-platform API access before committing to a design — X's current cost structure is materially different from what most existing blog posts describe, and it has changed more than once in two years.
- ✓Decide upfront whether you need custom triggers (real-time, more dev effort, ingestion-key security to manage) or Dataverse record-change triggers (lower effort, slightly less immediate).
- ✓If segmentation is part of the goal, don't rely on the Customer Insights – Data real-time API alone — confirm your scheduled/batch ingestion also covers the same data.
The bottom line
The "just connect Hootsuite" story repeated across a lot of existing content is a 2020–2021 answer to a 2026 question, and it's pointing at a product (Dynamics CRM/Customer Engagement) that isn't even the one under discussion here. The unified-profile-plus-real-time-journeys pattern, built on Microsoft's own documented trigger and ingestion mechanisms, is both the more accurate current answer and the more resilient one — it doesn't depend on a vendor keeping a Dynamics-branded plug-in alive somewhere in the background.
Related reading
IntegrationDual-Write Between Dynamics 365 (Dataverse) and Finance and Operations: Setup, Master Data, and Troubleshooting
A working runbook for linking Dataverse and Finance and Operations: prerequisites, the linking wizard, master data maps, Entra ID app users, the health check, and the errors you'll actually hit.
IntegrationDynamics 365 On-Premises Email Sync Is on Borrowed Time — Here's the Graph API Path Forward
EWS is being retired for Exchange Online, and Dynamics 365 CE on-premises has no first-party replacement. Here are the dates that matter and what a custom Graph API build actually involves.