What still differs in video meetings, with three Teams answers

Video meeting software is the most commoditized product in this whole category. Everything serious does grid views, screen sharing, virtual backgrounds, breakout groups, chat, and recording. If you evaluate on that list, every candidate will score nearly full marks and you will learn nothing.

The differences that remain are at the edges: bad networks, outside guests, what happens to recordings, and who can hear what. Those edges are where meetings actually fail, so that is what this page is about.

What to take away

What is now commodity

Treat these as present everywhere and stop scoring them: multiple video layouts, screen and window sharing, background blur and replacement, breakout rooms, in-meeting chat, hand raising, reactions, cloud recording, live captions, calendar integration, and a browser-based join option.

They are not unimportant. They are simply not discriminating, and time spent comparing them is time not spent on the things below.

Where the real differences are

1. Behavior on a poor connection. Zoom, Microsoft Teams, Google Meet and Whereby all drop video before audio when bandwidth collapses, and they split on recovery. Does the call repair itself after a brief loss, or does the person have to rejoin? Does the product tell the participant it is degrading, or simply freeze? This is the difference people feel most and the one no comparison table records.

2. The joining experience for outsiders. Whether a guest can join from a browser without installing anything or creating an account, how many clicks it takes, and how much it nags. If you run sales calls, client meetings, interviews, or public sessions, this is your single most important criterion, because friction here is measured in people who did not turn up. Google Meet and Whereby join in the browser with nothing to install. Zoom and Microsoft Teams also offer a browser join, so the difference is how many prompts stand between the guest and the room.

3. What happens to recordings and transcripts. Where they are stored, who can reach them, how long they are kept, whether they can be deleted on request, and whether an administrator can find all of them. This is a data governance decision wearing the costume of a convenience feature. Where recordings land differs. Zoom cloud recordings stay in Zoom's storage, Microsoft Teams saves recordings to SharePoint or OneDrive, and Google Meet saves them to Drive.

4. Telephone access. Whether people can dial in and be heard, and which license that takes. Still genuinely necessary for some participants and some regions, and frequently either absent or an expensive add-on. Dial-in is usually a paid extra. Microsoft Teams sells it as an add-on license, Google Meet ties it to certain Workspace editions, and Zoom depends on the audio plan.

5. Accessibility. Zoom, Microsoft Teams and Google Meet all ship live captions, keyboard navigation and a published accessibility statement, so the feature list settles nothing. Caption quality with real accents and real cross-talk is the test. Run it with the people who need it, ask whether captions can be saved and searched afterward, and treat the answer as a requirement rather than a preference.

6. Administrative control. Zoom's admin portal, the Microsoft Teams admin center and the Google Workspace admin console all set defaults centrally — recording permissions, who may admit guests, whether meetings are locked by default, what participants can share — and each keeps an audit log of who changed what. What differs is how much of that sits behind a higher tier and how far back the log reaches. The same administrative defaults decide who may share files and folders, which is the permission model a file sharing service sells.

If you can only test two criteria, make them the outsider join and behavior on a poor connection.

Three of the differences, answered for Microsoft Teams

Vendors document some of these edges precisely, and Microsoft's Teams documentation shows what a written answer looks like for three of them.

Outsider join. Teams gives administrators an organization-wide "Anonymous users can join a meeting" setting and a per-organizer "Anonymous users can join a meeting unverified" policy. When anonymous meeting join is turned on, lobby policies affect how anonymous participants join meetings. A third option, letting anonymous users join after verifying through a one-time passcode, is a Teams Premium setting, and only organizers with a Teams Premium license can use it.

Telephone access. Audio Conferencing requires an extra Teams add-on license for each person in your organization who is going to schedule or host an Audio Conferencing meeting, while meeting attendees who dial in don't need any extra licenses.

How far back the audit log reaches. Audit (Premium) in Microsoft Purview provides a default audit log retention policy that retains all Exchange Online, SharePoint, OneDrive, and Microsoft Entra audit records for one year. Audit records for all other activities are retained for 180 days by default, unless you change the retention with a custom audit log retention policy, which is itself part of the Audit (Premium) capabilities.

