The Microsoft MB-220 exam used to assess functional consultants working with Dynamics 365 marketing journeys, audiences and campaign operations. MB-220 retired on November 30, 2024. Its old study guides, registration instructions and practice-test promises must not be presented as a route to a currently available certification. The product work remains relevant, but it now sits within Dynamics 365 Customer Insights – Journeys and should be learned from up-to-date product documentation and tested business scenarios.
This article is for readers who have found an old MB-220 preparation page and need to know which skills are still valuable. It is not a replacement registration guide or a list of leaked examination questions. It is a way to assess whether a customer-experience workflow is correctly designed, legally permitted, measured and recoverable when contacts, segments or external services behave differently from a demonstration.
Separate the historical credential from the current product
The old exam followed the Dynamics 365 Marketing product era and evaluated knowledge of segmentation, customer journeys, events, lead handling and marketing operations. Microsoft’s retirement notice fixes the credential’s end date; a later feature name or an available course does not reopen the exam. Candidates preparing for another Microsoft certification should verify that credential’s own active exam and prerequisites instead of assuming a one-to-one successor.
For current implementation, begin with the tenant’s licensed capabilities, environments, release wave and data model. Customer Insights – Journeys often participates in a larger process spanning Dataverse, consent, sales, service, identity and reporting. A feature that looks ready in a design workshop can fail because the underlying contact identity or legal communication preference is incomplete. Product architecture should be planned around actual customer records and operational responsibility, not an old exam domain list.
Start with consent and a clear communication purpose
Suppose a service provider wants to send reminders about expiring maintenance contracts. The team must distinguish service messages that follow an existing obligation from marketing messages that may require separate permission under applicable law. Do not guess which message is permitted from the template name. Define the communication purpose, consent and compliance profile, relevant jurisdiction, the source of the preference and who can change it.
Test the record lifecycle: a contact opts out, updates a phone number, is merged into another record or requests deletion. Does the workflow respect the latest permitted channel and stop future sends promptly? Can staff trace which business rule authorized a particular message? A polished campaign that ignores consent history is not ready for production, no matter how many links were clicked during testing. Legal requirements vary; a product configuration is not by itself legal advice.
Give segments a business definition and an expiry rule
A segment is not just a collection of filters. It represents a claim about customers at a specific point in time. For a lapsed-customer reengagement program, document which transactions count as active service, how refunds are handled, whether duplicate contacts count twice and how frequently the segment refreshes. A live business rule may be more useful than a static export, but only if its update cadence and exceptions are understood.
Create examples for edges: a customer has two accounts; an invoice is unpaid but disputed; a contact has no valid email; an organization has one shared address for several employees. Check membership by querying the underlying data rather than trusting a segment preview. This makes the journey’s target population explainable to stakeholders who must answer complaints and audit questions later.
Design the journey as states, not a picture of arrows
A journey diagram shows the intended path; production behavior depends on triggers, entry conditions, delays, suppression checks, branching and exit rules. For each trigger, define what event is authoritative, whether it can arrive twice, and whether the customer is eligible to reenter. Determine what should happen if a scheduled reminder fires after a service renewal has already been completed.
Consider a two-message renewal journey. At entry, the system checks customer status and communication permission. After the first reminder it waits, then rechecks the business record before a second send. If renewal occurs during the delay, the journey must exit cleanly. If a trigger is processed twice, it should not produce duplicate outreach. These properties need test cases and observability, not only drag-and-drop configuration.
Connect sales handoff to a real owner
Marketing and sales teams frequently disagree about what qualifies as an actionable lead. Define the criteria: verified interest, product fit, territory, contactability and a recorded next action. A score alone is not a commercial handoff. A salesperson needs the relevant event, the customer’s stated preference and a clear reason to act now.
Test failures deliberately. What happens if a salesperson is inactive, the territory rule has no owner, the customer record is merged, or the CRM integration is temporarily unavailable? Keep an auditable queue of incomplete assignments rather than silently dropping opportunities. Useful metrics include assignment delay, unresolved ownership and conversion after accepted handoff; raw message volume is not evidence of commercial value.
Measure customer outcomes with reliable denominators
An email delivery count, a click rate and a booking conversion are different types of evidence. Define the denominator for each metric, the time window and exclusions before a campaign launches. A suppression can reduce total sends while improving the share of messages reaching eligible contacts. A high click rate can result from an unusually narrow audience rather than a successful program.
Where the objective is contract renewal, follow the customer record to completion. Separate customers whose subscription renewed independently from those whose actions followed outreach. Treat attribution as an estimate with explicit limitations unless an experimental design supports a causal conclusion. Monitor bounce reasons, consent-related complaints, journey failures, queue delays and unsuccessful CRM handoffs alongside top-line conversions.
Test with realistic records before releasing
Build a small test dataset: active customer, cancelled customer, lapsed contract, duplicate identity, no consent, channel opt-out, malformed address and a record that changes mid-journey. Exercise each state transition. Confirm that messages use appropriate locale and tokens, that links resolve without exposing private identifiers and that an opt-out is honored across all relevant future sends.
Run a controlled release with a named owner, change log and rollback conditions. An operational runbook should explain how to pause sending, disable an integration, investigate unexpected entrants and reconcile affected customers. A successful test is not merely receiving a preview email; it is proving the rules still behave correctly when the data and business process change.
Make deliverability and exceptions someone else’s reproducible test
A perfectly designed customer journey can still perform poorly if sender authentication, contact hygiene and message composition are weak. Work with the responsible mail-delivery team to check the authorized sender domain, relevant authentication records, bounce processing and suppression behavior. Inspect how hard bounces and complaints alter future eligibility. Avoid treating deliverability as an abstract score that improves by simply sending more messages; legitimate sender reputation depends on responsible audience management and recipients’ expectations.
Ask what happens when a contact has multiple identities, a sales representative manually sends the same reminder, or an integration synchronizes a record after the journey’s decision point. Can an operator locate the customer event and determine whether a second send is permissible? If the platform doesn’t supply a direct, auditable view, the process may require additional logging or an upstream change. Problems that cannot be explained later become customer-service liabilities even when the campaign dashboard looks healthy.
An effective release note should identify the business owner, compliance reviewer, data steward, operational support queue and approved rollback action. Include which metrics trigger a pause—unexpected volume, a spike in opt-outs, mispersonalized content or duplicate sends. These controls turn a marketing configuration into a governable customer communication service and offer a much stronger qualification test than memorizing screens from a retired MB-220 exam.
Use the old curriculum as history, not current booking advice
Retired MB-220 content can help explain the relationship between segments, consent, journeys, events and lead handling. But old user-interface paths, limits, licensing assumptions and exam logistics may no longer describe the current product. Review the documentation for the features actually enabled in your tenant and version, and verify the intended outcomes with reproducible tests.
For a portfolio or interview, present one governed customer journey: the business objective, a permission-aware audience, a reentry policy, an exception test, a measurement definition and a rollback plan. That demonstrates the ability the historical exam was trying to recognize without misleading readers into studying for a credential they can no longer schedule.