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

Hotspot Question
You are configuring Microsoft Teams calling for a company. The company uses Dynamics 365 Sales and Microsoft Teams. The Microsoft Teams dialer is enabled with all the prerequisites.
Sellers report the following issues:
- The Microsoft Teams dialer is enabled and the security role is
assigned in the dialer configuration, but sellers in the security role
are not able to access the dialer in Sales Hub.
- Sellers report that their existing third-party telephony system
stopped working in Sales.
- Sellers are able to use the Microsoft Teams dialer in Sales Hub, but
sellers that are using a custom model-driven app are not able to access the dialer.
You need to resolve the issues.
How should you configure the Microsoft Teams dialer setup? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Explanation:
For the first issue, the security role must be associated with the root business unit. Microsoft states that when Teams dialer is enabled for specific security roles, the selected roles must be associated with the root business unit; otherwise, users do not see the Teams dialer in Sales Hub. Merely assigning the role in the dialer configuration is not enough if the role is not rooted correctly.
For the second issue, Teams dialer conflicts with third-party telephony integrations that use Dynamics 365 Channel Integration Framework. Microsoft explicitly notes that when Microsoft Teams dialer is enabled, other telephony systems connected through Channel Integration Framework stop working for users for whom Teams dialer is enabled. Therefore, sellers who must continue using the third-party telephony system should not have Teams dialer enabled.
For the custom model-driven app issue, the dialer must be made available for that app in the dialer configuration. In the Teams dialer advanced options, administrators select the apps where the dialer should be available; Sales Hub is selected by default, so custom apps must be added explicitly.

Case Study 2 - Contoso Ltd
Background
Contoso Ltd. is a global technology distributor headquartered in Redmond, Washington. The company sells networking equipment, cloud infrastructure, and managed services to enterprise customers across North America and Europe.
Contoso Ltd. currently manages its sales operations by using Microsoft Dynamics 365 Sales and plans to enable Sales Insights in the future.
The leadership team wants to modernize the sales organization by introducing capabilities that help sellers prioritize leads, analyze opportunities, and accelerate deal closure.
The company has approximately 150 field sellers, 40 insider sellers, 20 sales managers, and a central IT team responsible for configuring the sales platform. Contoso Ltd.'s executive leadership has defined the following goals for the new sales platform implementation:
Improve seller productivity by reducing manual research and data entry.
Use Al insights to prioritize leads and opportunities.
Provide automated recommendations to sales representatives throughout the deal lifecycle.
Improve collaboration between sellers and sales managers.
Current Environment:
Sales platform
Contoso Ltd. uses Microsoft Dynamics 365 Sales integrated with Microsoft 365 services.
The following components are currently deployed:

