MB-230 Microsoft Dynamics 365 Customer Service Functional Consultant Exam Topics and Questions

This is where the exam puts most of its weight. Case management is the operational core of Dynamics 365 Customer Service, and the breadth here is deliberate: you are expected to know how a case moves from creation through resolution, how the system enforces service commitments, and how AI features fit into a live agent's daily workflow. Gaps in any of those three areas will cost you marks, and this topic reaches into every part of the product.

– Foundational setup and the case lifecycle

Before anything else works, the foundational components have to be configured correctly: record creation and update rules, the case resolution experience, and the security roles that control what agents and supervisors can see and do. Record creation rules are a frequent exam target because their logic is specific: the conditions, the actions, and the monitoring of those rules all behave in ways that differ from general Power Automate flows. The case resolution experience is configurable, and knowing which settings change the dialog versus which change the underlying data matters. Security roles in Customer Service are layered on top of Dataverse roles, so understanding what the Customer Service-specific roles add is the testable detail. The timeline control sits at the centre of the case form: which record types appear, how card forms are configured, and how highlights surface key information are all exam-ready details.

– Knowledge management and external sources

Knowledge management spans more sub-topics here than almost any other area, which tells you how seriously the exam treats it. You need to know how to set up the knowledge base from scratch: configuring the tables that store articles, managing translated versions, and controlling what agents can search internally. External knowledge sources add another layer: integrating them requires specific configuration steps that differ from the internal search setup. AI suggestions and Copilot-led article creation are explicitly in scope. For Copilot features, the exam tests configuration, not just awareness. Know where in the interface you enable AI suggestions, how you filter the content Copilot draws on, and what the administrator controls versus what the agent controls. Translated articles are a detail many candidates skip; the exam does not.

– Microsoft Teams collaboration and Copilot agent features

Teams integration in Customer Service goes well beyond a simple chat button. The exam distinguishes between configuring Teams chat, enabling agents to join a Teams call, and setting up suggested contacts, which can be driven by AI or by rules-based logic. Each of those has its own configuration path, and conflating them is a common mistake. The Copilot and agent features sub-group covers Ask a Question (including content filtering), case and conversation summaries, Draft a Response, and the Case Management Agent. Integrating agents with Customer Service through plug-ins and knowledge sources is also in scope. The exam tests whether you know which feature does what and where you configure it, not whether you can describe AI in general terms.

– SLAs, KPIs, and timers

Service Level Agreements are a standalone configuration discipline, and the exam treats them that way. SLA settings, SLA items, KPIs, warning actions, success actions, and applicability rules are all individually testable. You need to know the difference between an SLA and an SLA item, and between a KPI and the timer control that surfaces it on a form. Power Automate actions triggered by SLA events are in scope: the exam asks about the mechanics of that integration, not just that it exists. Applying SLAs to cases, including the rules that determine which SLA applies when multiple could match, is a practical configuration question that rewards candidates who have actually worked through the setup rather than read about it.

How Manage cases in Customer Service is tested

Items in this topic tend to present a business requirement and ask which configuration step, in which order, produces the described outcome. The trap is almost always specificity: two options will both sound plausible, but one applies to the wrong layer of the product. A question about SLA KPIs, for example, rewards knowing whether a setting belongs on the SLA item, the KPI record, or the timer control on the form. Copilot and AI feature items reward knowing the administrator-facing configuration steps rather than the agent-facing experience. Knowledge management items often test the difference between internal search configuration and external source integration. Candidates lose marks by applying general Dataverse or Power Automate logic where Customer Service-specific configuration is required. The volume of sub-topics means that broad familiarity without depth on any single area is a losing strategy: the exam will find the gaps.

Where the first topic covers the case itself, this one covers the system that gets work to the right agent and gives that agent the tools to handle it efficiently. Routing in Dynamics 365 Customer Service is a multi-layer configuration: workstreams, queues, classification rules, and assignment logic all interact, and the exam expects you to know how each layer behaves independently and in combination. Productivity tools add another dimension, because they sit inside a workspace that is itself configurable.

– Routing architecture: workstreams, queues, and capacity

Workstreams are the starting point for routing configuration. Every channel of incoming work passes through a workstream, and the settings you apply there, including user settings and capacity profiles, shape how work is distributed downstream. Capacity profiles control how much work an agent can hold at once, and the exam tests the relationship between a profile and the queue it applies to. Queues themselves have configuration options that affect assignment: understanding the difference between a basic queue and a messaging queue, and which routing type applies to each, is a detail that separates candidates who have configured routing from those who have only read about it. Basic routing rulesets sit alongside the more sophisticated classification and assignment rules; knowing when each is appropriate is the testable distinction.

– Classification, assignment, and skills-based routing

