Using the appropriate models for MSTeams meeting start/end routes

[Rodrigo Brandão (rodrigobr-msft)]

This pull request updates the way meeting start and end events are handled in the Microsoft Teams agent extension. The main change is to use the more specific MeetingStartEventValue and MeetingEndEventValue models instead of the generic MeetingDetails model. This ensures that meeting event handlers receive the correct data structures and improves type safety. The tests have also been updated to reflect these changes and to validate the new models.

Meeting event handler improvements:

• Meeting start and end handlers now use MeetingStartEventValue and MeetingEndEventValue models, respectively, instead of the generic MeetingDetails model. This affects both the handler signatures and the models used to parse incoming event data. [1] [2] [3] [4] [5] [6]

Test updates:

• Tests have been updated to use the new event value models. Test helper functions now return payloads matching the expected schema, and test assertions check for the correct model types and field values. [1] [2]

[Copilot]

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Copilot review overview

Review effort: Lite
Findings: 1 · 1

Open (2)

• The new models introduce event-specific fields (StartTime/EndTime) but the tests only assert… · New
• The test names still reference 'meeting_details', but the tests now validate… · New

What changed in this PR

Updates Microsoft Teams meeting start/end event handling to use the dedicated MeetingStartEventValue and MeetingEndEventValue models (instead of MeetingDetails) for improved schema correctness and type safety.

Changes:

• Swap meeting start/end handler parsing and type annotations to use MeetingStartEventValue / MeetingEndEventValue.
• Update tests to send event payloads matching the new meeting start/end schemas and assert on parsed fields.
• Update the Teams API usage manifest to reflect the newly consumed upstream symbols.

File	Description
tests/​hosting_msteams/​test_meetings.py	Updates test payloads and assertions to validate MeetingStartEventValue / MeetingEndEventValue.
libraries/​microsoft-agents-hosting-msteams/​teams-api-usage-manifest.json	Replaces MeetingDetails usage with meeting start/end event value models.
libraries/​microsoft-agents-hosting-msteams/​microsoft_agents/​hosting/​msteams/​meeting/​route_handlers.py	Updates handler type signatures to the more specific meeting start/end models.
libraries/​microsoft-agents-hosting-msteams/​microsoft_agents/​hosting/​msteams/​meeting/​meeting.py	Updates route handlers to parse incoming activity values into the new models.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.