Installing and provisioning Customer Insights

What it does

Installs the Customer Insights - Journeys application onto a Dataverse environment and, more importantly, connects that environment to the Microsoft-hosted marketing services that actually send messages, process segments and run journeys. The install is driven from the Power Platform admin centre, not from inside Dynamics, and the app solutions on their own are inert without the service connection.

Key facts

Licensing is one of: Dynamics 365 Customer Insights (entitles both Journeys and Data), or Dynamics 365 Marketing (Journeys only). The standalone Customer Insights - Data SKU entitles Data only and won't get you Journeys.
The person running the install needs Service support admin or higher (Dynamics 365 administrator or Power Platform administrator), permission to register applications in Microsoft Entra ID, and the System Administrator role on the target Dataverse environment.
The environment needs Dataverse enabled and the "Enable Dynamics 365 apps" toggle on at creation. Production, Sandbox and subscription-based Trial are all supported types.
Block unmanaged customizations must be Off on the target environment (Power Platform admin centre > Environments > env > Settings > Product > Features) or the install fails. This one catches almost everyone in a governed tenant.
You install from Power Platform admin centre > Manage > Dynamics 365 apps. Set the geo selector in the top right to match the environment's region first, otherwise the environment simply isn't in the list.
Application installation limits were removed on 30 June 2024. There's no longer a cap on how many environments you can install into.
Uninstalling leaves the user-experience solutions behind but disconnects the services. The environment keeps its records, shows a banner, and can't send email or process segments until you reinstall.
Reinstalling onto an environment that has had Journeys before should be done with the same user ID that ran the original install.
Releases are monthly. Check and apply via Settings > Versions > Manage + Update. Automatic upgrades roll out in the first week of most months (April and October are skipped for the release waves), regionally staged, with at least five days' notice to admins.
Quota state sits at Settings > Overview > Quota limits: monthly interaction quota, interacted people, Litmus email previews and text message allowances. Monthly interaction quota is ten times the interacted-people quota and resets on the 1st; people who haven't received an interaction in twelve months drop out of the interacted-people count.

When to use / skip

There isn't really a skip here — if the client has bought Journeys, someone has to do this. The judgement call is where you install it. The default temptation is to drop it onto the existing Sales or Customer Service production environment because the contacts are already there. That's usually right for data reasons and usually painful for release reasons: Journeys ships monthly and its solutions are large, so it drags the whole environment's update cadence along with it.

If the client has a mature ALM pipeline with a slow, gated release process on the CRM environment, push back and have the conversation early. If they have a single environment and no pipeline, install alongside and move on — a separate environment means you inherit a contact synchronisation problem, which is worse.

Always install into a sandbox first, even on a small project. You want somewhere to see what the solutions do to your existing forms and plugins before it lands on production.

Configuration decisions

Which environment hosts Journeys: shared with the core CRM environment, or standalone with contacts synchronised in. This is effectively a one-way door once real consent and interaction data accumulate.
Region and geo for the environment. Data residency matters here, and sending email, form prefill and analytics connectors all move customer content outside the geo by design.
Whether Customer Insights - Data is also in scope. If it is, connect the two (Settings > Data management > Customer Insights > Connect) and add contact and lead tables as a Dataverse data source on the Data side before anyone builds a segment.
Environment type for non-production: subscription-based Trial for a throwaway proof of concept, Sandbox if you want copy/restore and a real pipeline.
Whether to take manual control of updates rather than accepting the automatic rollout, and whether you need a deferral for a specific month.
Which security group is attached to the environment. Journeys is capacity-licensed, so any tenant user can otherwise reach the app URL.

Gotchas

Custom plugins on contact or lead frequently block the install. Run Solution Checker first and disable anything that fires on create/update of those tables during the install window.
Records owned by disabled or departed users will stop the install. Reassign ownership before you start; the failure message is not always specific about which records.
If the install fails, use the Diagnose action in the installation management area before retrying. Blind retries waste an afternoon.
The free Customer Insights - Journeys user licence assigned in the Microsoft 365 admin centre does not grant access to any other Dynamics 365 app. Assign it only to people who genuinely need marketing and nothing else.
Users who hit the environment URL are auto-created from Entra ID and given a default role. That is not the same as being correctly permissioned, and it quietly inflates your user list.
Quota is a tenant-level entitlement shown per environment. A forgotten trial on the tenant will show as "other orgs in your tenant" consumption and confuse the numbers.

Consultant notes

Get the Block unmanaged customizations setting and the plugin cleanup agreed with the client's platform team before you book the install date. Those two account for most failed first attempts.
Demo the Quota limits page to the client early. It's the only place they'll see interaction consumption, and finance always asks about it in month two.
Tell the client plainly that Journeys updates monthly and that they cannot indefinitely defer. If their change process can't absorb that, the environment topology decision needs to change, not the release cadence.
Before go-live, check Settings > Versions against the current release, confirm domain authentication is complete, and confirm the D365 Marketing service account still holds all its roles.

Worth revisiting when the install prerequisites shift or Microsoft changes the release cadence again.