A concrete platform-limit change

Microsoft announced on 18 June that paying Dynamics 365 Customer Insights customers could install Customer Insights - Journeys and Customer Insights - Data without the previous limit of four application installations. The change addressed installation count; entitlements, capacity and other service limits remained.

Marketing teams can use additional installations for regions, brands, organizational units or test environments. This can simplify rollout and data separation. It can also create more consent models, segment definitions and automations to maintain.

More environments need a portfolio

Create a register with environment, business purpose, region, owner, data sources, consent responsibility and expected lifetime. A new environment needs an explicit reason and measured requirement that an existing installation cannot meet. Test data movement and deletion before activating customer journeys.

Microsoft had previously recommended transition to real-time journeys. Additional installations do not remove the need for a governed move from older outbound marketing. Teams must map active journeys, integrations and reports and avoid copying obsolete configuration into new environments.

Automation with shared control

Choose one new installation and measure time to an approved setup, manual configuration steps and consent or segment exceptions. Reuse templates where rules are genuinely shared, while local owners approve channels, time zones and data use. Monitor capacity across the portfolio rather than per environment alone.

The June change makes the platform more flexible for larger and composite organizations. It does not automatically demonstrate lower cost or faster campaigns. Value appears when environments provide a necessary boundary, automation remains maintainable and customer information is treated consistently. Retire unused installations through a documented export or deletion and shutdown of connected flows.

Before creation, an architect and marketing owner should decide whether the need requires another installation or only a business unit, journey or security role. Record the choice and expected operating, support and analytics cost. For regional environments, local owners verify language, time zone, sending domain and consent rules.

Then test configuration recovery and controlled shutdown of a test journey. Confirm that scheduled messages stop, integrations stop writing and reports identify the correct environment. This lifecycle test makes the flexibility safer and prevents unlimited installations from becoming unlimited technical debt. Review the portfolio quarterly using capacity, activity, owner and retirement date as fixed decision points. Before retaining an environment, its owner should show the customer need it still serves and the integrations that remain active.

Sources

Microsoft Dynamics 365 Blog, “Announcing unlimited application installs in Dynamics 365 Customer Insights,” 18 June 2024

Microsoft Dynamics 365 Blog, “Transition to real-time journeys: the time is now,” 9 January 2024

Join the discussion

What have you learned from trying new marketing tools? Share what worked and what you needed to change.