AB-210 Accelerating Sales Pipelines with AI in Dynamics 365 Questions and Answers

The correct configuration is Business process flow . A structured lead qualification process requires sellers to move through defined stages and steps before a lead is converted into an opportunity. Microsoft describes business process flows as a way to guide users through stages of sales, marketing, or service processes toward completion. Business process flows can also include branching logic and defined steps, which makes them the correct mechanism for standardizing how sellers qualify leads before conversion.

The other options do not enforce a structured qualification path. Sales accelerator helps prioritize seller activities and guide daily work, but it is not the core process-control mechanism for lead qualification. Lead activity timeline displays activities, emails, notes, and interactions; it does not define qualification stages. Lead assignment rules route leads to sellers or teams, but they do not structure the seller’s qualification steps. Predictive lead scoring helps prioritize leads by likelihood to qualify, but it does not require sellers to complete a defined qualification process. Therefore, to make sellers follow a controlled lead qualification sequence before converting leads to opportunities, configure a Business process flow .

References/topics: Business process flows; lead qualification; structured sales process; lead-to-opportunity conversion; Dynamics 365 Sales process guidance.

Requirement

Configuration

Open the Pipeline view by default in Opportunities

Configure Opportunity main form

Open a specific form for the opportunity side panel

Set the default Opportunity form

Ability to expand or collapse the grid by sections

Enable aggregation on view controls

Display the average value at the bottom of the grid

Enable aggregation on view controls

To open the Pipeline view by default, configure the Opportunity main form by adding the Pipeline view control for Opportunities. Microsoft states that the read-only grid is the default view for opportunities, but administrators can set the Opportunities pipeline view as the default by customizing the Opportunity table form and adding the Pipeline view component. The configuration includes selecting the Opportunities table, choosing the opportunity view, and enabling grouping and aggregation.

To open a specific form in the opportunity side panel, use Set the default Opportunity form . Microsoft’s configuration guidance states that when sellers open an opportunity from the pipeline view, the side panel displays opportunity details, and administrators can change the default side-panel form to the main opportunity form or a custom form.

For expanding/collapsing by sections such as Owner or Account and displaying average values at the bottom of the grid, enable aggregation/grouping behavior on the Pipeline view control. Microsoft states that Enable grouping and Enable aggregation allow sellers to group and aggregate opportunities in the pipeline view. This supports sectioned grid behavior and aggregate values such as average, sum, or count. The quick create form is irrelevant because it controls record creation, not pipeline display behavior.

References/topics: Opportunity pipeline view; Opportunity main form; side panel default form; grouping and aggregation; pipeline grid configuration.

The correct action is to assign AI capacity to the Dynamics 365 environment . AI agents and AI-powered features run inside a Power Platform/Dynamics 365 environment, and the environment must have available AI capacity or credits before those features can execute reliably. Microsoft’s AI capacity guidance states that once acquired, AI credits can be allocated or assigned to a specific environment, and when an environment has access to the credits, AI features are enabled in that environment. It also states that if consumption exceeds available credits, some features may be blocked.

Option A is wrong because creating a new environment does not automatically provide AI capacity. The existing Dynamics 365 Sales environment can consume AI credits only when capacity is assigned or available to it. Option C is also wrong because Copilot Studio author permissions allow users to design or create agents; that is an authoring permission, not a capacity configuration. Option D is useful after deployment because administrators can monitor consumption in the Power Platform admin center, but monitoring does not make credits available. Microsoft also notes that AI Builder capacity is licensed as an add-on that must be allocated to a Power Platform environment by an administrator.

References/topics: AI capacity allocation; Copilot/AI credits; Power Platform environment capacity; Dynamics 365 Sales AI agents; agent deployment prerequisites.

The three default rule-style suggestions are the Record Owner of the initiating record , the Created By user of the initiating record , and the manager assigned on the seller’s system user record . Suggested contacts in Dynamics 365 Sales Teams chat are intended to help sellers quickly find coworkers who are relevant to the record they are working on. Microsoft states that administrators can enable suggested contacts when a seller starts a new connected chat, and that rules-based contact suggestions can be configured for supported Dynamics 365 record types.

The rule engine supports relational rules: Microsoft explains that a relational rule suggests a user who has a relationship with the linked record type or one of its related records, and administrators can select a user field directly on the record or through related entities. The record owner and created-by user are direct relational users on the initiating record. The seller’s manager is reached through the system user relationship. The business-unit owner is not the default suggestion path for seller collaboration, and “last modified by” or a user who updated a timeline activity are not the default rule answers in this configuration set.

