Redact a Microsoft Teams screenshot

Teams looks like Slack after a Microsoft skin. The leaks are the same class: emails, meeting join codes, SharePoint paths with tenant names.

Recap screenshots usually include a call window, a chat pane, and a calendar peek. Each pane has a different roster. If the artifact is a slide, the gallery is not the artifact. If the artifact is an error toast, the tenant URL in the title bar is still chrome.

Call window chrome

• Participant names across the top and in the roster flyout.
• Together-mode or large-gallery tiles you cannot crop.
• Chat pane with a pasted password or a guest email.
• “Meeting in progress” calendar peek with other appointments.
• Join info: meeting ID, passcode, dial-in numbers.
• Sensitivity labels that still leave a customer domain in the message.

Cover names of people who are not in the recap you are allowed to send. Virtual backgrounds fail; a bedroom or a badge on a lanyard is still in the tile. If the point is the shared deck, crop to the deck. Presenter view sometimes shows speaker notes; those notes are not the slide. Crop them. A second monitor with Outlook open behind Teams is a classic “I captured the whole display” leak — snip the window, not the desktop.

Chat, files, and SharePoint paths

Org directory photos sit next to every message. File names like a layoff workbook are a leak even if you cropped the sheet. Bar the file name. SharePoint and OneDrive URLs in the copy link dialog include tenant hosts; bar the host if the screenshot leaves the company.

Approval bots reprint email addresses. Cover them. Loop components and wikis in a channel often title themselves after a customer. Bookable desks and Shifts views add locations and phone extensions. If the bug is a button, crop until the roster of who is on shift is gone. Walkie-talkie tiles are names plus presence; they are not the error toast. Recurring-meeting series titles in the header often include a client; bar or crop that title on anything public.

Windows snipping is the usual capture path. After Win + Shift + S, you still need rectangles. The Slack twin of this checklist is Slack screenshots.

Black bar for codes and numbers

Conference IDs, dial-in numbers, OTPs from a bot, and account numbers pasted “for the vendor” are short strings. Do not Gaussian-blur them. Paint a bar. Guest join links are doors; cover the query string.

Export PNG. Teams chat will recompress; start from a flat barred file so you are not screenshotting a highlighter.

Calendar, voicemail, and status

Calendar screenshots include other meetings in the week grid. Crop to the one event or bar neighboring titles. Voicemail tiles show callback numbers. Status messages (“in an interview”) are not yours to publish for other people. Activity feeds mix DMs, @mentions, and file comments; if you only needed one mention, crop until the rest of the feed is gone. Queues in a call-center tenant add ANI-style numbers — bar those digits, do not discuss how to use them.

FAQ: Can I post a gallery if everyone works here?

Internal does not mean “fine for LinkedIn.” People in the gallery did not sign up for your recap post. Crop to the slide. If a face must stay, ask; do not assume.

FAQ: What about recorded-meeting screenshots?

A recording already has access control. A PNG does not. Bar names and codes in the still. Do not treat Stream permissions as redaction.

FAQ: Sensitivity labels vs redaction?

A label is a policy hint. It does not cover pixels. You can still leak a customer domain under a “Confidential” header. Bar the domain.

FAQ: Mobile Teams?

Mobile adds a system nav bar and notification previews. Cover banners. The people picker on a new chat is a directory; do not capture it to show a bug in the composer.

Snip the recap, then finish the bars in the browser so the tenant path never leaves with the slide. BlurThis is the local finishing step.