This post is a part of the AB-620: Designing and Building Integrated AI Agent Solutions in Copilot Studio Exam Prep Hub.
This topic falls under these sections:
Plan and configure agent solutions (30–35%)
--> Create and monitor agent flows in Copilot Studio
--> Create a human-in-the-loop agent flow
Note that there are 10 practice questions (with answers) at the end of each section to help you solidify your knowledge of the material. Also, there are 4 practice tests with 30 questions each available from the hub's main page below the exam topics section.
Introduction
While AI agents can automate many business processes, not every task should be completed autonomously. Many enterprise workflows require human judgment, approval, verification, or intervention before an action is completed. This design pattern is known as Human-in-the-Loop (HITL).
In Microsoft Copilot Studio, a human-in-the-loop agent flow combines AI-driven automation with human decision-making. The AI agent performs repetitive, deterministic, or data-intensive tasks, while a human reviews, approves, rejects, or modifies actions that require discretion or accountability.
Human-in-the-loop workflows are especially important in regulated industries, high-value transactions, legal processes, healthcare, finance, and any scenario where AI recommendations should be reviewed before execution.
For the AB-620 exam, you should understand when to use human-in-the-loop workflows, how to design them, how they integrate with Power Automate and enterprise systems, and how they support Responsible AI and governance.
What Is Human-in-the-Loop?
Human-in-the-loop (HITL) is a workflow pattern in which an AI agent collaborates with one or more human users to complete a business process.
Instead of allowing the AI to make every decision independently, the workflow pauses when human judgment is required.
Typical process:
- User submits a request.
- AI gathers information.
- AI performs automated tasks.
- AI requests human review or approval.
- Human approves, rejects, or modifies the request.
- AI completes the remaining workflow.
Why Human-in-the-Loop Is Important
Human review provides additional oversight for actions that may have financial, legal, ethical, or operational consequences.
Benefits include:
- Improved accuracy
- Better decision-making
- Regulatory compliance
- Reduced business risk
- Increased accountability
- Human oversight of AI recommendations
- Better customer outcomes
- Support for Responsible AI principles
Common Human-in-the-Loop Scenarios
Examples include:
- Expense approvals
- Vacation requests
- Purchase requests
- Contract approvals
- Loan applications
- Insurance claims
- Medical referrals
- Employee onboarding approvals
- High-value refund requests
- Customer complaint escalations
In each scenario, AI assists the process while humans retain final authority.
Human-in-the-Loop vs Fully Automated Flows
| Fully Automated Flow | Human-in-the-Loop Flow |
|---|---|
| No human intervention | Human review required |
| Best for routine tasks | Best for judgment-based tasks |
| Faster execution | Greater oversight |
| Lower operational cost | Higher confidence |
| Suitable for deterministic processes | Suitable for exceptions and sensitive decisions |
Components of a Human-in-the-Loop Flow
A typical workflow includes several stages.
1. User Request
The user initiates the process.
Examples:
- Submit expense report
- Request refund
- Approve invoice
- Create purchase request
2. Data Collection
The agent gathers all required information.
Examples:
- Employee ID
- Customer account
- Purchase amount
- Supporting documents
- Business justification
The AI validates the information before proceeding.
3. Automated Processing
The agent performs automated work such as:
- Looking up records
- Checking policies
- Calculating totals
- Retrieving customer information
- Validating eligibility
- Calling enterprise APIs
Automation reduces manual effort before human review.
4. Decision Point
At a predefined point, the workflow determines whether human review is necessary.
Conditions may include:
- Amount exceeds approval limit
- Sensitive customer information
- Regulatory requirement
- Confidence score below threshold
- Exception detected
- Policy violation
- Missing information
If no review is required, automation may continue.
5. Human Review
A human reviewer receives the request.
Common reviewers include:
- Manager
- Supervisor
- HR representative
- Finance approver
- Compliance officer
- Customer support specialist
The reviewer evaluates the request.
6. Human Decision
Possible outcomes include:
- Approve
- Reject
- Request additional information
- Modify request
- Escalate
The workflow resumes after the decision.
7. Completion
The agent completes the remaining tasks.
Examples:
- Update database
- Notify user
- Create record
- Send confirmation email
- Archive documents
Approval Workflows
One of the most common human-in-the-loop scenarios is approval processing.
Examples:
- Expense approval
- Purchase approval
- Leave approval
- Document approval
- Contract approval
Power Automate provides built-in approval capabilities that integrate well with Copilot Studio.
Power Automate Integration
Many human-in-the-loop workflows delegate approval logic to Power Automate.
Typical process:
Copilot Studio
↓
Power Automate
↓
Approval
↓
Manager decision
↓
Return result to agent
Power Automate simplifies:
- Approval routing
- Notifications
- Escalations
- Timeouts
- Audit history
Notifications
Human reviewers must be informed when action is required.
Notifications may be sent through:
- Microsoft Teams
- Outlook email
- Mobile notifications
- Power Automate
- Business applications
Prompt notification reduces workflow delays.
Handling Timeouts
Human reviewers may not respond immediately.
Possible timeout strategies include:
- Send reminder
- Escalate to another approver
- Cancel request
- Auto-close request
- Retry notification
Timeout planning improves workflow reliability.
Escalation
Organizations often define escalation rules.
Examples:
- Manager unavailable
- Approval exceeds time limit
- High-priority request
- Compliance review required
Escalations ensure requests continue moving through the process.
Exception Handling
Human-in-the-loop workflows should anticipate exceptions.
Examples:
- Missing documents
- Invalid requests
- Authentication failures
- API errors
- Approval system unavailable
- Reviewer unavailable
Graceful exception handling improves reliability.
Responsible AI Considerations
Human oversight is an important Responsible AI practice.
Humans should review:
- High-impact recommendations
- Financial decisions
- Medical information
- Legal recommendations
- Employment decisions
- Sensitive customer interactions
AI assists—not replaces—human judgment in these scenarios.
Security Considerations
Human-in-the-loop workflows often involve sensitive data.
Security planning should include:
- Microsoft Entra ID authentication
- Role-Based Access Control (RBAC)
- Least privilege
- Secure approval routing
- Audit logging
- Data Loss Prevention (DLP)
- Secure connectors
Only authorized reviewers should approve requests.
Audit Logging
Approval workflows should maintain complete audit trails.
Logs may include:
- Requestor
- Approver
- Timestamp
- Decision
- Comments
- Workflow status
- System actions
Audit logs support compliance and troubleshooting.
Designing Effective Human Reviews
Human review steps should be:
- Clearly defined
- Easy to complete
- Limited to necessary information
- Consistent
- Secure
- Well documented
Overly complex approval processes reduce efficiency.
Best Practices
When designing human-in-the-loop agent flows:
- Automate repetitive tasks.
- Involve humans only where judgment is required.
- Define clear approval criteria.
- Use Power Automate approvals when appropriate.
- Notify reviewers promptly.
- Plan escalation paths.
- Handle timeouts gracefully.
- Log every decision.
- Protect sensitive information.
- Continuously monitor workflow performance.
Common Design Mistakes
Avoid:
- Requiring unnecessary approvals
- Allowing AI to make high-risk decisions autonomously
- Missing audit logs
- Ignoring timeout scenarios
- Poor notification design
- Overcomplicated approval chains
- Excessive reviewer permissions
- Missing exception handling
Monitoring Human-in-the-Loop Flows
Monitor metrics such as:
- Average approval time
- Approval rate
- Rejection rate
- Escalation frequency
- Timeout frequency
- Workflow completion rate
- Automation success rate
- User satisfaction
These metrics help optimize workflow efficiency.
Exam Tips
For the AB-620 exam, remember the following:
- Human-in-the-loop combines AI automation with human decision-making.
- Use HITL for high-impact, judgment-based, or regulated business processes.
- Power Automate approvals commonly support human review workflows.
- Decision points determine whether human intervention is required.
- Approval workflows should include notifications, escalation, and timeout handling.
- Responsible AI encourages human oversight for sensitive decisions.
- Audit logging is essential for governance and compliance.
- Apply RBAC and least-privilege access to reviewers.
- Monitor approval times and workflow performance after deployment.
- Automate routine work while reserving human effort for decisions requiring expertise.
Practice Exam Questions
Question 1
An organization wants managers to approve employee expense reports before reimbursement is issued. Which workflow design is most appropriate?
A. A fully autonomous AI agent that always approves expenses
B. A human-in-the-loop agent flow with a manager approval step
C. A public chatbot with anonymous access
D. A static FAQ topic
Correct Answer: B
Explanation: Expense approvals involve financial accountability and often require managerial judgment. A human-in-the-loop workflow allows the AI to automate data collection and validation while the manager makes the final approval decision.
Question 2
At what point in a human-in-the-loop workflow should the process pause?
A. Immediately after the user opens the conversation
B. Before collecting any information
C. When a predefined condition indicates that human review is required
D. After the workflow has already completed
Correct Answer: C
Explanation: Human review should occur only when predefined business rules, policy requirements, or confidence thresholds indicate that human judgment is needed.
Question 3
Which Microsoft service is commonly used to implement approval workflows that integrate with Copilot Studio?
A. Microsoft Paint
B. Azure Virtual Machines
C. Microsoft Word
D. Power Automate
Correct Answer: D
Explanation: Power Automate provides built-in approval actions, notification capabilities, escalation options, and workflow orchestration that integrate seamlessly with Copilot Studio.
Question 4
Which scenario is the best candidate for a fully automated agent flow instead of a human-in-the-loop workflow?
A. Approving multi-million-dollar contracts
B. Determining employee disciplinary actions
C. Retrieving a customer’s order status
D. Reviewing legal agreements
Correct Answer: C
Explanation: Retrieving order status is a deterministic task that typically requires no human judgment, making it ideal for full automation.
Question 5
Why is audit logging especially important in human-in-the-loop workflows?
A. It reduces authentication requirements.
B. It records approval decisions, timestamps, and workflow history for compliance and accountability.
C. It eliminates the need for notifications.
D. It replaces business policies.
Correct Answer: B
Explanation: Audit logs provide a record of who approved or rejected requests, when decisions were made, and how the workflow progressed, supporting governance and regulatory compliance.
Question 6
A workflow requires a supervisor to review refund requests over $5,000. What determines whether the approval step is executed?
A. Conversation greeting
B. Adaptive Card color
C. A conditional decision within the workflow
D. Conversation transcript length
Correct Answer: C
Explanation: Conditional logic evaluates predefined business rules—such as refund amount—to determine whether human approval is required.
Question 7
Which Responsible AI principle is most directly supported by human-in-the-loop workflows?
A. Eliminating all human involvement
B. Allowing AI to make all decisions independently
C. Providing human oversight for high-impact decisions
D. Preventing workflow automation
Correct Answer: C
Explanation: Human oversight helps ensure that important decisions involving ethics, safety, legal requirements, or significant business impact are reviewed by qualified individuals.
Question 8
A manager does not respond to an approval request within the required timeframe. What should a well-designed human-in-the-loop workflow do?
A. Wait indefinitely
B. Automatically delete the request
C. Skip the approval and continue processing
D. Execute a timeout strategy such as sending reminders or escalating the request
Correct Answer: D
Explanation: Timeout handling helps prevent workflows from stalling indefinitely by sending reminders, escalating to another approver, or taking another predefined action.
Question 9
Which security practice is most appropriate for reviewers participating in a human-in-the-loop workflow?
A. Grant every reviewer Global Administrator permissions
B. Allow anonymous approvals
C. Apply role-based access control and least-privilege permissions
D. Disable authentication to simplify approvals
Correct Answer: C
Explanation: Reviewers should only receive the permissions necessary to perform their approval responsibilities, reducing security risk while maintaining accountability.
Question 10
Which statement best describes the purpose of a human-in-the-loop agent flow?
A. To eliminate human participation from business processes
B. To automate routine work while incorporating human judgment where appropriate
C. To replace enterprise approval systems entirely
D. To prevent AI from interacting with external systems
Correct Answer: B
Explanation: Human-in-the-loop workflows combine the speed and efficiency of AI automation with human expertise for decisions that require judgment, compliance, or accountability.
Go to the AB-620 Exam Prep Hub main page
The Data Community 