Microsoft Teams Insights

01 · Challenge

Coordinators were splitting their attention between the meeting and the notes.

Meeting coordinators needed to participate in calls while also creating an accurate record of the discussion. Concentrating on note-taking made it harder to stay engaged, and the quality and consistency of meeting artefacts could vary.

The goal was to automate that work without moving the application itself away from the organisation’s on-premises environment.

02 · Ownership

A complete solution researched, designed and built independently.

I researched, designed and built the entire application and remain its sole maintainer, responsible for production support, upgrades and continued development.

The work covered the Go backend, webhook-based Microsoft change-notification integration, RabbitMQ processing queues, SigNoz telemetry, on-premises deployment and the React and Microsoft Fluent UI experience presented within Teams as a tab application.

03 · Approach

React to Teams events, then return the useful context to Teams.

The application subscribes to Microsoft change notifications for meeting recordings and transcripts. Microsoft publishes each notification to a webhook exposed by the Go backend. The application then retrieves the relevant meeting artefacts and uses RabbitMQ to queue them for processing.

Summaries and structured notes are presented through a Teams tab built with React and Microsoft Fluent UI, allowing participants to use the output in the same collaboration environment as the meeting. SigNoz provides application telemetry for monitoring and operational investigation.

Access is provided through the Microsoft identity and Teams context, while retention and additional security controls continue to be expanded as part of the development roadmap.

The most significant engineering challenge was integrating cloud-hosted Microsoft APIs with an on-premises application. Available documentation did not fully cover the combination of recording notifications, transcript processing and Teams tab integration, requiring detailed research and iterative testing.

04 · Outcome

More attention in the meeting and more reliable artefacts afterwards.

The application is used across a workforce of approximately 80 employees and has been in active production since January 2025.

Automated note-taking allows coordinators to concentrate on the conversation instead of documenting it manually. The resulting notes are more consistent and are reused as previous-meeting context during follow-on discussions.