We already have Microsoft Teams: what it does for status updates, and where it stops
Steffen Rosenögger, Founder of CapmePublished October 9, 2026
What Teams clips, the Updates app, Clipchamp and recorded meetings do for async status updates as of October 2026, where they stop, and when Teams is enough.
In short
- Microsoft documents Teams clips at up to five minutes and Clipchamp camera takes at up to 30.
- As checked in Capme's code in October 2026, Capme has no Teams app: the link opens in the browser, and listeners on Team sign in with an email code.
- For written check-ins, the Updates app in Teams already sets a due date and shows who has not submitted.
Microsoft 365 has a tool for each piece of an async status update: video clips in Teams chats and channels, Clipchamp (formerly Stream) for longer recordings, recorded Teams meetings, and the Updates app, which collects written check-ins by a due date. An async status round is a status meeting in which each speaker records their topic by a deadline and everyone watches in one place. Microsoft 365 records each video, and you tie them into such a round yourself. If one person reports, or a written answer will do, Teams is enough.
| Tool | What it records | Documented limit | Who sees it |
|---|---|---|---|
| Teams video clip | Camera, screen or audio, sent as a chat message or channel post | Up to 5 minutes since the 2025 rollout; the how-to page still says one minute | Everyone in the chat or channel, with automatic captions |
| Clipchamp (formerly Stream) | Camera and screen, kept as a video file in Microsoft 365 | 30 minutes per camera recording on work accounts | Whoever the file is shared with; transcript, chapters, comments |
| Recorded Teams meeting | The live call, in the organiser's OneDrive (SharePoint for channel meetings) | Expires after 120 days by default; admins set 1 to 99,999 days or never | Invitees from your organisation, read only; channel members for channel meetings |
| Video analytics | Views, viewers and a retention curve per video | Any playback longer than 0 seconds counts as a view | The owner, site members and people with edit access |
| Updates app in Teams | Written check-ins from a template; files can be required | Due date and recurrence; Microsoft's guide describes text and files, no recorder | Viewers you assign, with submitted and unsubmitted counts |
| Chat read receipts | Who has seen a chat message, clips included | "Read by" in group chats of 20 people or fewer | The sender; the admin decides whether people may switch it off |
The clip limit has two answers from Microsoft. Message Center post MC1066938 announced in May 2025 that Teams video clips go from one minute to five, rolled out worldwide by early September 2025, while Microsoft's how-to page for clips still said "up to a minute" on 5 October 2026. Record a test clip in your own tenant before you plan around five minutes. Stream now runs under the Clipchamp name (MC1088176), and Clipchamp's help for work accounts says: "You can record videos of up to 30-minutes duration." Microsoft's video analytics page adds: "we consider any playback >0 seconds as a view."
Can Microsoft Teams replace a status meeting?
Microsoft Teams can replace a status meeting in which one person reports, and it gets awkward once five do. There are four ways to try it in Teams. Copilot's meeting recap is no fifth: it summarises a meeting that was transcribed, so the hour still takes place (AI notetaker or async meeting weighs the two).
- Clips in the team channel. Microsoft's read-receipt page covers group chats only, so in a channel the visible sign is a reaction or a reply, and a missing clip hides between other posts.
- Clips in a group chat. Up to 20 people, read receipts show who has seen each clip. Five clips still arrive as five messages, with no agenda and no deadline.
- A recurring request in the Updates app. It has the due date and the list of who has not submitted, and the answers are text and files, so nobody shows their screen.
- A recorded channel meeting. Channel members open the recording in the channel's SharePoint folder, but the live hour still took place, and recording colleagues raises consent questions in Germany.
A search for a Loom alternative from Microsoft ends at clips and Clipchamp. A Loom user expects a link that works outside the company and a list of who watched: clips stay inside their chat or channel, while a Clipchamp file can go out as a guest or "anyone" link if your admin allows it, with viewers per file. A status meeting is several videos with an order, owners and an end date, the shape Capme's async meetings are built around; which meetings can go async sorts which of yours fit it.
Where does Microsoft 365 stop for status updates?
Microsoft 365 stops where a status update turns into a round of several people recording video by a deadline. The pieces exist in separate places: due dates in the Updates app, read receipts in group chats, view counts per file. Nothing ties them to one agenda of videos. The last four rows are where Microsoft 365 is ahead:
| What a status round needs | Microsoft 365 (as documented) | Recorded agenda in Capme |
|---|---|---|
| Several speakers in one order | One post or file per person, in a thread or folder | One agenda, up to 25 topics on Team, watched as chapters |
| One owner per topic | You name people in the post | Each topic has one named speaker, who gets a link to it |
| A deadline | A due date and recurrence in the Updates app, for written check-ins; for clips, you write it in the post | A recording deadline for speakers, shown with a countdown, never enforced |
| Who has seen it | Read receipts in group chats of up to 20; view and viewer counts per video; names on the file card if the site owner switches that on | Per person: watched, partly, opened, not opened (a topic counts from 75%), or totals only |
| A reminder | By hand, or a Power Automate flow you build | One automatic reminder after 3, 7 or 14 days to whoever has not finished |
| Viewers outside the company | Guests and "anyone" links, if your admin allows them | Up to 200 addresses per meeting, outsiders included, all free |
| Transcripts and captions | Automatic captions on clips; transcripts in Clipchamp | None |
| Comments and replies | Thread replies; comments on the video page | None; questions go to your channel |
| A live follow-up call | Teams | None |
| Cost for people who only watch | Covered by the licences you already pay | Free; the workspace pays per speaker |
What does a status round in Capme look like next to Teams?
Capme Meetings, a platform for async meetings, runs the round itself. A fictional example: a department of 30 holds a Monday Jour fixe in which 5 team leads report and 25 people listen.
- One of the team leads organises and writes the agenda: five topics, each with one team lead and a target of four minutes. The target is only a guide, up to 30 minutes, and never cuts a recording off.
- The deadline is Thursday 12:00. Each team lead gets one email with a link to their topic and records in the browser.
- The 25 listeners go on the audience list. When the organiser publishes, they switch on the reminder and pick 3 days. On Team, each listener signs in with their work email and a six-digit code; on Business, the owner can connect Microsoft Entra ID over SAML single sign-on instead.
- The organiser posts the link in the department's Teams channel, and it opens in the browser. Questions go into that thread.
- On Friday the organiser sees who has watched everything, who has watched part, and who has not opened it.
On Team, the workspace pays per speaker: five team leads at €12 each come to €60 net a month, with a minimum of 3 speakers. Organising also needs a speaker seat, which is why the organiser is one of the five. The 25 listeners are free (our arithmetic from the published price).
As checked in Capme's code in October 2026, there is no Teams app and no calendar integration. If your team relies on captions, Microsoft 365 does that part better, since Capme has none. On Team recordings are kept 365 days unless someone marks them keep, and Business sets its own window.
Run next week's Jour fixe as a recorded agenda
Topics, owners, a deadline, and the link in your Teams channel. The trial runs 14 days.
What do the works council and the DPO say if Teams is already approved?
A company's approval for Teams covers Teams only: a second tool needs its own data processing agreement and, where there is a works council, its own look at what it records about people. Under § 87(1) no. 6 BetrVG the council has a say over technical means that can monitor behaviour or performance, and per-person watch progress can fall under it. Capme's totals-only setting answers the usual objection: organisers and admins then see numbers without names. The steps are in introducing a video tool in Germany.
For the DPO, the DPA and the Trust Center are public. Videos are stored on EU hosting, or on Business in your own S3 bucket.
When is Teams enough for status updates?
Teams is enough for status updates when one or two people report and each update fits in a short clip, or when a written answer to a few fixed questions will do. For that second case, we think the Updates app is the right first try as long as nobody needs to show a screen, because it is part of Teams and already lists who has not submitted. Switch the round to a recorded agenda when at least two of these apply:
- Three or more people report, every week.
- The speakers need to show a screen or a demo, and text will not do.
- You have to know who has not watched, by name or in totals.
- People outside the department or the company should watch.
For a status review with clients or a steering group, the async project status review has an agenda you can copy, and the comparison of async video update tools covers the options beyond Microsoft. If people have to agree on something they see differently, neither a clip nor an agenda helps, so keep that part live in Teams.
Frequently asked questions
- Can a Teams meeting recording be kept longer than 120 days?
- Yes, if your admin raises the default in the meeting policy, up to 99,999 days or, through PowerShell, never. The change applies only to new recordings. Expired recordings go to the recycle bin, which on work accounts empties after 93 days by default.
- What if a sixth person reports only now and then?
- They need a speaker seat to record, billed per month. If they go back to being a viewer, they keep their recordings, but the bill drops only once the owner lowers the number of paid speakers.