ExamFinch.com My Study

Study guide

5.3 Configuring an Agent That Has Knowledge

Practice this exam

Microsoft AI Business Professional AB-730

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

0.1 About the AB-730 Exam 0.2 How to Use This Study Guide

2 Chapter 1: Understand Generative AI Capabilities Across Microsoft 365

1.1 How Copilot Works: LLMs, Microsoft Graph & the Security Boundary 1.2 Context & Grounding: Work Files, Web Data and App Context 1.3 Chat Experiences vs. Agent Experiences 1.4 When to Create Your Own Agent 1.5 Copilot Capabilities Across Microsoft 365 Apps

3 Chapter 2: Responsible AI & Data Protection Practices

2.1 Generative AI Risks: Fabrications, Prompt Injection & Over-Reliance 2.2 Verification Steps: Citation Checks & Human Review 2.3 Recognizing & Mitigating Risks to Sensitive Data 2.4 How Data Protection Restricts Prompt Results

4 Chapter 3: Creating and Managing Prompts

3.1 Creating an Effective Prompt: The GCSE Framework 3.2 Selecting Resources to Reference in a Prompt 3.3 Saving and Sharing Prompts in Copilot Prompt Gallery 3.4 Scheduling Prompts

5 Chapter 4: Managing Conversations and Notebooks

4.1 Finding Previous Conversations 4.2 Renaming and Deleting Chats 4.3 Adding a Conversation to a Copilot Notebook

6 Chapter 5: Creating and Managing Microsoft 365 Copilot Agents

5.1 Agent Store vs. Creating a New Agent 5.2 Creating an Agent from a Template 5.3 Configuring an Agent That Has Knowledge 5.4 Configuring Instructions, Capabilities & Suggested Prompts 5.5 Sharing an Agent with Team Members

7 Chapter 6: Drafting and Analyzing Business Content

6.1 Creating a New Document from a Prompt 6.2 Generating a Document from an Existing Document 6.3 Generating a Management Summary 6.4 Moving Data & Insights Between Microsoft 365 Apps 6.5 Drafting Communications with Copilot in Outlook

8 Chapter 7: Meetings, Collaboration and Personalization

7.1 Using Copilot for Meetings: Setup & Live Intelligence 7.2 Meeting Recap, Transcripts & Catch-Up 7.3 Copilot Pages for Collaboration 7.4 How Copilot Uses Memory & Instructions

5.3 Configuring an Agent That Has Knowledge

Key Takeaways Explain This Topic AI

Scoping agent knowledge restricts retrieval to designated SharePoint document libraries, specific file URLs, OneDrive folders, and authorized public websites, eliminating irrelevant enterprise noise.

System instructions serve as the agent's persistent metaprompt, defining its operational persona, professional tone, output structural schemas, and mandatory compliance boundaries.

Negative constraints in system instructions are vital for preventing hallucinations, strictly prohibiting the agent from answering out-of-scope inquiries, giving unauthorized advice, or fabricating ungrounded data.

Agent capabilities—including Web Search via Bing, Image Generation, and Code Interpreter—can be toggled individually to align with organizational security and operational needs.

Well-crafted conversation starters (starter prompts) guide end users toward high-value, supported workflows, eliminating the blank page problem and showcasing the agent's core capabilities.

Last updated: August 2026

5.3 Configuring an Agent That Has Knowledge

Quick Answer: Configuring a high-performing declarative Copilot Agent requires four core components: (1) Scoped Knowledge , which bounds data retrieval to explicit SharePoint document libraries, OneDrive folders, specific file URLs, or public websites rather than open tenant searches; (2) System Instructions (Metaprompt) , which define persona, tone, output schemas, and strict negative constraints; (3) Capability Toggles , which enable or disable Web Search (Bing), Image Generation (Designer), and Code Interpreter (Python sandbox) based on security and task requirements; and (4) Suggested Conversation Starters , which provide structured, one-click prompts that orient users and demonstrate the agent's capabilities.

While foundation Large Language Models possess remarkable linguistic fluency, their performance in specialized enterprise environments depends entirely on configuration precision. An unconfigured or vaguely guided agent risks hallucinating policies, referencing outdated organizational drafts, adopting an inappropriate tone, or drifting into out-of-scope discussions. Mastering the configuration pillars of declarative agents is a primary objective of the AB-730 certification.

1. Scoping Agent Knowledge: Repositories and Grounding Mechanics

