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.
Topic 1, AdventureWorks Case StudyBackgroundAdventureWorks
Cycles is a global manufacturer of high-performance bicycles
headquartered in Seattle. The company sells products through
distributors, specialty retailers, and a growing direct-to-consumer online channel. AdventureWorks Cycles recently expanded its product catalog to include the athlete package. This package includes a cycle, connected devices and subscription-based analytics services.
To support this expansion, the company wants to modernize its sales operations by implementing Microsoft Dynamics 365 Sales. The leadership team wants sellers to focus on building relationships with distributors and enterprise buyers rather than manually qualifying leads or assembling product packages.
The sales operations team is responsible for configuring the Dynamics 365 Sales environment. Their goal is to implement Al-driven processes that streamline the lead-to-cash workflow while ensuring that sellers can easily identify the most promising opportunities.
Current Environment AdventureWorks Cycles previously used a legacy CRM system that tracked leads and opportunities but lacked predictive intelligence or automated lead qualification. Sellers manually evaluate incoming leads, which creates delays and inconsistent prioritization.
The global sales team manages approximately 15,000 leads per month generated from marketing campaigns, trade shows, and partner referrals.
Product data is stored in multiple systems. Product managers maintain products and pricing in spreadsheets.
Information regarding custom
relationships, competitor analysis, and region-specific marketing content is stored in a SharePoint site called the sales portfolio.
The organization has identified several challenges they want to resolve with a new solution:
* Sellers often spend significant time researching leads that ultimately do not convert.
* Regional managers require in-depth reporting using information from the sales pipeline and seller activities, the point-of-sale solution, website analytics, and the accounting system.
* Multiple product offerings are difficult to manage because components are defined in different systems.
* Team leads require real-time information on active opportunities, as well as visibility of seller ' s appointments and phone calls, without needing to navigate into multiple views.
All sellers are assigned Dynamics 365 Sales Enterprise licenses, Also, the CFO has requested that Copilot message packs are pre-purchased by using the Copilot Studio subscription license.
A Dynamics 365 sales sandbox environment has been in use for six months. There are 60 leads records with
30 records that are qualified and 20 that are disqualified. Ten of the qualified leads are over three months old.
Business Requirements: AdventureWorks Cycles has defined the following business requirements for the production environment of Dynamics 365 Sales:
Sellers in all regions should be able to review the new mountaineer cycles. The cycles include economy and premium fittings. When creating opportunities, sellers should be able to select a metal type when adding a mountaineer cycle to an opportunity. The metal types include chrome, aluminum, and titanium.
* Pricing managers must be able to create deals for the same products in their own currencies and at their own prices, without reference to the cost of the product.
* Sellers must be able to quickly view their own opportunities by phase.
* Predictive scoring should be enabled for leads created within the last three months in the sandbox environment. This should provide seller training on the scoring ' s interpretation and usage.
* A segment of leads named Hot is needed that will contain all leads where the source is phone, employee referral or partner. Leads from this segment should be distributed to sellers by using a round robin method.
* Agents should not be able to take action on any data that is created in the production environment before they are started.
* All sellers should be able to access disqualified leads.
Technical Information and Requirements: The new Dynamics 365 Sales environment must meet the following technical requirements:
Agents must use a dedicated service identity to execute write actions with a controlled security role in Dataverse.
The sales operations team lead must be assigned the Power Platform administrator role.
The lead pricing manager must be assigned to the Microsoft 365 billing admin role.
The vice president of sales must be assigned the Al admin role.
* A sandbox and a production environment must be created. Both of the environments must be enabled for Al capacity, but usage should be capped on the sandbox environment.
* A trial environment must be created, with the Sales Qualification Agent configured to business requirements.
* Sellers must be assigned the security roles on the production environment only.
* All sellers must be assigned a customized version of the salesperson role. This role should grant read access only to the leads that the sellers own.
* The EnableRoleBasedSystemViews property must be set to true for the production environment.
No Azure subscriptions are available in the tenant.
Issues: During early testing, the sales operations team identify the following issues:
* The Sales Qualification Agent has disqualified several leads in the trial environment. The vice president of sales has requested to understand the reason for the disqualified leads.
* Sellers are unable to create agents in the production environment.
* Agent consumption has been unreliable. The company requires that Al capacity is always available to sellers.

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.

The correct configuration is to enable the Microsoft Teams dialer. Microsoft's Dynamics 365 Sales documentation states that Microsoft Teams dialer brings Teams calling directly into Dynamics 365 Sales so sellers can make and receive calls without leaving the application. The documented setup path is to go to Sales Hub app settings, open Teams calls, and turn on Teams calls for the selected security roles and apps.
This matches the requirement precisely: the sales team must place outbound calls directly from Dynamics 365 Sales records using Microsoft Teams. Phone numbers and PSTN connectivity are prerequisites for Teams calling, but option A is not the Dynamics 365 Sales feature that enables record-level calling. The mobile app is irrelevant because the question asks for calling from Dynamics 365 Sales records, not mobile access. Teams meeting integration supports meetings and collaboration, but it does not enable click-to-call or Teams dialer calling from Sales records.
Therefore, the required feature is Microsoft Teams dialer.

Explanation:
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.

The correct agent type is Sales Qualification Agent: Research and engage . The requirement is specifically about inbound lead processing: researching incoming leads, generating outreach, autonomously contacting leads, following up, and evaluating qualification during the engagement process. Microsoft defines Sales Qualification Agent as the AI agent used to automate lead qualification in Dynamics 365 Sales, especially for high-volume inbound leads from sources such as websites, events, and webinars. In Research and engage mode, the agent researches the lead, evaluates fit using target customer profile and BANT criteria, sends personalized outreach emails, engages based on responses, sends follow-up emails, detects positive intent, and then hands promising leads to sellers.
Research-only mode is not enough because it generates a draft outreach email for seller review but does not send outreach emails or detect positive intent from responses. Microsoft's mode comparison explicitly shows that BANT checking, sending outreach, detecting positive intent, and follow-up emails are available in Research and engage mode, not Research-only mode. Sales Close Agent options are wrong because they apply to opportunity/deal execution, not initial lead qualification.
References/topics: Sales Qualification Agent; Research and engage mode; lead research; outreach automation; BANT qualification; AI-driven lead prioritization.