If you are buying or already running Microsoft's CRM, someone has probably asked whether you should add Dynamics 365 Customer Insights. The answer is unusually confusing, because Customer Insights is two applications sold under a single name and a single subscription, and it is priced in a way that works nothing like the rest of Dynamics 365.
This piece covers what each half does, how the licensing meters, the signals that say you are ready for it, the signals that say you are not, and a comparison against HubSpot for a company that already runs Dynamics 365 Sales.
What Customer Insights is
One subscription buys access to two applications. They share a name, they share a license, and they solve different problems.
Customer Insights - Journeys
This is the marketing application. It was called Dynamics 365 Marketing until September 2023. It handles campaign orchestration: building segments, designing and sending email and text messages, running multi-step nurture sequences that branch based on what a person does, capturing form submissions, scoring leads, and managing events.
The event management capability is more complete than most people expect: planning, sessions and speakers, venue and room tracking, attendee passes, sponsors, registration, attendance history, and Microsoft Teams webinars, all against the same contact records your sellers use.
Lead scoring models assign points for demographic attributes and for engagement (emails opened, forms submitted, events attended), then convert those points into grades your sellers can sort by.
One change worth knowing about: Journeys used to contain two modules, real-time journeys and an older one called outbound marketing. Outbound marketing was removed from all environments in May 2026. Older guidance or proposals referencing outbound marketing segments, forms, or journeys are out of date.
The problem Journeys solves: your marketing team is running campaigns in one tool while your sellers work leads in another, and nobody can tell which campaign produced which opportunity.
Customer Insights - Data
This is a customer data platform. Its job is to take customer records that live in several different systems (your CRM, your ERP, an e-commerce platform, a support desk, a spreadsheet somebody maintains) and resolve them into one profile per actual human being.
The unification process runs in four steps: you map the source columns to descriptive types, define deduplication rules within each source, define matching rules across sources, then choose which columns win when two sources disagree. The output is a unified profile with a stable identifier that persists across runs. From there you can build segments, calculate measures, and run predictive scoring against a complete picture rather than a partial one.
The problem Data solves: the same customer exists as three records under two spellings across your CRM and your ERP, so nobody can answer what that customer is worth or what they have already bought.
Why the shared name causes trouble
Buyers hear "Customer Insights" and picture whichever half was described to them, so conversations drift when one side means marketing automation and the other means data unification. When scoping this, name the application every time and ask whether a given requirement is served by Journeys or by Data. The two are metered separately, and one may matter to you while the other does not.
How it is licensed
This is where most of the surprise lives. Dynamics 365 Sales is a per-user subscription. Customer Insights is not.
It is licensed per tenant, not per seat. You buy one subscription for the organization and any number of users can access the applications at no additional per-user cost. Microsoft's documentation is explicit that Customer Insights licenses do not appear under "Licenses" in the Microsoft admin center because they are not assignable seat licenses. They show up under "Your Products" instead. If you have more than one tenant, you buy for each tenant separately.
Two independent meters. The base subscription carries two entitlements that you can scale independently of each other.
| Meter | What it counts | Base entitlement |
|---|---|---|
| Interacted people | Records (contacts, leads, unified profiles, custom records) that have received an outbound message from Journeys | 10,000 at the tenant level |
| Unified people | Unique profiles produced by Customer Insights - Data merging records across sources | 100,000 at the tenant level |
The definitions matter more than the numbers. An interacted person is any record that has received an outbound interaction. It is counted once no matter how many messages it receives. Records you store but never market to do not count at all. Inbound activity such as a form submission does not trigger the count. And a record stops counting once it has gone 12 months without receiving an interaction, so this is a rolling annual measure, not a snapshot.
An interaction is a specific set of outbound sends: email, text message, push notification, voice channel, and custom channel messages orchestrated through Journeys.
The monthly sending limit is derived from the people count. You get 10 interactions per month for every interacted person you have licensed. Own 10,000 interacted people and you can send 100,000 messages in a calendar month. The messages are not tied to specific individuals, so you could send all of them to one person if you wanted. This quota resets on the first of each month and does not roll over. Microsoft's own guidance is to size for your peak month, not your average one, because the only way to raise the monthly ceiling is to buy more interacted people.
Everything sums at the tenant level, including sandboxes. Usage in development, sandbox, and trial environments counts against the same entitlement as production, because Microsoft's underlying cost is the same regardless of environment type. If you plan a build with several environments running in parallel, factor that in.
What happens when you exceed it. You get in-app notifications as you approach the paid quota and again when you pass it. Once the monthly interaction quota is used up, messages stop going out for the rest of the month. Separately, there is a service limits and fair use policy that caps things like total monthly sends, segment counts, and sending throughput regardless of what you have purchased. Those are ceilings on the service, not on your subscription.
Add-on capacity packs. Additional interacted people and additional unified people are sold in packs, tiered by volume band. The two meters are independent, so a company that needs heavy data unification and light email volume buys accordingly. Add-on packs carry incremental Dataverse storage; the base subscription's Dataverse allowance is granted once no matter how many base subscriptions you hold.
The attach subscription. If you already own Dynamics 365 Sales, Customer Service, Field Service, Supply Chain Management, Finance, or Commerce with 10 or more users, you qualify for a reduced-price "attach" version of the base subscription, which Microsoft documents as carrying identical entitlements to the full-price offer. This is the relevant path for almost every company reading this. Confirm your qualifying user count before anyone quotes you the standalone number.
One thing not included. If you plan to send text messages, the Customer Insights subscription does not include phone numbers or message delivery. You sign up separately with a supported messaging service and pay them directly.
Where to find the current price
Current pricing for the base subscription, the attach subscription, and every add-on capacity tier is published on Microsoft's Dynamics 365 Customer Insights pricing page. Complete entitlement terms are in the Dynamics 365 Licensing Guide, which Microsoft updates regularly. Prices change, so the published page is the one to check.
When it makes sense to add to Dynamics 365 Sales
Concrete signals, in rough order of how strongly they point toward yes.
- You have a real marketing function. At minimum one person whose job includes building segments, writing campaigns, and reviewing results. A partial responsibility bolted onto an office manager's week does not clear the bar.
- Customer data is split across more than one system and the split is costing you. Your CRM and your ERP disagree about who the customer is, or e-commerce records never make it back to the sales team. This is the specific case Customer Insights - Data addresses, and ordinary marketing tools do not.
- You run multi-step nurture sequences rather than one-off sends. Journeys earns its keep on branching logic: send this, wait, check whether they opened it, branch, and hand the qualified ones to a seller.
- You run events and want registration tied to the same contact records your sellers use. Trade shows, webinars, customer days.
- You need marketing-sourced pipeline attribution in the same system as the pipeline. Because Journeys writes interaction and scoring data into the same Dataverse database that holds your opportunities, "which campaigns produced closed revenue" is a report rather than a reconciliation project.
- Your outbound volume is meaningful and predictable. Monthly sends divided by 10 gives a rough interacted-people requirement, which is the fastest check on whether this is affordable at your scale.
On threshold: below roughly a few thousand people you market to and a handful of campaigns a year, the base subscription is priced above what the capability returns, and simpler tools do the job. The base entitlement of 10,000 interacted people is generous for a small company, which means small companies typically pay for headroom they will not use. The break-even point tracks whether someone is running marketing operations as a job more closely than it tracks company size.
When it is not a fit
Stated flatly, because these situations are common and the outcome is predictable.
- No one owns marketing operations. The application does not run itself. Journeys assumes someone builds segments, writes messages, configures consent, and reads the results. Bought without that person, it goes unused and renews anyway.
- The contact database is small. If you market to a few hundred people, the entitlement you are buying is mostly headroom.
- Campaigns are occasional one-off sends. A quarterly newsletter to a static list does not need journey orchestration, lead scoring, or a customer data platform.
- Nobody will maintain the data unification. Matching rules are not set-and-forget. Source systems change, new fields appear, and match quality drifts. Without an owner, unified profiles degrade and the segments built on them go quietly wrong.
- Dynamics 365 Sales is not adopted yet. If sellers are not reliably working leads and opportunities in the CRM, adding marketing automation on top produces scored leads that nobody follows up. Get adoption first. The order matters, and Customer Insights is easier to add later than it is to rescue.
If more than one of those describes your situation today, the answer is to wait.
Customer Insights compared to HubSpot alongside Dynamics 365 Sales
Both are credible answers. They are structurally different in ways that show up months after the decision, so it is worth being precise.
| Customer Insights | HubSpot Marketing Hub | |
|---|---|---|
| Where marketing data lives | Same Dataverse database as Dynamics 365 Sales | HubSpot, synced to Dynamics |
| Systems of record | One | Two, kept aligned by sync |
| Data unification across source systems | Included (Customer Insights - Data) | Not a capability of the marketing tool |
| Time to first campaign | Longer; configuration-heavy | Shorter; designed for marketer self-service |
| Metering | Interacted people and unified people, per tenant, users included | Marketing contacts plus paid seats |
| Administrative surface | Dataverse, security roles, consent model, environments | HubSpot admin plus the sync configuration |
Where the data lives, and whether you end up with two systems of record. This is the decision. Customer Insights writes into the same database as your sales pipeline, so a segment can reference an opportunity field and a report can trace a campaign to closed revenue without leaving the system. With HubSpot you run two databases and a sync between them, a normal and well-supported architecture that thousands of companies operate successfully. It also means someone owns the sync forever.
How the integration works in practice. HubSpot's Dynamics 365 integration is a documented data sync covering companies to accounts, contacts to contacts or leads, deals to opportunities, products, meetings, notes, tasks, invoices, orders, emails, and calls, plus custom objects. Sync can be one-way or two-way per object, and two-way requires read and write permissions on each record type in Dynamics. The boundaries are published rather than hidden: custom field mappings require a paid Data Hub subscription, tasks associated with Dynamics leads sync one direction only, and line item price changes on a HubSpot deal do not carry into a created Dynamics sales order. Record data flows well, and the edge cases call for mapping decisions made deliberately at setup rather than discovered later.
Ease of use and time to first campaign. HubSpot is the faster path for a small marketing team. It is built for marketers to configure themselves, and a competent marketer can ship a campaign without a consultant. Customer Insights carries more setup before the first send: consent model, compliance profile, forms, segments, and security roles. If your constraint is a one-person marketing team that needs to be productive next month, HubSpot is usually the better answer.
Reporting and attribution. Customer Insights has the structural advantage: marketing interactions and sales opportunities are rows in one database, so attribution is a query. HubSpot's attribution reporting is strong on its own side and reaches into Dynamics through the sync, though the fidelity of any cross-system report depends on the fidelity of the sync. Where board-level "marketing-sourced pipeline" reporting is a stated requirement, weigh that difference carefully.
The data unification difference. If your problem is that customer records are scattered across a CRM, an ERP, and an e-commerce system and nobody can resolve them, Customer Insights - Data addresses that directly and a marketing platform does not. HubSpot deduplicates within HubSpot. It is not trying to be a customer data platform, and comparing it on that basis is not a fair comparison. When we hear "we cannot tell who our customers are across systems," that requirement points to Customer Insights - Data regardless of which tool sends the emails.
Administrative surface. Customer Insights concentrates administration in the Microsoft stack you already run: Dataverse, environments, security roles, and the Power Platform admin center. That is fewer places to look if you are already a Microsoft shop, and more depth to learn if you are not. HubSpot has a lighter, self-contained admin experience plus the ongoing sync to own.
How each is metered. Customer Insights meters on people you engage and profiles you unify, at the tenant level, with no per-user charge for access. HubSpot Marketing Hub tiers on marketing contacts and charges for seats separately, and its email send allowance is likewise a multiple of the contact tier per calendar month. Both companies, notably, meter sending as a multiple of the audience you have licensed rather than selling messages outright, and HubSpot's Professional and Enterprise tiers carry a required one-time onboarding charge. Current figures are on HubSpot's pricing page.
Migration and lock-in. With Customer Insights, contact and interaction data stays in Dataverse, which you keep as long as you keep Dynamics 365 Sales, so what you would rebuild is the journeys and assets. With HubSpot, synced records exist on both sides, but marketing assets, engagement history, and campaign structure live in HubSpot and leaving means rebuilding them elsewhere. Both represent real work to unwind, which is worth asking about before signing rather than after.
Where we land. We recommend HubSpot when the marketing team is small, needs to move quickly, and values self-service over integration depth. We recommend Customer Insights when customer data is genuinely fragmented across systems, when attribution across marketing and sales has to be trustworthy, when events matter, or when the organization is already standardized on Microsoft and does not want another system to administer. Both recommendations are common in our work.
Gotchas
The naming confusion is the first one. Two applications, one name, one subscription. Confirm in writing which one a given requirement depends on.
The metering will surprise your finance team. It scales with how many people you market to and how many profiles you unify rather than with seats, it counts sandbox and trial usage against the same pool, the interacted-people count runs on a rolling 12-month window, and the monthly send ceiling is derived rather than bought directly. Size for your peak month.
It requires clean underlying data. Unified profiles are only as good as the matching rules, and matching rules are only as good as the source data. Committing to Customer Insights - Data means committing to a data quality effort with an owner. Bought without that, you get unified profiles that are confidently wrong.
The implementation is a project. Consent configuration, compliance profiles, form and website tracking, segment design, journey design, scoring models, security roles, and a migration of existing marketing content. Plan a defined scope and timeline.
Outbound marketing carries legal obligations. Consent in Journeys is captured per contact point (each email address or phone number), organized under compliance profiles, purposes, and topics, with three enforcement models: restrictive (send only on explicit opt-in), non-restrictive (send unless opted out), and disabled. Regulations including the European Union's General Data Protection Regulation and the United States CAN-SPAM Act determine which model applies where, which is a decision for your counsel rather than your consultant. Two details catch people out: Journeys does not evaluate the older "do not email" and "do not bulk email" fields on a contact unless an administrator turns on a feature switch, and unsubscribe links in messages expire six months after they are created. Microsoft also states plainly that responsibility for complying with privacy law when using lead scoring and the rest of the application sits with your organization.
If you are weighing this decision
Bring us the specific question you are trying to answer. How many people do you market to in a year, how many messages do you send in your busiest month, which systems hold customer records today, and who on your team would run this. Those four answers usually settle whether Customer Insights, HubSpot, or neither is the right next move, and they settle it before anyone signs anything. We are happy to work through them with you.