MB-910 Dynamics 365 CRM Fundamentals: Sales, Service, Field Service, and Customer Insights

MB-910, Microsoft Dynamics 365 Fundamentals (CRM), retired on December 31, 2025. Its final study scope remains a useful introduction to the customer-engagement side of Dynamics 365 because it organized the platform around five related areas: Customer Insights, Sales, Customer Service, Field Service, and the shared capabilities that connect those applications.

The retired status changes how the exam should be discussed. Readers should not see MB-910 as a current certification target, but the workload map still helps explain how customer data becomes marketing activity, sales opportunities, support cases, scheduled field work, and reporting. The exam was intentionally foundational; it tested recognition of capabilities and business scenarios rather than deep implementation expertise.

The historical MB-910 page also provides a bridge to more specialized material. Sales concepts connect to the Dynamics 365 Sales functional-consultant subject area, service concepts to Dynamics 365 Customer Service, and configuration across customer-engagement apps often intersects with Power Platform. Those relationships are useful when clearly described as topic lineage rather than as a claim that the old fundamentals credential is still active.

Customer Insights connected audience understanding with customer journeys

The final MB-910 scope treated Customer Insights as both a data and engagement story. Customer Insights - Data unified information from multiple sources into customer profiles, measures, segments, and predictions. Customer Insights - Journeys used audience information to create targeted interactions, forms, email communication, events, and automated journeys. The exam expected learners to understand the purpose of these capabilities and when each would be relevant.

The distinction between data unification and journey execution is essential. A clean profile does not by itself create customer engagement, and a sophisticated journey is only as trustworthy as the data and consent model behind it. Fundamentals candidates benefited from thinking in a sequence: collect approved data, resolve identities, create usable segments, activate communication, then measure results and refine the next interaction.

Dynamics 365 Sales modeled the progression from prospect to revenue

Sales coverage began with leads and opportunities, then extended into accounts, contacts, activities, products, price lists, quotes, orders, and invoices. The business value came from giving sellers a consistent pipeline and giving managers enough structured information to forecast, coach, and identify stalled opportunities. Guided selling and process flows made the expected sales motion visible inside the application.

For a deeper historical treatment of this workload, Dynamics 365 Sales processes show how the sales role became a distinct certification topic. MB-910 remained at the recognition level: understand what the objects and features are for, how they relate, and why a connected pipeline is more useful than disconnected spreadsheets or private notes.

Customer Service organized cases, knowledge, routing, and service commitments

Customer Service focused on turning incoming problems into manageable cases. Agents needed queues, routing, activities, knowledge articles, entitlements, service-level agreements, and a workspace that kept relevant customer context close to the conversation. The fundamentals challenge was to recognize which capability supports a particular support scenario rather than to memorize every administrative option.

The modern MB-230 exam goes much deeper into configuring and operating Customer Service. The relationship is useful because it shows the difference between fundamentals and functional-consultant depth: MB-910 introduced the service lifecycle, while role-based material expects decisions about routing, knowledge, productivity, analytics, and how the support organization should actually work.

Field Service extended customer engagement into physical work

Field Service addressed situations in which resolving a customer need requires a technician, a location, time, skills, equipment, and often replacement parts. Work orders, bookings, resources, inspections, mobile experiences, assets, and scheduling combined to coordinate that work. The application therefore sits at the boundary between customer service and real-world operations.

A strong fundamentals interpretation follows the work order from creation to completion. The organization identifies the service requirement, finds an appropriate resource, schedules the visit, equips the technician with customer and asset information, records work and materials, and closes the job with an auditable history. That sequence explains the product better than memorizing isolated feature names.

Dataverse and Power Platform supplied the common application foundation

Customer-engagement applications share common records, security patterns, user experiences, and integration capabilities. Microsoft Dataverse provides structured business data and relationships, while Power Platform services can extend the experience with apps, automation, reporting, and integrations. MB-910 therefore included platform awareness because CRM processes rarely remain inside a single screen or department.

Readers who want to follow that configuration layer beyond fundamentals can compare the old CRM exam with PL-200 and the Power Platform functional-consultant role. The connection is especially relevant for forms, views, business process flows, automation, and governed extensions that support a Dynamics workload without replacing the core application.

Microsoft 365 integrations connected customer work with everyday productivity tools

