Advanced: Microsoft Graph tests
For troubleshooting. Every request and Microsoft’s answer is also written to the activity log above.
Nothing waiting.
No transcripts yet. They appear here a few minutes after each meeting ends.
Meetings from the Google Sheet – the bot joins each one at its start time.
No meetings on this day.
Paste one Teams meeting link or hundreds, one per line. The bot joins each as the bot account, switches transcription on, leaves, then takes the next.
What the bot is about to do, one meeting at a time.
Nothing here. Paste links under Start transcription – the schedule also adds meetings a few hours ahead.
Nothing yet. Each meeting the bot joins, and each sign-in test, shows up here with its log and screenshots.
Fetched from Microsoft 365 after each meeting the bot switched transcription on in.
No transcripts yet. When the bot has switched transcription on, the transcript appears here after the meeting ends.
Fetches every transcript of that meeting from Microsoft 365 – also a quick way to test the setup with a meeting that already has one.
What is in the VMA database – one row per meeting in meeting_records, day by day.
A meeting’s row is written as soon as the sheet is synced (course, assignment, trainer, attendees, scheduled times). After the meeting, Teams’ transcript fills user_transcription (the trainer) / participants_transcription, the real start and end times and the duration; the report columns come last. Rows the VMA app wrote itself are never changed.
How the bot behaves, and the Microsoft Graph tools.
Set in the server’s environment variables.
Sets the meeting option “Record and transcribe automatically”. Needs OnlineMeetings.ReadWrite.All and a Teams application access policy; the meeting is recorded as well.
No meetings yet.
Joins through Microsoft Graph and reports whether Teams is transcribing. Graph cannot switch it on for this app.
For troubleshooting. Every request and Microsoft’s answer is also written to the activity log above.