FAQ - What data does BeZoned receive from Microsoft Teams change notifications?

Which Microsoft Graph change notifications BeZoned subscribes to for teams, channels, members and online meetings, what data they contain, and how long it is kept.

BeZoned keeps your virtual offices in sync with Microsoft Teams using Microsoft Graph change notifications. When something changes in Teams, Microsoft notifies BeZoned's API. Examples are a team being renamed, a channel being renamed, a member leaving a team or a meeting ending. This article explains what those notifications contain, what BeZoned does with them and how long anything is kept.

Which subscriptions does BeZoned create?

BeZoned creates subscriptions for each Microsoft Team that is set up as a BeZoned office, and for each online meeting held in a BeZoned meeting room.

Subscription	What Microsoft sends	What BeZoned does with it
Teams(team updated or deleted)	Metadata only: subscription ID, change type, tenant ID and team ID. No team content.	Reads the team's current display name from Microsoft Graph and updates the office name. If the team is deleted, the office is removed from BeZoned.
Channels(channel updated)	Metadata only: subscription ID, change type, tenant ID, team ID and channel ID. No messages or files.	Reads the channel's current display name and updates the name of the linked table in the office.
Team members(member added, changed or removed)	Member details, encrypted with BeZoned's certificate.	Only notifications about a removed member are decrypted. BeZoned uses only that person's Microsoft user ID to remove them from the office. Notifications about added or changed members are not decrypted and are discarded.
Online meetings(call events for a meeting room meeting)	Call events (started, ended, participants updated), encrypted with BeZoned's certificate.	BeZoned reads only the event type, event ID and time, and acts only on call ended. When a call ends, BeZoned resets the meeting room and deletes the subscription at Microsoft. All other fields are ignored.

BeZoned never receives or stores audio, video, recordings, transcripts, or chat or channel message content through these subscriptions.

How are notifications protected?

All notifications are delivered over HTTPS to BeZoned's API.
Every notification is checked before it is processed. It must carry a shared secret matching your organization's tenant, and it must belong to a subscription that BeZoned knows about.
Notifications that carry member or meeting data are encrypted by Microsoft. BeZoned also verifies the validation token Microsoft signs for each delivery before it decrypts anything.
Decryption happens in memory only.

What is stored, and for how long?

Notification content is not stored. Each notification is processed in memory and discarded once the request completes.
Subscription details are stored in your organization's own, separate database: the subscription ID, the resource it covers (for example the team ID), the change type and the expiry time. Subscriptions expire after 2 days and are renewed automatically. The details are deleted when the office is deleted. Meeting subscriptions are removed as soon as the meeting ends.
Team and channel names that BeZoned reads after a notification are stored as part of your office for as long as the office exists.
Usage event: when a meeting ends, BeZoned records a product usage event that contains only the meeting room's ID, not who attended.
Operational logs and error monitoring contain technical identifiers: tenant, team, channel and subscription IDs. When a team or channel is renamed, they also contain the old and new names.

All data is hosted in EU.

What happens if we stop using BeZoned?

When an office is removed, its subscriptions are deleted. If your organization stops using BeZoned, or you want your data deleted, contact our support team and we will delete it.

If you have further questions about data handling, please contact support.

Was this helpful?

Still need help? Ask the team