The Microsoft Dynamics 365 Marketing / Customer Insights (Journeys) Functional Consultant exam MB-220 retired on November 30, 2024. Its historical Microsoft MB-220 study guide documents that retirement. The product’s marketing and data-governance concepts remain useful, but candidates must not mistake old certification materials for a bookable October 2026 examination.
Consider a company launching a webinar campaign using email and SMS. Its marketing team has customer records from sales, a web signup form and an imported event list. Before building an automated journey, the team must establish who consented to which channel and purpose and whether any recipient is already registered or opted out.
Put contact-point consent before audience volume
Current Customer Insights – Journeys uses consent at the contact-point level, such as a particular email address or phone number. The existence of a contact record does not authorize promotional messages. A person may accept service updates at one address but decline commercial email at another. Purpose, topic, channel and the organization’s compliance model determine whether the proposed message may be sent.
Microsoft’s contact-point consent guidance describes restrictive, nonrestrictive and disabled enforcement. The organization remains responsible for choosing an appropriate legally reviewed configuration. Disabling consent checks to make a segment larger is not an acceptable shortcut when the intended communications require permission.
Test imported signup records with explicit opt-in, opt-out and missing-consent states. If a web form feeds Dataverse via a cloud flow, record how the consent event is created, updated and audited. A data import should not fabricate an opt-in because a field is blank. Changes in preferences need a reliable route back to the messaging system.
Prove segmentation and journey state
Define a webinar segment as existing customers in specified markets who have not registered and whose intended contact point meets the campaign’s policy. Create examples at the boundaries: duplicate contacts, a changed region, a registration received late and a customer whose preference has just changed. Segment size by itself is not proof that the selected people are correct.
A journey may send an invitation, wait for registration and send a reminder only when the recipient remains eligible. Specify entry, exit, reentry and suppression conditions. An interruption or retry must not send a second unwanted message. Use an isolated audience to compare actual sends with the decision table before activating a real campaign.
When a message is suppressed or fails, troubleshoot the contact point, compliance profile, journey version, channel delivery status and entry conditions. A send error is not always a platform outage; it may be the desired outcome of a permission rule. Preserve the explanation so the marketing team does not “fix” compliance by loosening it.
Measure campaigns without claiming unsupported causality
Deliveries, opens, clicks, registrations and attendance are different measures. Open tracking is incomplete when clients or privacy settings prevent it, and a conversion after several touchpoints cannot automatically be credited to the last email. Use consistent event definitions, holdouts when appropriate and contact feedback before claiming an improvement.
AI-assisted content or personalization requires review of factual claims, preferences, source data and sensitive attributes. Test template fields with realistic but non-sensitive sample records. An automated message should not invent prices, expose a customer’s purchase details or cite an unsupported claim about the product.
Preserve historical credential context, build current evidence
People who hold an MB-220 credential can describe it according to their actual Microsoft record without presenting the retired exam as current. A modern marketing-operations portfolio is better served by a documented consent design, a segment acceptance table, a safe trial journey, suppressed-message tests and postcampaign review.
Keep the communication approval, journey version and consent settings together so reviewers can reconstruct what governed a message when it was sent. This makes the marketing workflow auditable and repairable independently of an expired certification label.