Dynamics 365 customer-engagement apps frequently intersect with Outlook, Teams, Excel, Word, and SharePoint. Email and appointments may become activities, Teams can support collaboration around a record, Excel can help analyze or update data, Word can generate structured documents, and SharePoint can hold related files. Fundamentals candidates needed to recognize the business value of these integrations.

The important design principle is context. An integration is useful when it reduces duplicate entry or keeps collaboration attached to the customer process. It becomes harmful when users cannot tell which system is authoritative or when uncontrolled exports create competing copies of sensitive data. Even a beginner-level exam can teach that application integration needs ownership and governance.

Copilot features changed the interface but not the underlying process discipline

The final MB-910 blueprint referenced Microsoft 365 Copilot capabilities across customer-engagement scenarios. Generative assistance can summarize records, help draft communication, surface relevant information, or accelerate routine steps. Those features can make a workflow faster, but they do not remove the need for accurate customer data, appropriate permissions, review, and clear process ownership.

This is a useful historical endpoint for MB-910 because it shows the fundamentals track adapting to AI-enhanced business applications before retirement. The enduring lesson is to evaluate AI inside the workflow: what information it can use, what task it assists, what a human must verify, and how the organization prevents convenience from weakening compliance or customer trust.

The retired exam remains a compact map of customer-engagement responsibilities

A reader revisiting MB-910 should study the customer lifecycle rather than practice outdated scheduling details. Start with audience and profile data, move through marketing and sales, follow support interactions, and finish with field execution when physical service is required. Then examine the shared Dataverse, reporting, collaboration, and security foundation underneath those workloads.

Dynamics 365 CRM fundamentals can supplement that historical map, while broader Microsoft certifications help readers locate role-based exams that match present-day responsibilities. The old exam remains valuable when it clarifies the ecosystem and its process boundaries, not when it is treated as a current credential.

The final MB-910 outline also rewarded an ability to see one customer across applications. A person might first appear in a marketing segment, become a lead, progress into an opportunity, open a support case after purchase, and later require a field-service visit. The applications specialize in different stages, but the organization benefits when identity, activity history, consent, and account context remain connected instead of fragmenting into unrelated records.

That end-to-end view makes data ownership important. Sales teams may care about opportunity accuracy, marketers about consent and segment membership, service teams about entitlements and case history, and field teams about assets and work orders. A fundamentals learner should understand that “single customer view” does not mean every user owns every field. Governance still assigns responsibility for data quality, access, retention, and process changes.

Reporting provides another shared layer. Pipeline dashboards, service backlog, journey performance, field utilization, and customer measures answer different questions, yet all depend on structured records and consistent status values. When users bypass the application with private spreadsheets, the analytics lose credibility. The old exam therefore indirectly taught a data-discipline lesson: operational reporting improves only when the underlying workflows are actually used.

Because MB-910 is retired, practice should emphasize scenario classification rather than obsolete exam logistics. Given a business request, identify the relevant customer-engagement workload, the shared platform capability, and the data needed to support it. Then decide whether the request belongs at fundamentals, functional-consultant, or solution-design depth. That exercise keeps the historical material useful without pretending the old certification still represents Microsoft's current credential structure.

Finally, the retired exam is a reminder that Dynamics 365 customer engagement is not synonymous with “sales CRM.” Support, field operations, marketing journeys, customer data, and productivity integration all contribute to the relationship. Readers who preserve that broader model are less likely to design a solution around one department while ignoring the handoffs that determine the actual customer experience.

Customer engagement also depends on consent and communication preferences. Marketing and service teams may have legitimate reasons to contact the same person, but those reasons do not automatically grant unlimited use of every channel. A fundamentals understanding should include the idea that profiles, segments, journeys, and sales outreach operate inside privacy, preference, and organizational policies. Good customer experience is partly the discipline of knowing when not to send another message.

Cross-functional handoffs make strong practice scenarios. Let a marketing interaction generate a lead, qualify it into sales, convert the relationship into a customer, open a service case, and finally schedule a field visit. At each step, ask which application owns the work, which records should be shared, and which information should remain governed. That exercise turns the retired blueprint into a coherent customer lifecycle instead of five unrelated product descriptions.

MB-910 also makes a useful vocabulary checkpoint for people moving into specialized Dynamics roles. If a learner can clearly explain a lead, opportunity, case, work order, segment, journey, unified profile, Dataverse record, and business process flow without relying on screen memorization, later configuration material becomes easier to absorb. The retired exam remains strongest as that shared conceptual language across customer-engagement teams.