MB-910 Retired: Historical Blueprint and Next Steps

Historical MB-910 Scope

MB-910, Microsoft Dynamics 365 Fundamentals (CRM), retired on 2025-12-31. Its published domains cover Describe Dynamics 365 Customer Insights, Describe Dynamics 365 Sales, Describe Dynamics 365 Customer Service, Describe Dynamics 365 Field Service, Explore the core capabilities of customer engagement apps in Dynamics 365. The historical MB-910 blueprint remains a compact map of the customer lifecycle. Customer Insights forms and segments audiences, Sales advances opportunities, Customer Service resolves cases, and Field Service carries service into scheduled onsite work. The useful artifact is that process map, not the retired exam target. Microsoft does not name a direct replacement in the reviewed official sources. This page keeps the dated blueprint useful while separating verified lifecycle facts from recommendations.

Who MB-910 Was For

The original audience was learners who used the fundamentals exam to understand how Dynamics 365 customer engagement applications support marketing, sales, service, and field operations. This historical page is for prior learners, credential holders, training teams cleaning up old material, and practitioners mapping durable knowledge into a current role-based plan.

Skills You Should Be Ready to Demonstrate

• Explain how Customer Insights supports profiles, segments, journeys, and engagement
• Map Dynamics 365 Sales capabilities to the lead and opportunity lifecycle
• Relate Customer Service cases and knowledge to agent and customer outcomes
• Connect Field Service work orders, scheduling, assets, and mobile execution

How to Reuse Your Preparation

Reuse the blueprint as product orientation. Trace one customer scenario through profiles and journeys, lead qualification, an opportunity, a service case, and a field work order. Then choose a current Microsoft credential from the active catalog based on the job role or application you actually need to operate. Start with the dated Microsoft guide, map each objective to a task, decision, observable result, and failure mode, and use domain ranges to balance coverage rather than predict question counts. Keep notes labeled with the guide date so future product or blueprint changes do not silently contaminate the plan.

Historical Domain Guide

Describe Dynamics 365 Customer Insights: Historical Scope

Domain 1, Describe Dynamics 365 Customer Insights, organizes related decisions rather than isolated product facts. The historical outline includes Explore Customer Insights - Journeys; Describe Customer Insights - Data. Practice by connecting the configuration or recommendation to prerequisites, downstream effects, evidence of success, and a safe correction when the expected result is not observed.

• Turn every Describe Dynamics 365 Customer Insights objective into a concrete task or decision you can explain
• Record the prerequisite, implementation choice, verification signal, and failure mode
• Mix this domain with adjacent domains so dependencies remain visible

Describe Dynamics 365 Sales: Historical Scope

Domain 2, Describe Dynamics 365 Sales, organizes related decisions rather than isolated product facts. The historical outline includes Explore Sales. Practice by connecting the configuration or recommendation to prerequisites, downstream effects, evidence of success, and a safe correction when the expected result is not observed.

• Turn every Describe Dynamics 365 Sales objective into a concrete task or decision you can explain
• Record the prerequisite, implementation choice, verification signal, and failure mode
• Mix this domain with adjacent domains so dependencies remain visible

Describe Dynamics 365 Customer Service: Historical Scope

Domain 3, Describe Dynamics 365 Customer Service, organizes related decisions rather than isolated product facts. The historical outline includes Explore Customer Service. Practice by connecting the configuration or recommendation to prerequisites, downstream effects, evidence of success, and a safe correction when the expected result is not observed.

• Turn every Describe Dynamics 365 Customer Service objective into a concrete task or decision you can explain
• Record the prerequisite, implementation choice, verification signal, and failure mode
• Mix this domain with adjacent domains so dependencies remain visible

Describe Dynamics 365 Field Service: Historical Scope

Domain 4, Describe Dynamics 365 Field Service, organizes related decisions rather than isolated product facts. The historical outline includes Explore Field Service. Practice by connecting the configuration or recommendation to prerequisites, downstream effects, evidence of success, and a safe correction when the expected result is not observed.

• Turn every Describe Dynamics 365 Field Service objective into a concrete task or decision you can explain
• Record the prerequisite, implementation choice, verification signal, and failure mode
• Mix this domain with adjacent domains so dependencies remain visible

Explore the core capabilities of customer engagement apps in Dynamics 365: Historical Scope

Domain 5, Explore the core capabilities of customer engagement apps in Dynamics 365, organizes related decisions rather than isolated product facts. The historical outline includes Describe the foundations of customer engagement apps. Practice by connecting the configuration or recommendation to prerequisites, downstream effects, evidence of success, and a safe correction when the expected result is not observed.

• Turn every Explore the core capabilities of customer engagement apps in Dynamics 365 objective into a concrete task or decision you can explain
• Record the prerequisite, implementation choice, verification signal, and failure mode
• Mix this domain with adjacent domains so dependencies remain visible