Microsoft AB-210 - Accelerating Sales Pipelines with AI in Dynamics 365

Create a Power Automate cloud flow.

Add a Dataverse trigger.

Define an approval step.

Test and activate the flow.

The correct automation pattern is an automated Power Automate cloud flow triggered by a Dataverse event. The case study states that the process must notify the seller’s manager when a draft quote is created and requires approval, and that approvals must use the Power Automate Approvals connector. Therefore, the flow should first be created as a cloud flow, then started by a Dataverse trigger such as when a row is added, modified, or deleted on the Quote table, filtered for the draft quote condition. Microsoft’s Dataverse trigger guidance confirms that this trigger runs when a selected Dataverse table row is created, modified, or deleted.

After the trigger is defined, the flow must include an approval step using Power Automate approvals. Microsoft’s approval workflow guidance states that Power Automate can manage approvals across services including Dynamics 365 and Dataverse-based processes. The final action is to test and activate the flow so the quote approval automation is available to users. Do not use a scheduled trigger because the requirement is event-driven, not time-based. Do not connect to the existing desktop flow because that desktop flow processes partner orders for fulfillment, not draft quote approvals. A Teams step is optional collaboration, not the required approval mechanism.

References/topics: Power Automate cloud flows; Dataverse triggers; Approvals connector; Dynamics 365 Sales quote approval automation; sales platform extension.

Requirement

Tool

Perform purchase required by CFO

Microsoft 365 admin center

Configure Sandbox billing

Power Platform admin center

Configure Production billing

Microsoft 365 admin center

Why: Production requires reliable AI capacity so sellers are not blocked when prepaid Copilot capacity is depleted. The correct production setup is pay-as-you-go / billing policy configuration through the Microsoft 365 admin center . Azure portal is not the best answer here because the scenario says no Azure subscriptions are available , and Microsoft 365 admin center can be used for the billing policy workflow. Microsoft Agent 365 is for agent management/governance, not billing configuration.

Requirement

Configuration

Automatically prioritize leads based on conversion probability

Predictive lead scoring

Ensure the lead scoring improvement requirement is met

Automatically retrain model

The correct capability for automatically prioritizing leads based on conversion probability is Predictive lead scoring . Dynamics 365 Sales predictive lead scoring assigns scores to leads so sellers can prioritize the leads most likely to qualify or convert. Microsoft’s Sales documentation states that predictive lead scoring helps sales teams prioritize leads based on scores and improve lead qualification outcomes. This directly matches Contoso’s requirement to guide sellers toward high-potential leads and reduce inconsistent manual prioritization across regions.

To meet the requirement that lead scoring must continuously improve based on historical sales outcomes, configure the model to automatically retrain . Microsoft’s predictive lead scoring guidance explains that retraining uses the latest leads in the organization to improve model accuracy, and automatic retraining allows the application to retrain the model every 15 days. This is the correct option because Contoso wants the scoring model to improve continuously as more closed lead outcome data becomes available.

“Lead scoring model” is too generic; the AI capability required is specifically predictive lead scoring. “Relationship intelligence” supports relationship analytics and engagement insights, but it does not score leads by conversion probability. “Configure forecast” applies to pipeline forecasting, not lead scoring accuracy.

References/topics: Predictive lead scoring; lead prioritization; scoring model accuracy; automatic model retraining; AI-driven lead qualification.

Requirement

Component

Mountaineer range

Product family

Athlete package

Product bundle

Metal range

Product property

The Mountaineer range should be configured as a Product family because it represents a product classification hierarchy. Dynamics 365 Sales uses product families to organize related products, child products, and bundles under a parent structure. Microsoft’s product catalog guidance states that product families can contain child product families, products, and bundles in a hierarchy, which fits the mountaineer cycle range with economy and premium fitting variations.

The Athlete package should be configured as a Product bundle because it combines multiple sellable items: a cycle, connected devices, and subscription-based analytics services. A bundle is used when multiple products are sold together as one commercial package. Dynamics 365 Sales allows products to be associated with a bundle, including quantities and required or optional components.

The Metal range should be configured as a Product property because sellers must choose a configurable attribute—chrome, aluminum, or titanium—when adding the mountaineer cycle to an opportunity. Product properties define product characteristics such as size, color, or component, and can be used at run time when adding products to opportunities, quotes, orders, or invoices.

References/topics: Product catalog setup; product families; product bundles; product properties; opportunity product configuration.

The required fix is about visibility and security , not agent operating mode. In the scenario, production has EnableRoleBasedSystemViews set to true, which restricts system views based on role configuration. Because the business requirement says all sellers should be able to access disqualified leads , the role-based system view setting must be updated so sellers can access the view that exposes leads disqualified by the Sales Qualification Agent.

The second required action is to change Lead table permissions. The customized Salesperson role currently grants sellers read access only to leads they own. That is too restrictive because leads disqualified by the Sales Qualification Agent may not be owned by each seller. To let all sellers view those records, sellers need organization-level Read permission on the Lead table. Option A is wrong because upgrading the agent to research and engage mode affects how the agent researches and interacts with leads; it does not solve seller access to disqualified records. Option C is also wrong because the look-back period controls which historical leads the agent evaluates, not who can view disqualified leads.