Data and lead management
Leads are important for driving new business at Contoso Ltd. They are generated from multiple sources including:
- Marketing automation campaigns
- Website registrations
- Partner referrals
- Trade show contact imports
Marketing teams import lead lists weekly into Dynamics 365 Sales by using spreadsheet imports.
Sellers currently evaluate leads manually.
Sales managers report that this process results in inconsistent prioritization across regions.
Opportunity management
Opportunities are tracked in Dynamics 365 Sales through a defined qualification-to-opportunity lifecycle to ensure accurate reporting.
Sales leadership has requested the Contoso Ltd. IT team to evaluate the following capabilities:
- AI-generated summaries of opportunity records.
- AI-driven research for customer organizations.
- Automated recommendations for closing deals.
Business Requirement:
Contoso Ltd.'s executives have defined the following business requirements:
Lead management
Inside sellers must use a seller engagement workspace that prioritizes leads automatically based on predicted likelihood to convert.
All sellers are guided through a consistent set of qualification steps aligned to Contoso Ltd.'s sales strategy.
Leads cannot be advanced to the development stage until a decision maker has been confirmed.
Sales leadership requires flexibility in how leads are converted. Inside sales need automatic opportunity creation. Field sellers need the option to manually decide whether an opportunity should be created when a lead is qualified.
Lead scoring must be implemented to help sellers identify high potential leads automatically.
Lead scoring must continuously improve based on historical sales outcomes.
Opportunity development
The opportunity flow must be improved by using Al-driven research and automated insights.
Field sellers must be able to access contextual research about customers and competitors while working on opportunities.
Opportunity records must display Al-generated summaries to reduce the time required to review historical activities.
Field sellers must use the Opportunity pipeline view to visualize, prioritize, and manage opportunities.
All opportunity revenue must be calculated using opportunity line items based on selected Contoso Ltd.'s products and standard pricing.
Sales managers must receive an external quarterly competitive intelligence brief to help with their research. This should be delivered as a PDF document.
Sales performance
Sales managers require improved pipeline and revenue forecasting capabilities. The managers need to report on their business performance and use insights, visuals, and recommended next actions.
The new solution must provide the following:
- Allow sales managers to configure forecasts for opportunity pipelines.
- Notify the seller's manager when a draft quote is created and requires approval.
- Allow leadership to track performance against revenue goals.
- Ask questions about Dynamics 365 Sales data to support executive analysis and decision making.
- Support data definitions used at Contoso Ltd. when reporting.
Technical Requirement:
Contoso Ltd.'s IT department defines the following priorities for the sales platform.
AI capabilities
The platform must support the following Al features:
- Lead scoring to guide sellers to priority items.
- Opportunity research insights to prepare deal analysis.
- Copilot-generated summaries of sales records to help with decision making.
- AI-powered research and analytics to aid leadership reporting.
- When performing sales research, sales managers must be able to save their favorite prompts.
Automation
Automation must be implemented to guide sellers through recommended next steps during the sales cycle.
Any approvals must use the Power Automate Approvals connector.
Field sellers use the existing Lead to Opportunity Business Process Flow to manage their leads.
A Power Automate desktop flow is used to process orders into a partner ordering application that completes fulfillment.
Collaboration
All sellers must be able to collaborate by using Teams and store related sales documents in SharePoint.
AI-driven insights
The company is deploying the Sales accelerator to guide seller activities.
The Sales Research Agent
Sales managers will use the Sales Research Agent to gather intelligence about customer organizations.
The sales managers have the following requirements:
- Must be able to reuse visualizations after they are created; they don't want to recreate them.
- Must have a consistent method to quickly return to a blueprint that they frequently use.
- Must be able to retain a library of questions to receive consistent responses based on definitions approved by the company.
- Should have Bing search enabled on the environment for generative Al feature settings.
Platform extensions
The IT department plan to extend the platform by doing the following:
- Create Power Automate flows to automate seller tasks.
- Embed Power Apps components inside model-driven forms.
- Embed Power BI reports for sales analytics.
Testing
The IT department is testing predictive lead scoring with a small group of sellers.
The IT department edits the existing lead scoring model by adding new fields.
Issues:
Users have reported the following issues:
- Field sellers spend a significant amount of time researching customers before engaging with prospects.
- Sales managers cannot easily identify the most promising opportunities across regions.
- Lead prioritization varies significantly between sales teams.
- Testers report they cannot access the field changes in the lead score.
- A sales manager generated a blueprint but forgot the competitive intelligence brief.
Hotspot Question
You need to configure AI-powered research capabilities for the sales team.
What should you configure? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all.

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

Drag and Drop Question
You are responsible for improving lead prioritization in Dynamics 365 Sales.
Sales managers report that predictive scores do not match current conversion trends.
You need to edit the predictive lead scoring model to improve accuracy based on recent lead data.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Explanation:
The correct sequence starts by opening and configuring the predictive scoring settings for lead scoring. The administrator must access the predictive lead scoring configuration page before changing the model. Microsoft's predictive scoring configuration guidance states that the Predictive lead scoring page is where administrators configure model settings, including model criteria and field behavior.
Next, the administrator should edit model attributes. This is the actual model-tuning step.
Microsoft states that Edit model is used to update or add fields that affect the prediction accuracy score, especially when the organization wants the model to consider different fields or a unique business process.
After modifying the attributes, the model must be retrained. Retraining is required when prediction accuracy does not meet expectations or when recent data should be incorporated. Microsoft explains that retraining uses the latest leads in the organization so the model can provide more accurate scores.
Finally, the administrator must verify predictive score accuracy by reviewing the model accuracy and performance. Exporting all lead records is unnecessary, and editing health score grading applies to opportunity health scoring, not predictive lead scoring.

A company uses the Sales Close Agent in Dynamics 365 Sales to help sellers close deals.
The sales managers want to ensure the agent is used only in specific scenarios.
You need to identify the behavior of the Sales Close Agent.
What should you use to review the agent's behavior?

• A. Open the underlying opportunities from the Forecast section to access the agent's My top opportunities from the AI agent list.
• B. Configure the opportunity pipeline view under App settings to display the agent's See full research page in the side panel for every opportunity.
• C. Open a researched opportunity and choose See full research to open the Opportunity research page with complete agent insights and recommendations.
• D. Open the Sales agent runs table to review the opportunity research results and recommendations for the Sales Close Agent in Research mode.

Explanation: Only visible for VCETorrent members. You can sign-up / login (it's free).

A sales executive wants to measure whether Copilot adoption actually improves seller productivity over time. Which metric would provide the strongest evidence?

• A. Number of CRM security roles created
• B. Reduction in preparation time while maintaining sales quality
• C. Total database storage consumed
• D. Number of duplicate contacts removed

Explanation: Only visible for VCETorrent members. You can sign-up / login (it's free).