Description

Currently, when Business Unit Scoping is enabled in Dynamics 365 Customer Insights – Journeys, entity views respect business unit segregation (e.g., Journeys entity shows only records for the user’s BU). However, the Analytics dashboards (Journey Insights, Email Insights, etc.) continue to display aggregated data for all business units in the environment. This creates a mismatch between data access and reporting, and limits the usefulness of BU scoping for organizations that require strict data isolation.

Problem

• Users belonging to a specific business unit (e.g., INTERNAL COMMS) see only their BU’s journeys in entity views.
• In Analytics, they see metrics for other business units’ journeys, even though they cannot access those records elsewhere.
• This violates expectations for BU scoping and introduces compliance and governance challenges for organizations with multiple BUs.

Impact

• Reduces trust in analytics for BU-specific performance reporting.
• Forces organizations to build custom Power BI dashboards or custom Dynamics charts to achieve BU isolation.
• Increases complexity and cost for multi-BU environments.

Proposed Solution

• Add Business Unit as a filterable field in all Real-Time Marketing Analytics dashboards (Journeys, Email, SMS, Push).
• Ensure default views respect the user’s BU when scoping is enabled.
• Optionally allow admins to configure whether analytics should show org-wide or BU-specific data by default.

Benefits

• Aligns analytics with BU scoping behavior.
• Improves data security and compliance for multi-BU organizations.
• Reduces need for custom reporting solutions.