Configuring Dataverse Business Terms for Copilot

AB-100 By islever Editorial Last updated

Design AI and agents for business solutions

Short answer

B Map the field display names as business terms to align Copilot with existing non-standard terminology while minimizing administrative effort.

Question

A company uses Microsoft Dynamics 365 Sales to manage leads that are stored in a Microsoft Dataverse table named Lead and use non-standard terminology and custom columns.
You need to configure business terms in the Lead table so that Microsoft Copilot controls can summarize the leads efficiently. The solution must minimize administrative effort.
How should you configure the business terms?
  1. Combine all the fields into one custom field.
  2. Map the field display names as business terms. Correct Answer
  3. Add the schema names as business terms.
  4. Create new business terms for each field.

Key Takeaways

This question tests the method for configuring Copilot business terms in Dataverse, where the main trap is choosing schema names or creating new terms instead of leveraging existing display names.

Configure Microsoft Copilot controls in Dataverse by mapping field display names as business terms to ensure efficient lead summarization with minimal administrative effort.

Common mistake: Choosing option D (Create new business terms) or C (Add schema names) because of a misunderstanding of how Copilot consumes metadata; schema names are technical, and creating new terms violates the minimal effort constraint.

Expert Analysis

Copilot Business Language Requirement Microsoft Copilot for Dynamics 365 relies on business terms to understand and summarize data semantically. It does not interpret technical schema names; it requires mappings to the language that users speak within the organization.

Minimizing Administrative Effort The scenario specifies that the Lead table already uses non-standard terminology and custom columns, which means the display names of these fields have already been configured to reflect the desired business language. Option B, mapping the field display names as business terms, leverages this existing configuration. This requires no additional manual entry, satisfying the constraint to minimize administrative effort.

Evaluating Incorrect Options Option C is incorrect because schema names are technical (e.g., new_customfield) and meaningless to Copilot's natural language processing. Option D is incorrect because creating entirely new business terms for each field duplicates work already done in setting display names, violating the minimal effort constraint. Option A is structurally destructive and irrelevant to configuring business terms for Copilot summarization. Option B is the only approach that correctly bridges the technical-to-business semantic gap with zero redundant administration.

Official Reference

https://learn.microsoft.com/en-us/training/modules/design-ai-agents-business-solutions/3-design-business-terms-copilot-dynamics-365-apps-customer-experience-service

This link opens the official vendor documentation in a new tab.

Exam Strategy

When a question asks to minimize administrative effort while configuring AI or Copilot semantics, always look for the option that reuses existing metadata (like display names or labels) rather than creating new objects or relying on technical schema names. AI features consume business language, so leverage the business-facing configurations already present in the system.

Community Votes

B
80%
D
20%

80% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 5 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 5

  1. Newb007 👍 6 Answered B
    B. Map the field display names as business terms.
  2. omath 👍 5 Answered B
    Correct answer: B. Map the field display names as business terms. Takeaway: To let Microsoft Copilot summarize leads effectively with the least administrative effort, you should map the existing display names of the Lead table’s fields to business terms. This avoids creating new terms manually and aligns Copilot with the terminology already used in Dynamics 365 Sales.
  3. KathCha 👍 1 Answered B
    Why B is correct Microsoft Copilot controls reason in business language, not technical schema language. In Dataverse, field display names already reflect business terminology, even when: Non‑standard terms are used Custom columns exist Mapping display names → business terms: Requires minimal administrative effort Preserves existing semantics Improves Copilot’s ability to summarize leads accurately Avoids duplication and maintenance overhead
  4. Sathish_PP 👍 1 Answered D
    https://learn.microsoft.com/en-us/training/modules/design-ai-agents-business-solutions/3-design-business-terms-copilot-dynamics-365-apps-customer-experience-service
  5. maxblack2099 👍 1 Answered B
    orrect answer: B. Map the field display names as business ter

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How Microsoft 365 Copilot invokes Azure-hosted logic

S-grade

Customizing Microsoft Copilot Opportunity Summary Presentation

S-grade

Prerequisites for Prebuilt Copilot in Dynamics 365 Finance

S-grade

Dynamics 365 Copilot Studio Knowledge Sources for In-App Help

S-grade

← Back to AB-100 Study Guide