Exercise - Select a harness for a business scenario
In this exercise, you apply harness-selection criteria to three independent business requirements. No Copilot Studio environment is required.
Scenario 1: Contract review
A legal operations team needs an agent that receives contract files, extracts key terms, compares them with an approved playbook, checks customer records, and routes exceptions to a lawyer. The sequence can change based on the contract and tool results.
Recommended harness: Microsoft Copilot harness.
The solution performs file-intensive, reasoning-heavy work across several tools. It must adapt its plan to intermediate results and route exceptions. Those requirements align with the Microsoft Copilot harness.
Scenario 2: Equipment return
An IT team needs to extend an existing standard-harness equipment-return agent. It must retain approved topics and agent flows that collect an asset number, validate the employee's location, present shipping options, and branch for damaged and undamaged devices. The team wants to reuse that implementation rather than rebuild it.
Recommended harness: Standard harness.
The requirement to retain the existing standard-harness topics and agent flows makes the standard harness the appropriate choice. Customer Conversation also supports deterministic Topic skills, so fixed questions and branches alone don't distinguish the two. Existing implementation, required channels, and lifecycle requirements matter too.
Scenario 3: Customer order support
A retailer needs an agent that answers order questions through website chat and phone calls. Delivery and returns require different specialist behaviors. If the agent can't resolve an issue, it must transfer the conversation to a human representative through the appropriate escalation path.
Recommended harness: Customer Conversation harness.
The primary requirement is customer service over voice and chat, with specialist sub-agents and defined human escalation. Those requirements align with the Customer Conversation harness. Individual parts of the conversation can still use deterministic Topic skills when they need fixed steps.
Review the decisions
The scenarios use different harnesses because they require different operating models:
- Contract review prioritizes dynamic planning, file operations, and multitool reasoning.
- Equipment return prioritizes reuse of existing standard-harness topics and agent flows.
- Customer order support prioritizes voice and chat conversations, specialist sub-agents, and human escalation.
When requirements include elements from more than one scenario, identify the dominant job and required control model. A solution can also combine agents and workflows, but each agent still runs on one selected harness.