Question 16 — AB-620 Case Study Set
Given that the system rendered the version 1.6 card correctly in the Copilot Studio test pane but produced fallback behavior in Teams, which conclusion best explains the discrepancy? (Select one answer)
The test pane can render capabilities associated with the web channel, while Teams has a lower Adaptive Card schema ceiling.
The Teams client requires Adaptive Cards to use version 1.6 even when the web channel successfully renders version 1.6.
The Foundry project endpoint changes Adaptive Card schema versions when an agent is invoked from Teams.
The Azure Function must authenticate through Microsoft Entra ID before Teams can display the card body.
Correct answers
The test pane can render capabilities associated with the web channel, while Teams has a lower Adaptive Card schema ceiling.
Explanations
Correct Answer:
The test pane can render capabilities associated with the web channel, while Teams has a lower Adaptive Card schema ceiling.
Explanation:
Paideffort validated the card in an environment that uses web-channel rendering behavior, where version 1.6 can work. The production Teams deployment supports version 1.5 as its maximum. The card therefore passes the web-oriented test while containing schema features that aren't compatible with Teams.
Wrong Answers:
The Teams client requires Adaptive Cards to use version 1.6 even when the web channel successfully renders version 1.6.
The compatibility direction is reversed. Paideffort's Teams deployment has a lower supported schema ceiling than its web deployment.
The Foundry project endpoint changes Adaptive Card schema versions when an agent is invoked from Teams.
The Foundry endpoint is used for agent operations and policy reasoning. It doesn't negotiate or rewrite the Adaptive Card schema used by the Teams renderer.
The Azure Function must authenticate through Microsoft Entra ID before Teams can display the card body.
Entra authentication governs downstream enterprise services. The rendering discrepancy occurs before any requirement to execute the leave-recording Azure Function.