Our experience from building agents in Copilot Studio: generative AI pays off where language has to be understood or written. A simple data query runs more efficiently through a connector such as the Dataverse connector, and a change to data through an explicit, validated action. Copilot Studio supports both in the same agent; the work lies in choosing the right route for each action.
The guiding question
The most important question when designing an agent is not ‘How much AI is possible?’ but ‘What must happen reliably in this task?’ An open question benefits from a generative answer. A query, a booking or a data change needs clearly defined inputs and controls.
Which mechanism for which task
| Task | Example | Mechanism |
|---|---|---|
| Knowledge question | ‘What is the travel expense rule?’ | Generative answer from approved sources, with citation |
| Understanding or writing text | Drafting a reply to a customer, summarising a document | Generative AI |
| Querying data | Retrieving a list of records from Dataverse | Dataverse connector with a fixed query |
| Changing data | Changing a customer address, approving a payment | Explicit action with validation, permission check and confirmation |
Why a data query does not need AI

Retrieving a list of data: no AI needed.
For simple queries, the Dataverse connector is the more efficient choice:
- 1Accuracy: generative AI produces probabilistic results. The connector returns exactly the data requested, without that variability.
- 2Cost: running AI models can be expensive. For routine access, the connector is the cheaper option.
- 3Speed: connectors are designed for fast data queries; generative AI takes longer.
- 4Energy: generative models are compute-intensive. For a simple query, that effort is unnecessary.
When data is changed
When someone changes a customer address or approves a payment, the agent captures identity and inputs, validates the values, checks authorisation and asks for confirmation where needed. Only then may an action write to Dataverse or another system. Free-form text does not replace these rules.
A simple design test
- 1Write down the expected outcome for three typical and two difficult cases.
- 2Mark every point where the state of a system changes.
- 3For knowledge questions, use limited sources and citations.
- 4For changes, use explicit actions with validation, permission checks and an error path.
- 5Test the cases in the agent and record where people have to step in.
Limits of generative answers
With generative answers, test whether outdated sources are excluded and whether the agent admits when it does not know something. Microsoft describes the capabilities and limits of generative answers, and its Copilot Studio guidance on topics explains how topics, tools and knowledge sources are orchestrated. Whether a step runs generatively or on a guided path depends on the risk of the individual task, not on the label ‘agent’.

