MB-910 After Retirement: Where Dynamics 365 CRM Skills Fit Now

MB-910 is no longer an active Microsoft exam. Microsoft retired Dynamics 365 Fundamentals (CRM) on December 31, 2025, along with the MB-910 exam. That means older material describing MB-910 as an entry point candidates can still schedule is now outdated, even though the customer-relationship concepts behind the exam remain useful.

The retired MB-910 covered the purpose and capabilities of Dynamics 365 customer engagement applications, including sales, customer service, field service, marketing-related capabilities, shared platform concepts, reporting, and how Microsoft business applications support customer processes. It was broad by design because it was a fundamentals credential rather than a job-role certification.

There is no single exam that simply replaces MB-910. Microsoft’s current direction is more role-specific and increasingly AI-oriented. Someone who used MB-910 to explore CRM now needs to decide what work they actually want to perform: customer service configuration, finance, sales-related business solutions, development, architecture, administration, or another Dynamics and Power Platform role.

This is an important change in study strategy. A fundamentals exam lets a learner stay broad for a while; a role-based path asks for evidence that the learner can design or operate a real business process. The transition should therefore start with the kind of work you want to own, not with the search for the nearest surviving exam number.

MB-910 was a map of customer engagement, not a deep implementation exam

The value of MB-910 was breadth. Candidates learned why organizations use CRM systems, how customer records support business processes, and how Dynamics applications divide responsibilities across sales, service, marketing or journey management, field work, and shared platform capabilities.

That broad view remains useful because CRM implementations still connect people, data, and process. A customer may begin as a lead, become an opportunity, purchase a product, open a support case, receive communications, and later require on-site service. Different applications may own different stages, but the customer experience spans them.

What has changed is certification strategy. The retired Dynamics 365 Fundamentals credential should now be treated as historical context rather than a current target. New learners can keep the conceptual map while choosing a current path that matches a job role.

That historical framing also prevents an easy mistake: continuing to study old product naming as though it were a current blueprint. Customer engagement products and AI capabilities continue to evolve. The durable concepts are customer data, business processes, security, service operations, automation, and analytics—not the exact menu names used in an older fundamentals course.

Dataverse remains the shared business-data foundation

Many Dynamics 365 customer engagement applications use Microsoft Dataverse as the underlying business-data platform. Tables, relationships, ownership, security roles, auditing, APIs, and solution components provide a common structure that applications and Power Platform services can share.

This is one of the most transferable MB-910 concepts because role-specific specialists still need to understand the data foundation. A customer service consultant may work with accounts, contacts, cases, activities, queues, entitlements, and knowledge. A sales-oriented solution may use leads, opportunities, products, and activities. The applications differ, but data relationships and security remain central.

New learners should therefore go beyond memorizing application names. Create a small Dataverse model, trace how a record moves through a process, examine ownership and permissions, and observe how apps and automation reuse the same data. That practical foundation supports several current Microsoft business-applications roles.

Pay attention to data ownership and security while doing this. A user should not automatically gain access to every record simply because the application exposes the table. Record ownership, teams, business units, roles, and sharing determine who can work with customer data. Those controls matter in every role-specific implementation that grows out of the old MB-910 foundation.

Customer service is one clear current specialization

Professionals who are most interested in cases, queues, knowledge, entitlements, service-level agreements, routing, and agent productivity can move toward the current Dynamics 365 Customer Service Functional Consultant Associate role. The associated MB-230 exam goes much deeper than MB-910 ever did.

A functional consultant needs to translate service requirements into configuration. That includes understanding how work enters the system, how it is routed, which agents can see it, what knowledge is available, how service commitments are tracked, and how supervisors measure outcomes. The role is about operational design, not merely knowing what the Customer Service application does.

This is a useful example of Microsoft’s move away from broad fundamentals. A learner who once would have taken MB-910 to “learn CRM” can now build depth around a real job such as designing and operating customer-service processes.

Hands-on preparation should include exception paths. Create a case that misses its service target, a case that needs escalation, a routing condition that sends work to the wrong queue, and a user who lacks access to the required customer record. Troubleshooting those cases develops consultant judgment that a fundamentals survey could never test deeply.

Finance and operations roles are separate from CRM fundamentals

MB-910 focused on customer engagement and should not be confused with finance and operations work. Microsoft retired the separate MB-920 Dynamics 365 Fundamentals (ERP) exam on the same date, but specialized roles remain available for deeper functional work.