Ask Zoom, Google and any other shortlisted vendor for the same three answers in writing, so the comparison rests on documents rather than demos.

Test it on a bad network, deliberately

Arrange the opposite:

Then note what breaks, in what order, and whether the software tells anyone what is happening. A product that says "your connection is unstable" and drops your video is doing something useful. One that simply freezes is not.

Do this for at least a couple of the shortlisted options on the same day with the same people, because network conditions vary too much to compare across weeks.

Recordings are a retention decision

The moment you enable recording, you have created a data set with legal and practical weight, and it grows on its own.

Consent is regulated. In the United States, several states require that all parties consent when one party wants to record a telephone conversation, and a meeting recording that captures everyone raises the same question for whoever signs off on retention.

Decide before rollout:

Automatic transcription and summarization are worth evaluating on the same terms. The useful question is not how good the summary is; it is where the transcript is stored, how long it lives, and who else's systems it passed through on the way.

The encryption trade-off is real

Two different things are called encryption in this category, and the distinction matters.

The trade-off is structural, not a product limitation: anything requiring the provider to process the media is unavailable under end-to-end encryption. That typically includes cloud recording, server-side transcription, telephone dial-in, and streaming out to other platforms, because a server that cannot decrypt the stream cannot transcribe, record, or bridge it.

Decide this alongside the ordinary settings rather than separately, because most of what goes wrong in this category is a meeting that was open when it should not have been rather than a cipher that was too weak. The short checklist in the guidance on securing online meetings covers the settings that actually prevent incidents.

The question is not whether it supports end-to-end encryption, since many do. The question is which meetings need it, and whether you will give up recording and dial-in for those meetings.

For most organizations, a small subset of conversations warrants it and the rest do not. You need a product that turns it on per meeting rather than only for the whole account.

What measurement can and cannot tell you

Meeting platforms report attendance, duration, engagement signals, and connection quality. Two of those are useful.

Genuinely useful: connection quality data, which lets you distinguish "the software is bad" from "that office's internet is bad", a distinction that otherwise gets argued about for months. Also useful: adoption data showing whether people are actually using the tool you bought, or quietly meeting somewhere else.

Not useful: attention and engagement scoring. It measures whether a window was in focus, which is not attention, and using it as a management signal produces performance rather than participation. If your candidate markets this heavily, treat it as a statement about the vendor's assumptions rather than a feature.

Whatever you collect, decide who can see per-person data before you turn it on. Participant-level analytics is one of the few things in this category that can damage trust faster than an outage.

A trial worth running

Before you commit

Ask about the exit and about the edges:

What makes leaving expensive

Less than in most categories, which is genuinely good news: meetings are ephemeral and habits transfer quickly, and the costs that remain are worth naming before you sign a term contract rather than after.

Because switching cost is comparatively low here, this is a category where it is reasonable to choose on the edges rather than agonize. Get the outside-guest experience and the recording policy right, verify the bad-network behavior, and accept that the rest is close enough not to matter.

Where to read next

Meetings sit inside a wider estate; three neighboring decisions usually settle part of this one. The suite decision often includes a meeting product worth testing first, while the collaboration decision determines how much coordination needs a call at all.

Since almost every invitation travels by mail, the mail decision and the hosting arrangement affect whether joining details reach people intact.

Common questions

Do we need a meeting room system, or is a laptop enough?

A laptop works for two or three people and fails for a room of eight, because the microphone cannot hear the far end of the table. The threshold is the room, not the budget. Fix the microphone before the camera; people forgive a poor picture and leave a call they cannot hear.

How do we handle recordings people ask us to delete?

Decide the process before the first request. Who can ask, who decides, how the recording is located, and what is recorded about the deletion. The hard part is finding every copy, which is an argument for keeping recordings in one place rather than letting people download them.

Is it worth paying for a webinar product?

Only with a date in the calendar. Broadcast products are priced by attendee capacity and are commonly bought speculatively. The ordinary meeting product handles more than most people expect, and the moment it does not is obvious.

What should we do about the meeting that could have been a message?

Nothing the software can help with. The number and length of meetings is a property of how decisions get made, and it changes when somebody is named to decide rather than when a better product is bought.