In standard Copilot Chat, retrieval queries the entire Microsoft Graph accessible to the user. For a specialized agent, this broad retrieval can introduce noise—such as surfacing preliminary drafts, personal notes, or obsolete historical policies. Knowledge Scoping explicitly restricts the agent's Retrieval-Augmented Generation (RAG) pipeline to curated, authoritative data repositories. +-------------------------------------------------------------------------+

  • | AGENT KNOWLEDGE SCOPING TIERS |
  • +-------------------------------------------------------------------------+
  • | [1. SHAREPOINT SITES & LIBRARIES] |
  • | • Point to full site collections, subsites, or specific libraries. |
  • | • Example: https://contoso.sharepoint.com/sites/HR/Policies/ |
  • | • Auto-indexes supported Office files (.docx, .pptx, .xlsx, .pdf). |
  • | |
  • | [2. SPECIFIC FILE ATTACHMENTS] |
  • | • Pin explicit authoritative master documents. |
  • | • Example: /Employee_Handbook_2026.pdf, /Travel_Matrix_v4.xlsx |
  • | |
  • | [3. ONEDRIVE FOR BUSINESS FOLDERS] |
  • | • Attach curated personal or department-shared cloud folders. |
  • | |
  • | [4. AUTHORIZED PUBLIC WEBSITES] |
  • | • Index external public domains, subpaths, or documentation hubs. |
  • | • Example: https://learn.microsoft.com/en-us/microsoft-365-copilot/ |
  • +-------------------------------------------------------------------------+
  • Supported Knowledge Sources and Ingestion Mechanics

Declarative agents support multiple distinct knowledge source types:

SharePoint Document Libraries & Sites: Creators can attach entire SharePoint site URLs or target specific document libraries. The agent automatically leverages the Semantic Index to vectorize and index supported file formats ( .docx , .pptx , .xlsx , .pdf , .txt , .rtf ). When files within the document library are modified or added, the changes are automatically reflected in the agent's grounding context through Microsoft Graph synchronization.

Specific File URLs: For razor-sharp precision, creators can specify individual file URLs. This guarantees that the agent grounds its responses exclusively on certified master assets (such as an approved corporate standard operating procedure or an annual pricing matrix).

OneDrive for Business Folders: Useful for team-level or personal agents where project files reside in a shared cloud folder.

Public Web Domains & URLs: Creators can ground agents in authoritative external documentation by adding specific public URLs or full web domains (e.g., regulatory compliance portals or vendor product manuals). The system crawls and indexes public text while respecting standard web robots protocols.

Knowledge Source Comparison Matrix

Knowledge Source Type Grounding Scope Synchronization Behavior Primary Enterprise Use Case

SharePoint Document Library Multi-document repository within a team or departmental site Dynamic: reflects updates and newly added files via Graph indexing Departmental policy hubs, standard operating procedures, HR handbooks

Specific File URLs Single explicit file ( .pdf , .docx , .xlsx ) Immediate: points directly to the active cloud master version Authoritative reference guides, executive charters, legal disclaimers

OneDrive Folder Cloud folder owned by an individual or shared team Dynamic: synchronizes with cloud edits Project-specific working groups, ad-hoc team initiatives

Public Web URLs Public website domains or specific sub-paths Periodic web crawling of publicly accessible HTML/text Regulatory standards, industry certifications, vendor documentation

  • 2. Realistic Business Scenario: Configuring a Global Financial Compliance Agent
  • Background

Woodgrove Bank requires an internal agent to assist commercial loan officers in verifying compliance with the bank's 2026 Commercial Lending Credit Policy and analyzing borrower debt-service coverage ratios (DSCR).

Configuration Architecture

Knowledge Scoping:

  • SharePoint Document Library: https://woodgrove.sharepoint.com/sites/CreditRisk/Policy2026/
  • Specific Master File: /Master_Loan_Underwriting_Matrix.xlsx

System Instructions (Metaprompt):

Persona: Senior Commercial Underwriting Auditor.

Tone: Highly formal, analytical, and risk-averse.

Formatting Schema: Deliver loan evaluations with (1) Executive Decision [Compliant / Non-Compliant], (2) Financial Ratios Table, (3) Risk Factor Justification citing exact policy sections.

Negative Constraints: "Do not approve any loan application with a DSCR below 1.25x without explicit written waiver from the Chief Risk Officer. If borrower financial data is missing from the prompt or attached workbook, do not assume baseline figures; output 'Incomplete Borrower Data' and list the missing metrics."

Capability Configuration:

Web Search: Disabled (to protect non-public financial deliberations and prevent external market chatter from influencing risk audits).

Image Generation: Disabled .

Code Interpreter: Enabled (essential for running exact Python scripts to calculate loan amortization, debt yields, and DSCR formulas).

Conversation Starters:

  • "Calculate the Debt-Service Coverage Ratio (DSCR) for an attached borrower income statement."
  • "Check minimum collateral requirements for commercial real estate loans over $5M."
  • "Generate a pre-underwriting compliance checklist for industrial equipment financing."

Exam Warning: Pay close attention to scenario questions involving numeric accuracy or data analysis in Excel. If a question asks how to guarantee mathematical precision and prevent calculation hallucinations in a declarative agent, the answer is to enable Code Interpreter .

Exam Tip: Remember that negative constraints are not suggestions; they are rigid behavioral guardrails embedded into the system metaprompt that instruct the model to refuse out-of-scope requests and avoid speculating when knowledge sources lack data.