Question 14 — AB-620 Case Study Set
Business Requirements
Paideffort operates a global HR assistant in Microsoft Copilot Studio for approximately 42,000 employees. The agent is available through Microsoft Teams, Live Chat for service-desk users, and an internal web portal. Employees use the agent to view leave balances, review regional leave policies, and submit requests. HR leadership requires the same essential information and actions to remain available across all supported channels, even when individual channels render conversational UI differently.
The leave-balance card must work reliably in Microsoft Teams and the internal web portal. Live Chat will be enabled for a limited group during the next release. HR prefers one maintainable card definition unless a measurable web-channel benefit justifies maintaining channel-specific variants. Employees must never become blocked solely because suggestion buttons or advanced card elements are unavailable in their channel.
Paideffort requires Microsoft Entra ID authentication for enterprise services, managed identities where supported, auditable tool execution, and centralized operational monitoring. The platform must support regional scale-out without unnecessary model invocations or duplicate topic logic. The employee-facing interaction should remain predictable across channels, and production acceptance requires testing in every target channel rather than relying only on authoring-time previews.
Technical Architecture
Copilot Studio hosts the primary orchestration topic. A Microsoft Foundry project provides an HR policy agent for complex entitlement interpretation and country-specific policy reasoning. Project-scoped operations use the Foundry project endpoint and Foundry SDK. Direct model operations that don't need project-scoped agent capabilities use the Azure OpenAI endpoint through the OpenAI SDK.
A FunctionTool performs deterministic leave entitlement calculations. An OpenAPI tool exposes approved HR operations, and an Azure Function records finalized leave requests. Production access uses Microsoft Entra ID and managed identity. Adaptive Cards are used only for structured employee interaction; deterministic channel compatibility checks are handled in the topic rather than delegated to the model.
Current Card Implementation
The design team copied a leave-summary card from an external card gallery and modified it in the Copilot Studio test pane. The card uses a two-column layout, an action for opening leave details, and a compact footer. The team approved the design after it rendered correctly in the test pane and the internal web portal.
{
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"type": "AdaptiveCard",
"version": "1.6",
"body": [
{
"type": "TextBlock",
"text": "Leave balance",
"weight": "Bolder"
},
{
"type": "Container",
"layouts": [
{
"type": "Layout.Flow"
}
],
"items": [
{
"type": "TextBlock",
"text": "Annual leave: 14 days"
},
{
"type": "TextBlock",
"text": "Sick leave: 8 days"
}
]
}
],
"actions": [
{
"type": "Action.Execute",
"title": "View details",
"verb": "viewLeaveDetails"
}
]
}
After publication to a pilot Teams group, several employees report that the leave card doesn't appear as designed. In some sessions they receive fallback text instead. The same card continues to render in the web test pane. The release engineer confirms that Microsoft Teams and Live Chat are being treated as production targets alongside the web portal.
Topic Routing Prototype
A developer proposes preserving the richer web experience by creating a separate card for each channel. The following topic configuration is being evaluated:
topic: LeaveBalance
steps:
- detectChannel
- condition:
when: channel == "web"
sendCard: LeaveBalanceWeb16
- condition:
when: channel == "teams"
sendCard: LeaveBalanceTeams15
- condition:
when: channel == "livechat"
sendCard: LeaveBalanceLiveChat15
- invokeAgent:
endpoint: ${FOUNDRY_PROJECT_ENDPOINT}
agent: hr-policy-agent
purpose: "Confirm card compatibility for the active channel"
The web, Teams, and Live Chat cards currently contain the same HR information and differ only in schema version and minor layout styling. Product management has not identified any measurable employee outcome that depends on the newer web-only layout.
Deployment Validation
Paideffort's release pipeline contains a compatibility validation utility. It evaluates the card version selected for each channel before the package is promoted. The current Python implementation is shown below.
CHANNEL_LIMITS = {
"teams": 1.5,
"livechat": 1.5,
"web": 1.6
}
def validate_card(channel, card):
requested_version = float(card["version"])
supported_version = CHANNEL_LIMITS[channel]
if requested_version <= supported_version:
return True
return False
The web-channel deployment also consumes the Action.Execute definition from the current card. During user acceptance testing, the card body appears but the expected action behavior isn't considered reliable enough for production.
Several leave topics also display quick replies such as “Request leave,” “View balance,” and “Review policy.” Some channel integrations used by regional business units either don't render these buttons or display fewer suggestions than the topic defines. The current message text says only “Choose an option below.”
Future Requirements
Paideffort plans to add more regional channels, richer agent capabilities, centralized card-rendering telemetry, and governance reports that correlate failed interactions with channel, schema version, and card definition. Security engineering will expand Entra-based authorization for HR tools, while the platform team wants to minimize duplicate card maintenance. Release governance requires production-like testing in Teams, Live Chat, and the web portal before a card is approved for broad employee deployment.