For example, the Dynamics 365 Finance Functional Consultant Associate path focuses on financial management, accounts receivable, accounts payable, budgeting, fixed assets, cash and bank, tax, and related business processes. That is a different professional destination from customer service or sales.

The distinction matters for career planning. A person who enjoys customer journeys and service operations should not choose a finance credential merely because both are under the Dynamics brand. Start from the business domain you want to implement, then select the role that owns those processes.

Role choice should also account for how you prefer to work. Functional consultants spend significant time in workshops, configuration, testing, documentation, and process design. Developers spend more time on extensions, integrations, and code. Architects operate across systems and make broader solution decisions. The product family overlaps, but the daily work is different.

Power Platform skills increasingly overlap with Dynamics implementation

Dynamics applications do not exist in isolation from Power Platform. Dataverse, Power Automate, Power Apps, Power Pages, Power BI, and Copilot Studio can extend or connect business processes. Functional consultants therefore benefit from understanding when a requirement belongs in standard Dynamics configuration and when a Power Platform component is appropriate.

A flow can automate a cross-system process. A Power App can provide a specialized user experience. Power BI can analyze operational data. Power Pages can expose selected processes externally. Copilot Studio can add agents that answer questions or invoke bounded actions. The technical possibility is broad, but architecture and governance should prevent every small requirement from becoming a separate custom solution.

The core MB-910 lesson still helps here: understand the business process first. Technology should support the process rather than determine it.

Application lifecycle management becomes important as soon as these extensions matter to production. Solutions, environments, connection references, permissions, and deployment practices help teams move changes from development to production without rebuilding them manually. That discipline is another area where role-based learning goes beyond what a fundamentals exam was designed to cover.

AI changes customer engagement, but it does not remove process design

Microsoft business applications increasingly include copilots, agents, summarization, recommendations, natural-language assistance, and AI-supported automation. These features can improve agent productivity and reduce repetitive work, but they also create new questions about data access, grounding, permissions, auditability, and human review.

An agent that summarizes a case is different from an agent that can change customer data or trigger a business action. The more consequential the action, the more carefully authentication, authorization, confirmation, and logging should be designed. AI should not bypass the same business rules and controls that a human user must follow.

This is another reason modern role-based learning matters. Fundamentals provide vocabulary, but current implementations require practitioners who can connect AI features to the operational and governance requirements of a specific business role.

Evaluation should also be scenario-specific. An AI-generated summary can be checked for factual completeness. A suggested response can be reviewed for tone and policy compliance. An agent that invokes a tool must be tested for authorization and safe failure behavior. “It uses AI” is never sufficient evidence that the feature belongs in a production process.

Legacy MB-910 knowledge is most useful when converted into hands-on scenarios

If you previously studied MB-910, inventory what you already know. You may understand the purpose of Dynamics applications, Dataverse, security, reporting, customer records, and basic process concepts. Keep that foundation, but stop studying the retired exam blueprint as though it were current.

Choose one business scenario and implement it in greater depth. For customer service, create a case intake and routing process. Define queues, knowledge, permissions, and service targets. For another role, select an equivalent end-to-end process and document requirements, configuration, exceptions, and testing.

This exercise reveals whether your knowledge is conceptual or operational. Being able to name the applications is fundamentals-level knowledge. Being able to design a process, secure it, test exceptions, and explain why the configuration satisfies the requirement is role-level competence.

Add a small handoff document as if another consultant will inherit the solution. Record assumptions, data ownership, security roles, workflow conditions, test evidence, and unresolved risks. That work forces you to connect product behavior to business intent and is a much stronger indicator of readiness for current role-specific study.

The right successor to MB-910 is a role decision, not a replacement code

Do not search for a one-to-one “MB-910 replacement exam.” Microsoft’s certification structure has moved away from that broad CRM fundamentals assessment. Instead, identify the work you want to perform and choose a current credential only when it matches that responsibility.

The Microsoft certification inventory includes current paths across Dynamics, Power Platform, Azure, data, security, and AI. The broader Microsoft role-based certifications can help you see how business-application roles sit alongside technical cloud roles without implying that one path is the universal next step.

MB-910 still has value as a historical introduction to Microsoft CRM concepts. What it no longer provides is a current certification destination. Keep the mental model of customer data, connected processes, security, and business applications, then build depth in the role that matches your work. That is the most accurate way to carry the old fundamentals forward into the 2026 Microsoft ecosystem.