Implement and configure Dynamics 365 Customer Insights - Journeys
Install and configure
Customer Insights - Journeys is a model-driven app installed into a Power Platform environment that already hosts Dynamics 365 apps. The first decision in any scenario question is which app: Customer Insights - Journeys (marketing) is a separate product from Customer Insights - Data (customer data platform), and mixing them is a common distractor.
Settings exam questions target
- Email sending domain and domain authentication - outbound email only works reliably after the sending domain is verified and DNS records (SPF/DKIM) exist. "Emails land in spam after go-live" usually points here, not at the email designer.
- Business units and security roles - records are owned by business units, so a user who "cannot see the journey" often lacks a role or is looking at another business unit's record. Assign least-privilege marketing roles rather than System Administrator.
- Compliance and consent defaults - purpose/topic model, double opt-in, subscription center linkage, data residency region.
- Quotas - sending capacity scales with licensed contacts; exceeding the monthly limit blocks sends rather than degrading silently.
- Feature switches and Copilot - AI features require enablement and a supported region.
Traps to expect: settings are environment-wide, so a "fix" for one team changes behaviour for every business unit; and some questions have "this cannot be configured" as the correct answer (for example, using an unverified from-domain).
Rule of thumb: if the symptom is delivery, check domain authentication and compliance; if it is visibility, check business-unit ownership and security roles; if it is behaviour, check Marketing settings.