Microsoft MB-910 Retired: Connecting the Customer Story

A customer complains that a service team keeps asking for the same information already provided to sales. Both teams use Microsoft technology, yet their processes create separate records, permissions and measures. Understanding Dynamics 365 customer relationship management begins with recognizing how sales, customer service and engagement capabilities relate—and where a shared platform does not automatically produce a shared customer experience.

Microsoft MB-910, Dynamics 365 Fundamentals (CRM) , retired on December 31, 2025. Its historical scope introduced customer engagement applications and the business processes they support. Current learning plans must be checked against Microsoft’s active credentials.

CRM is the relationship, not only the database

Customer relationship management joins information about people and organizations with the work performed to win and support their business. An account may contain several contacts with different roles; a lead may exist before the business has a confirmed opportunity; a case records a service need. These distinctions matter because they determine the workflows, permissions and reports that support employees.

Model a business account with a buyer, technical contact and finance approver. Record a sales inquiry and then a support incident for an existing product. Decide which objects represent each event and which staff members need access. A data model that treats every interaction as an indistinguishable note makes reporting and follow-up harder. The point of a common platform is to preserve meaningful relationships while keeping processes clear.

Sales stages must represent evidence

Dynamics 365 Sales can help teams track leads, opportunities, quotations and activities, but a pipeline is only as honest as its stage definitions. A lead’s existence does not prove buying intent. The sales process should establish who owns the account, what qualifies an opportunity and how estimates are reviewed. Without these rules, automation creates more records without creating a better forecast.

Imagine two opportunities of equal value. One has a signed specification and a procurement deadline; the other is an informal inquiry. Ask whether both deserve the same forecast classification. Capture the difference in customer intent and required next action. Fundamentals candidates should understand the purpose of sales capabilities and common relationships, not confuse a product interface with a substitute for commercial judgment.

Service quality depends on routing and knowledge

Customer Service capabilities support cases, queues, knowledge and response commitments. A case should contain enough context to reach the right team, and a knowledge article should be appropriate to the product version and customer circumstances. Automated routing can reduce waiting when the underlying classification is reliable. If agents cannot see the relevant history or lack permission to access a resolution, the apparent automation advantage disappears.

Use a simple example of an outage affecting several customers. Explain why one major incident might be linked to multiple cases and why duplicate records distort service measures. Distinguish the first response promise from actual resolution. After an agent closes a case, the record should preserve enough evidence to explain the action taken and reopen the matter if the problem returns.

Engagement must include customer choice

Customer Insights capabilities can support segmentation and personalized journeys, but a customer with a matching profile does not necessarily consent to every kind of outreach. Sources must be reconciled, and preferences should be respected across channels. Fundamental CRM understanding requires recognizing how data quality, segmentation and consent interact before message design and measurement begin.

Consider a customer who browses a product and later withdraws permission for promotional email. The business may still have a legitimate reason to send a service communication, but it must use the correct purpose and channel rules. A segment should not silently reintroduce that customer because an older system has a positive opt-in field. Shared data makes a better experience possible only when it carries trustworthy preferences.

Platform integration is an operating responsibility

Customer-facing Dynamics applications often use Dataverse and connect with Microsoft 365, Power Platform and other business systems. Integration increases usefulness but also introduces questions about record ownership, refresh timing and security roles. A service agent should not automatically receive access to confidential sales information, and a salesperson should not have unrestricted control over support case outcomes.

A good legacy MB-910 study exercise follows a customer from inquiry to sale to service interaction. Identify the application role of each process, its records and the data that must cross boundaries. Then insert a duplicate contact and changed permission to see why governance matters. The exam is retired; the durable lesson is how CRM applications form one coherent business system when their processes and data contracts are deliberately designed.