References/topics: Teams chat in Dynamics 365 Sales; suggested contacts; rules-based contact suggestions; relational suggestion rules; sales collaboration.

The correct action is to select a valid price list on the opportunity and verify that the product has a matching price list item for the selected unit. Dynamics 365 Sales calculates Price Per Unit from the price list item when an existing catalog product is added to an opportunity, quote, order, or invoice. Microsoft states that if an existing product is associated with a price list, the price per unit is calculated from the related price list item; otherwise, it is set to 0 .

The failure pattern described in the question is classic missing or mismatched price-list setup. Price calculation will not occur when no price list is selected, when the selected price list does not contain the product, or when the required price list item is missing. Microsoft also notes that price lists tie the product, unit, and pricing details together. Option A is incomplete because matching currency alone does not create the product/unit price list item. Option B is wrong because User Provided revenue bypasses system calculation. Option D handles discounts only; it does not fix a zero base unit price.

References/topics: Opportunity products; price lists; price list items; Price Per Unit calculation; system-calculated opportunity revenue.

The correct conclusion is that lead outcomes reflect updated evaluation criteria applied during processing . The Sales Qualification Agent evaluates inbound leads against the configured target customer profile and qualification settings. Microsoft states that the target customer profile suitability is determined by the attributes defined in the agent configuration’s handoff criteria, and the agent categorizes leads as high, moderate, or low fit based on how well the lead matches those attributes.

Therefore, when the sales manager updates the qualification criteria, a shift in categorization is expected. It means the agent is applying the new criteria to processed leads, not that the old evaluations were incomplete or that external factors are necessarily driving the change. The continued processing and absence of evaluation gaps also indicate normal operational continuity. Microsoft’s Sales Qualification Agent setup guidance explains that the agent works on assigned leads based on configured selection criteria and that stopping the agent prevents new lead processing; here, processing continued, so the agent remained active while using the revised configuration. Option A is too speculative: tuning might be useful later, but the evidence given does not prove a tuning problem. The clean interpretation is D .

References/topics: Sales Qualification Agent; target customer profile; qualification criteria; lead categorization; AI-driven lead qualification monitoring.

The issue is that the sales manager already generated a Sales Research Agent blueprint but forgot to include the quarterly competitive intelligence brief. The brief is an external document and the case study states it is delivered as a PDF document , so the correct first content action is to upload the competitive intelligence brief as a PDF file , not CSV. Microsoft’s Sales Research Agent documentation states that users can select Add data to upload files including CSV, Excel, or PDF to augment research with additional data.

The second required action is to add a data source , because the competitive intelligence brief is not part of the default Dynamics 365 Sales data. Sales Research Agent connects to Dynamics 365 Sales data by default, but additional external files must be added as supporting data sources before they can influence the analysis. The documentation identifies the Data area as the place where the research data source is specified and where additional data sources can be added.

The final action is to regenerate the canvas/blueprint so the agent reprocesses the analysis using the newly added PDF. Refreshing alone is not the best answer because the problem is not stale data; it is missing context. Regeneration creates updated research output with the new source included.

References/topics: Sales Research Agent; research canvas; adding PDF data sources; blueprint regeneration; intelligent opportunity research.

Requirement

Configuration

Blueprints

Name the blueprint workspace and pin the workspace.

Questions

Create a business function with seeded prompts.

For Blueprints, the correct configuration is to name the blueprint workspace and pin the workspace. The requirement is not asking to regenerate analysis; it asks for a reliable way to return to frequently used research output. In Sales Research Agent, a generated blueprint exists inside a workspace, and Microsoft states that the workspace displays the workspace name, can be renamed, and can be switched from the workspace menu. That makes naming and pinning the workspace the correct operational pattern for reusable research access.

For Questions, the correct configuration is to create a business function with seeded prompts. Sales Research Agent business functions are designed to tailor research to a specific use case, and administrators can add starter prompts. Microsoft explains that starter prompts appear on the Sales Research Agent home page for quick access and that the full prompt is sent to the agent when selected. This directly satisfies the requirement to retain a reusable library of approved questions.

Do not select regenerate the blueprint because regeneration refreshes or recreates analysis, but it does not create a persistent shortcut to frequently used research. Do not select custom table or manual prompt questions in Sales Copilot because the native Sales Research Agent feature already supports reusable business-function prompts.

References/topics: Sales Research Agent; research blueprints; workspace management; business functions; seeded/starter prompts; intelligent opportunity research.

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.

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

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.