Work classification determines what a work item is before assignment decides where it goes. The exam tests both steps as distinct configuration tasks. Classification rules attach attributes to incoming work; assignment rules use those attributes to pick a queue or an agent. Skills-based routing adds a third element: the skill finder model, which must be configured and trained separately from the routing rules themselves. Candidates often conflate classification rules with assignment rules because both involve conditions, but they operate on different objects at different points in the routing pipeline. Routing for records, as distinct from routing for conversations, has its own configuration path that the exam treats as a separate skill. Knowing which settings appear under unified routing versus which appear under the legacy routing engine can be the deciding factor on a narrow question.

– Productivity tools, workspace, and experience profiles

The Copilot Service workspace is the agent-facing environment, and its configuration is fully in scope. Session templates define what opens when an agent accepts a work item; application tab templates control what appears within a session. Experience profiles bring those templates together and determine which agents see which workspace configuration. The Inbox, including the ability to create custom views within it, is a recent addition that the exam now covers explicitly. Scripts and macros sit on the productivity side: scripts guide agents through a process step by step, while macros automate repetitive actions. Slugs, which are the dynamic data tokens used inside scripts, are a specific detail that the exam uses to test whether candidates understand how scripts are actually built rather than just what they do.

How Configure representative experience and routing is tested

This topic rewards candidates who can trace a work item from the moment it enters the system to the moment it lands with an agent. Items often describe a routing outcome, such as work not reaching the intended queue, and ask which configuration element is responsible. The trap is the layered nature of routing: the fault could sit in the workstream, the classification rule, the assignment rule, or the queue itself, and the exam expects you to isolate the correct layer. Skills-based routing items reward knowing the skill finder model as a distinct configuration object. Productivity tool items tend to test the difference between a session template and an application tab template, or between a script and a macro. Experience profile items reward knowing that profiles are the control point for which agents get which workspace setup. Candidates who treat routing as a single feature rather than a pipeline of distinct configuration steps consistently lose marks here.

After routing and case management, the exam turns to the layer that sits beneath both: the data model, the UI components, and the integrations that connect Customer Service to the rest of the Microsoft ecosystem. This topic is less about the Customer Service application specifically and more about the platform it runs on. Candidates with a strong Dynamics 365 or Power Platform background will find familiar ground here, but the Customer Voice and Dataverse search sub-topics have details specific enough to catch anyone who relies on general platform knowledge alone.

– Data model: tables, columns, and relationships

Creating and modifying tables, configuring columns, and setting up relationships are foundational Power Platform skills, but the exam tests them in a Customer Service context. That context matters: the question is rarely whether you can create a column, but whether the column type, the relationship cardinality, or the table configuration is appropriate for the described Customer Service scenario. Configuring Dataverse search is in scope as a distinct task: enabling it, selecting which tables and columns are indexed, and understanding how it differs from the legacy Quick Find search are all testable details. Candidates who treat Dataverse search as simply a search box miss the configuration depth the exam expects.

– Forms, views, model-driven app components, and notifications

Forms and views are the primary way agents interact with data, and the exam tests both creation and modification. The distinction between creating a new form and modifying an existing one matters because some settings are only available at creation time. Configuring model-driven app components, including which tables appear in the navigation and how the sitemap is structured, is in scope. Alerts and in-app notifications are a newer area: the exam tests how they are configured and triggered, not just that they exist. Email templates, which can be created and managed independently of the case or conversation they support, are a separate configuration task that the exam treats on its own terms.

– Customer Voice: surveys, distribution, and case integration

Customer Voice is the survey layer that closes the feedback loop after a case or conversation. The exam covers three connected tasks: triggering survey distribution, personalising the survey content, and writing the results back to cases and conversations in Dataverse. Each step has a specific configuration path. Triggering distribution is typically done through Power Automate, and the exam tests the connection between the survey distribution settings in Customer Voice and the flow that fires them. Personalisation uses variables that pull data from the triggering record; knowing how those variables are defined and passed is the testable detail. Populating survey results against cases and conversations requires mapping, and the exam expects you to know what that mapping looks like and where it is configured.

How Extend Customer Service is tested

Items in this topic often present a scenario where an organisation needs to capture, display, or search data in a way the out-of-the-box configuration does not support, then ask which platform component solves the problem. The trap is picking a solution that works in general Power Platform terms but is wrong for the Customer Service context, or picking a Customer Service feature when a platform feature is the appropriate tool. Dataverse search items reward knowing the indexing configuration rather than the search experience itself. Customer Voice items reward knowing the full pipeline from trigger to result, and candidates who know distribution but not the result-mapping step lose marks on scenario questions that span both. Form and view items tend to test modification rules: what can be changed on a managed component, what requires an unmanaged layer, and what is locked entirely. Email template items are often the most straightforward in the topic, but only for candidates who have worked with them in practice.