Skills Pragati
YouTube

AB-410 Step by step · Lab 10

Build a Copilot Studio Agent That Only Uses Your Data

Create the Claims Assistant in Copilot Studio: plain instructions, no web search, and the Dataverse MCP server so it answers only from your data.

· 4 min read

Copilot Studio Claims Assistant with the Microsoft Dataverse MCP server listed under Tools
Watch the lesson: Lab 10: Claims Assistant, a Copilot Studio agent | Building Intelligent Applications | AB-410

Surveyors at Pragati General Insurance ask the same questions all day: what is the amount of this claim, who handles it, which documents are missing? The answers are already in Dataverse. An agent can answer them, as long as it answers only from our data.

This is Lab 10 of the AB-410 course: the Claims Assistant in Copilot Studio.

The plan

  • Create the agent, grounded on the app’s data.
  • Its knowledge: Dataverse tables, not the public web.
  • Publish it into the app, Teams or a website.
  • Agent messages use Copilot Studio capacity, so check it before you go live.

Step 1: Name it and write the instructions

In Copilot Studio, in the Pragati Claims environment, create an Agent named Claims Assistant. The instructions are plain words: who it helps, which data it uses, and what it must never do.

Claims Assistant instructions: help claims handlers and surveyors, answer from the Claims table, never change data
Instructions: answer questions about motor claims from the Claims table, say so if a claim is not found, never change data.

The agent’s knowledge starts with Search all websites. Remove it: the answers must come from our data only.

Copilot Studio knowledge section after removing Search all websites
No web search: an insurance agent should not improvise from the internet.

Step 3: Connect Dataverse through MCP

Add tool, search Dataverse, choose MCP. The Microsoft Dataverse MCP server lets the agent find tables and query rows in this environment, with the user’s own permissions.

Tools section with Microsoft Dataverse MCP Server added
The Dataverse MCP server: the agent queries real rows, and sees only what the user may see.
Claims Assistant saved with the Dataverse MCP server under Tools
Tools now lists the Dataverse MCP server. Save.

Step 4: Test, and meet the capacity question

In Preview, ask: what is the amount and handler of claim CLM0006?

Preview message: you need credits to continue, the environment is out of credits
"You need credits to continue." Running an agent uses Copilot Studio credits, and this developer environment has none.

Buying capacity is a billing decision for the admin, so we stop here, honestly, rather than show a fake answer. With credits, the agent would query the Claims table through the MCP server and answer with the amount and the handler.

What a tech lead should take away

  • Ground agents on your own data and remove web search when the answers must be authoritative.
  • MCP plus user permissions means the agent cannot show what the user could not open.
  • Plan capacity before go-live. Agent messages are metered; agree who pays before users depend on it.

Do it yourself

Lab guides, practice and full mock exams come with a subscription. See the plans

More on AB-410