References/topics: Sales Qualification Agent; role-based system views; Dataverse security roles; Lead table read access; AI-driven lead qualification.

Requirement

Configuration

Define measurable sales target

Goal metric

Aggregate opportunity revenue

Rollup column

The correct configuration for defining measurable sales targets is Goal metric . In Dynamics 365 Sales, goals are measured by using goal metrics, which define what is being measured and how performance is calculated. Microsoft’s goal documentation explains that goals help measure progress toward targets such as revenue, while goal metrics and their rollup fields define the values used to calculate performance against those targets.

To aggregate opportunity revenue, use the Rollup column . A goal metric uses rollup fields/columns to calculate actual, in-progress, or custom values. Microsoft specifically describes a money-based goal metric that uses the Opportunity table and the opportunity actual revenue field to track money amounts from opportunities closed as won. This matches the requirement to aggregate opportunity revenue for monthly seller targets. Rollup query is not the best answer because it only adds filtering criteria to an existing goal metric, such as limiting records by owner, territory, or other conditions; it does not define the revenue aggregation itself. Goal hierarchy organizes parent-child goals, and forecasting supports pipeline projections, but neither defines the measurable target calculation or aggregates opportunity revenue for goal achievement.

References/topics: Dynamics 365 Sales goals; goal metrics; rollup columns/fields; opportunity revenue aggregation; seller revenue target tracking.

For Dynamics 365 Sales predictive lead scoring, the model cannot be created unless there is enough historical lead outcome data in the selected training window. Microsoft’s predictive lead scoring configuration requirement states that the organization must have at least 40 qualified leads and 40 disqualified leads in the selected training period. The official guidance specifically explains that if the model is trained with leads from the past three months, the organization needs “at least 40 qualified and 40 disqualified leads” created and closed during that period.

In the sandbox, AdventureWorks has 30 qualified leads and 20 disqualified leads. However, 10 of the qualified leads are older than three months, and the business requirement says predictive scoring must be enabled for leads created within the last three months. Therefore, only 20 qualified leads are usable for this model. The sandbox currently has 20 usable qualified leads and 20 disqualified leads. To meet the required threshold of 40 each, the company needs 20 more qualified leads and 20 more disqualified leads . Simply creating 40 new leads is not enough because predictive scoring requires outcome-classified leads, not merely open or newly created records.

References/topics: Configure predictive lead scoring; lead scoring model training data requirements; AI-driven lead prioritization in Dynamics 365 Sales.

The correct action is Update a single block in the canvas . In Sales Research Agent, the research canvas generates a blueprint that contains research findings, visualizations, and blocks of insight. Microsoft states that users can interact with visualizations through the AI cursor, ask follow-up questions, and then choose whether to update the existing block or generate a new blueprint. If Update block is selected, the existing block is updated with the new information; if Generate new blueprint is selected, the agent creates a new blueprint and adds a journey line.

This distinction matters. The requirement is to update one component , not rebuild the full blueprint. Regenerate the blueprint or Refresh the blueprint would affect the broader blueprint output: Microsoft documents refresh/regenerate as actions for using latest data or producing new visualizations and insights, not for targeted single-block editing. The Dynamics 365 AI Optimization hub is unrelated to editing individual research canvas blocks.

References/topics: Sales Research Agent; research canvas; blueprint blocks; AI cursor; update block; intelligent opportunity research.

Requirement

Automation type

Notify a manager when a high-value opportunity is created

Power Automate automated cloud flow

Validate the products with an external ERP system every Sunday

Power Automate scheduled cloud flow

Display a guided lead qualification interface on the lead form

Business process flow

Update an external ERP system when an opportunity is won

Power Automate automated cloud flow

A Power Automate automated cloud flow is the correct automation type when work must run automatically after a business event occurs. Microsoft describes cloud flows as flows that can perform actions automatically after an event triggers them, such as sending a notification after a triggering event occurs. Therefore, notifying a manager when a high-value opportunity is created and updating an external ERP system when an opportunity is won are both event-driven scenarios, so they should use automated cloud flows with Dataverse triggers.

A Power Automate scheduled cloud flow is correct for validating products with an external ERP system every Sunday. Microsoft states that a scheduled cloud flow runs at a specific time or recurring schedule, such as daily or weekly, and uses a recurrence trigger. That directly matches the weekly Sunday validation requirement.

A Business process flow is correct for displaying a guided lead qualification interface on the lead form. Business process flows provide a streamlined user experience that guides users through defined processes, and Dynamics 365 Sales documentation explains that stages and steps display in a control at the top of a form. Instant cloud flow is not used because none of the requirements ask for a manually triggered user action.

References/topics: Power Automate automated cloud flows; scheduled cloud flows; Dataverse triggers; Business process flows; Dynamics 365 Sales automation and extensibility.