Microsoft retired Exam MB-910, Dynamics 365 Fundamentals (CRM), on December 31, 2025. This article retains its original certification title and URL as a historical guide to customer-engagement applications; it should not be used to register for an unavailable MB-910 exam. The underlying Dynamics 365 products continue to help organizations manage selling, customer service, field work and customer engagement. Understanding how information moves between these activities remains useful, but each current role and credential must be evaluated against its own Microsoft documentation.
Imagine a company that sells industrial equipment, maintains the units after delivery and communicates with customers about service appointments. A prospective buyer first contacts a seller, later accepts a quote and receives the equipment. Months afterward, the customer reports a fault and a service technician is dispatched. The customer may also choose to receive maintenance reminders while refusing unrelated promotional messages. This sequence connects Dynamics 365 Sales, Customer Service, Field Service and Customer Insights – Journeys without pretending that each application performs the same work.
What the retired MB-910 certification covered
MB-910 was a fundamentals examination about Dynamics 365 customer-engagement applications. It covered basic capabilities for sales, marketing or customer insights, customer service, field service and shared relationships between these products. A fundamentals credential could help a learner understand terminology and business purpose, but it never proved independent expertise in every product’s configuration. Its retirement means that historical objective percentages and an old exam code should not be used as current booking guidance or a claim of up-to-date certification.
The broad concepts are still relevant: customer information should be accurate, different departments should see only what they need, business processes should have clear owners, and actions should produce records that can be reconciled. A customer inquiry is not a committed order, a service case is not necessarily a technician work order, and a message being sent is not proof the recipient gave permission for it. These distinctions matter more to a reliable implementation than memorizing the names of buttons in an obsolete exam lesson.
Readers seeking a current Microsoft credential should use the live Microsoft certification catalog. For example, Microsoft’s AB-210 Sales AI Consultant assessment is a separate modern, AI-enhanced sales qualification, not a direct successor to every MB-910 topic. A beginner may benefit first from Microsoft Learn product training and an authorized environment rather than purchasing an exam simply because its name resembles a retired fundamentals test.
Dynamics 365 Sales tracks the commercial relationship
Dynamics 365 Sales supports account and contact management, leads, opportunities, product information, quotes and pipeline reporting. A contact is a person, an account may represent the organization, a lead is potential interest that still needs qualification, and an opportunity represents a possible commercial transaction. A useful configuration preserves those meanings across the sales lifecycle. The team should be able to explain how a lead becomes an opportunity and what evidence justifies a record moving to a later stage.
For the equipment business, create synthetic records for a buyer, the buyer’s company, an inquiry and a proposed sale. Record what the customer actually requested, which service options apply, and who approves a discount. Then test a quote revision and compare the customer-facing document with the approved product catalog and price list. A quote that generates successfully can still be wrong if it selects an outdated product or an unauthorized discount.
Pipeline and forecasting reports depend on these data definitions. An opportunity marked as won should reflect the business’s actual criteria, not a seller’s confidence. Create a negative test with a lost opportunity and confirm that it no longer contributes to active pipeline revenue. When sales accelerator or Copilot features are used, review suggested actions and summaries against the source records. Automated recommendations are not independent proof of customer intent or permission to contact somebody.
Customer Service manages problems and response obligations
Dynamics 365 Customer Service handles cases, service interactions and the processes for resolving or escalating customer problems. In the equipment example, a store reports a refrigeration unit that does not maintain temperature. The support team needs an accurate case with severity, reported symptoms, asset reference and service-level expectations. A customer service case records the customer’s request and the organization’s response; it is not always identical to a field technician’s work order.
Configure a small synthetic support queue with a normal request, an urgent fault and a duplicate case. Test assignment rules and escalation so that each record reaches the proper owner and an urgent customer is not lost in a generic backlog. The team should know which events pause or resume a service-level timer and what evidence is required to mark the issue as resolved. Closing a case without confirming the customer’s problem is addressed may improve a dashboard metric while making service quality worse.
A customer may share feedback through Customer Voice or another approved survey process. Feedback data and the service record have different purposes and permission requirements. A poor satisfaction score may prompt review, but should not automatically overwrite technical findings or personal details. If a survey is sent after resolution, verify that the correct contact receives it and that the message complies with the organization’s applicable communication policies.
A support consultant must also account for knowledge articles, suggested responses and agent assistance where supported. Generated summaries can save effort, but a user-facing answer should not fabricate the maintenance status of an asset or reveal a restricted account’s history. Responsible implementations test how a tool behaves with missing information, duplicate cases and an agent who does not have permission to view every record.
Field Service coordinates work beyond the contact center
When a customer problem requires a visit, Dynamics 365 Field Service can manage work orders, service tasks, resource booking, parts and customer assets. A dispatcher must choose an appropriately qualified person whose schedule, location and equipment fit the job. The customer service team may remain responsible for communication while the field team owns the physical repair. Explicit handoffs keep the customer from receiving conflicting messages about when someone will arrive or whether the equipment is safe to use.
For the refrigeration repair, create a synthetic work order and select an available technician who meets the required skills and travel constraints. Reserve a suitable replacement component and document what happens if that part is unavailable. A technician might need a second visit or a different specialist; a successful booking does not establish that the repair is complete. Record the outcome and next step so both customer service and dispatch can see an accurate status.
Mobile workers may record inspection results, photos and parts consumption through an approved mobile app. Offline capability depends on current configuration and synchronization behavior. Test the work order with a permitted device in a low-connectivity scenario, then verify that the edits reach the intended records after reconnection. Avoid treating a local “saved” confirmation as proof the server accepted every change. Protect customer names, addresses and photos during portfolio exercises by using fictional data.
A historical MB-240 Field Service guide offers additional context, but the MB-240 exam also retired in June 2026. It should be used to understand field-service processes, not as a recommendation to buy an obsolete exam voucher. A current implementation should follow the active Field Service product documentation and the company’s actual safety, maintenance and scheduling requirements.
Customer Insights connects engagement to consent and evidence
Dynamics 365 Customer Insights includes customer data and journey capabilities, but the two have different responsibilities. Customer Insights – Data can help organize customer information and calculated insights, while Customer Insights – Journeys helps design and deliver permitted engagement through segments and event-driven processes. The former Dynamics 365 Marketing name and retired MB-220 exam may appear in historical tutorials; those labels should not be treated as the full current product or an active certification path.
The equipment business might send a transaction-related service reminder and separately offer promotional updates. The contact-point permission for each type of message matters. A webinar registration or service request does not by itself authorize every possible future marketing campaign. Build a synthetic consent matrix for subscribed, unsubscribed and unknown addresses, and test the behavior of the selected compliance profile, purposes and topics. A campaign that sends to more people by bypassing consent is not a successful implementation.
Customer identity can be inconsistent across systems. A sales contact may use one email address, while a service case records another. Duplicates or delayed synchronization can lead to a customer receiving repeated messages or being included in the wrong segment. Define which source is authoritative, how records are matched and how updates affect consent. A unified profile is useful only when it preserves meaning, permissions and a reliable explanation of where each attribute came from.
Marketing measurement needs distinctions too. An email being sent, delivered, opened or clicked says different things, and some events are missing because of legitimate privacy protections. Report what each metric means and how recent the data are. A chart showing engagement cannot substitute for customer satisfaction, repairs completed or revenue actually recorded. The analyst should reconcile conclusions against the business events those dashboards claim to describe.
Shared platform data, security and automation need boundaries
Dynamics 365 customer-engagement applications use Dataverse and related platform capabilities for data storage, permissions and extensibility, subject to service-specific behavior. Shared data does not mean every user should have universal access. A seller may need account and opportunity details without permission to view sensitive service investigations, while a technician may need equipment history without seeing confidential commercial negotiations. Role-based access and approved ownership rules should be tested with separate synthetic identities.
Power Automate flows, integrations and other extensions can connect events across teams. The configuration must define which event is authoritative and how retries or duplicate messages are handled. For example, a field-service work order update should not create two customer notifications whenever the mobile app reconnects. Test repeated events and rejection scenarios, then document how staff will correct inconsistencies without losing the audit trail. Automation that runs quickly can also spread bad data quickly.
A useful end-to-end acceptance test begins with a lead, advances through a legitimate sale, generates a service case after delivery and dispatches a technician. Record which user owns each step, what status the receiving team expects, and which information should cross application boundaries. Add one exception: a wrong contact, a canceled booking or a revoked marketing consent. The system should prevent or expose inappropriate behavior rather than silently mark every process successful.
The lesson preserved from MB-910 is an understanding of connected customer activities, not an outdated set of exam answers. Microsoft retired the fundamentals exam on December 31, 2025, and other Dynamics 365 assessments have also changed independently. For current learning, use Microsoft Learn documentation and authorized practical scenarios relevant to the product and role. A customer lifecycle is trustworthy when records, permissions, communication and real-world outcomes agree, regardless of which historical certification first introduced the concepts.