Maybe that custom expense tracker app isn’t needed anymore. Or perhaps someone added an app to your team that’s just taking up space. Whatever the reason, removing Power Apps from Teams isn’t always obvious if you’ve never done it before.

In this guide, I’ll walk you through exactly how to remove Power Apps from Teams chat. We’ll cover everything from removing apps from individual chats to getting rid of them from entire teams. Let’s dive in.

Why You Might Want to Remove Power Apps from Teams

Before we get into the how-to, let’s talk about why you’d want to do this in the first place.

Your Teams workspace can get messy fast. Every app you add creates another tab, another notification source, and another thing to manage. (If you’re still on the setup side, here’s how to add Power Apps to Teams in the first place.) When apps pile up, it becomes harder to find what you actually need.

Here are some common reasons people remove Power Apps:

• The app was created for a specific project that’s now finished
• The app isn’t being used by anyone on the team anymore
• You have duplicate apps doing similar things
• The app is causing performance issues or errors
• You’re reorganizing your Teams workspace for better efficiency

Whatever your reason, cleaning up unused apps just makes sense. It keeps your workspace clean and helps your team focus on what matters.

Understanding Where Power Apps Can Live in Teams

Power Apps can show up in different places within Microsoft Teams. Before you start removing them, it helps to understand where they might be hiding.

Power Apps can appear in:

• Personal app bar (on the left side of Teams)
• Team channels as tabs
• Team channels as bots or messaging extensions
• Group chats as tabs
• One-on-one chats

Each location requires a slightly different removal process, because a channel tab belongs to the whole team while a personal app belongs only to you (here’s a quick refresher on Microsoft Teams team vs channel). Don’t worry though – I’ll cover all of them.

Removing Power Apps from Your Personal App Bar

Let’s start with the easiest one. If you’ve pinned a Power App to your personal app bar (that’s the vertical menu on the left), here’s how to remove it.

Step 1: Look at your app bar on the left side of Teams. Find the Power App you want to remove. If it isn’t pinned there, select View more apps (…) and search for it.

Step 2: Right-click on the app icon.

Step 3: Select “Uninstall” from the menu that appears. (If you only want the icon off the app bar but still want the app, choose Unpin instead.)

Step 4: Select Remove when Teams asks you to confirm.

That’s it. The app disappears from your personal view immediately. Note that this only removes it from your personal app bar – if the app is added to a team or channel, it’ll still be there. Microsoft confirms that uninstalling the Power Apps personal app doesn’t remove the apps you built with Power Apps from your Teams channels.

Removing Power Apps from Team Channels

This is where things get a bit more involved. When a Power App is added as a tab in a team channel, you need the right permissions to remove it.

You’ll need to be:

• A team owner, or
• A team member, as long as the owner hasn’t turned off Allow members to create, update, and remove tabs in the team’s member permissions

If you don’t have these permissions, you’ll need to ask your team owner to remove the app for you.

Here’s the process:

Step 1: Navigate to the team and channel where the Power App is located.

Step 2: Look at the tabs at the top of the channel. Find the tab for the Power App you want to remove.

Step 3: Click the small dropdown arrow next to the tab name.

Step 4: Select “Remove” from the dropdown menu.

Here’s what that menu looks like on a Power Apps tab I added to the First Public Channel of my SPGuides demo team. The tab shows the app’s name (Service Desk Demo here), not “Power Apps”:

Step 5: Teams will ask you to confirm. Click “Remove” again.

The app tab disappears from that channel. Remember, this removes it for everyone in that channel, not just you. Make sure your team doesn’t need this app before you delete it.

Removing Power Apps from Chats

Power Apps can also be added to group chats or one-on-one conversations. The removal process here is similar to removing them from channels.

For group chats:

Step 1: Open the group chat where the Power App is installed.

Step 2: Click on the tab with the Power App name at the top.

Step 3: Click the dropdown arrow next to the tab name (or right-click the tab).

Step 4: Select “Remove” and confirm your choice.

In group chats, any member can typically remove tabs. But keep in mind that removing it affects everyone in the chat, so maybe give folks a heads up first.

Uninstalling Power Apps Completely from Teams

If you want to completely uninstall a Power App from your Teams environment (not just hide it), you need to go through the Teams app management settings.

Step 1: Select Apps in the app bar on the left side of Teams. (After the latest Teams update, my tenant labels this button Store.)

Step 2: Select Manage your apps. In the newest version, it’s the icon at the top right of the Store page, and it opens a page called Your agents and apps.

Step 3: Use the filters at the top, such as Added by you, to narrow the list.

Step 4: You’ll see a list of all apps installed in your Teams. Scroll through and find the Power App you want to remove.

Step 5: Hover over the app and select More options (…).

Step 6: Select “Uninstall.”

Step 7: Confirm the uninstallation when prompted.

If your Teams still shows the older Manage your apps list, expand the app’s row instead. It lists the teams and chats where you’ve used the app, and you can select Remove for each place one by one.

This removes the app from your personal Teams environment entirely. If the app was added at the organization level by your admin, you might not be able to uninstall it completely.

Removing Power Apps as a Teams Admin

If you’re a Teams admin and need to remove a Power App for your entire organization, the process is different.

Step 1: Go to the Microsoft Teams admin center (admin.teams.microsoft.com).

Step 2: In the left navigation, go to “Teams apps” and then “Manage apps.”

Step 3: Find the Power App in the list. You can use the search box to make this faster.

Step 4: Click on the app name to open its details page.

Step 5: Check the status toggle at the top. If it’s set to “Allowed,” you can change it to “Blocked.”

Step 6: When you block an app, it becomes unavailable to all users in your organization.

Blocking an app doesn’t delete any data, and the change isn’t instant. Microsoft says availability changes can take up to 24 hours to reach every user. While it’s blocked, people can’t add or use the app.

Most tenants were moved to app centric management starting in April 2025, so you may see an Available to column instead of a simple status. In that case, open the app, go to Users and groups > Edit availability, and choose No one (the same as blocking) or Specific users or groups. The older app permission policies are deprecated.

What Happens to Data When You Remove a Power App

This is an important question that a lot of people have. When you remove a Power App from Teams, what happens to all the data?

Here’s the good news: removing the app from Teams doesn’t delete the underlying data. The Power App itself still exists in your Power Apps environment, and all the data is still stored safely.

Removing the app from Teams just removes the interface – the way you access the app. Think of it like removing a shortcut from your desktop. The actual program is still installed on your computer.

If you want to delete the app and its data permanently:

• You need to go to Power Apps directly (make.powerapps.com)
• Find the app in your app list
• Delete it from there
• Then separately delete any associated data sources if needed

Most people just want to remove the app from Teams to declutter, not delete everything. But it’s important to know the difference.

Troubleshooting Common Issues

Sometimes things don’t go as smoothly as we’d like. Here are some common problems and how to fix them.

Can’t find the remove option: You might not have the right permissions. Check with your team owner or Teams admin.

App reappears after removal: If your admin installs or pins an app for everyone through an app setup policy, it might come back automatically. Contact your IT department if this keeps happening.

Error message when trying to remove: Try closing and reopening Teams, then try again. If the error persists, sign out and sign back in, or clear the Microsoft Teams cache.

App tab is grayed out: The app might be managed by a policy. Again, your Teams admin needs to handle this one.

Best Practices for Managing Power Apps in Teams

Now that you know how to remove apps, let’s talk about some best practices to avoid clutter in the first place.

Regular cleanup sessions: Schedule time every few months to review which apps your team actually uses. Remove the ones that aren’t adding value. It’s also a good time to review your Microsoft Teams settings.

Clear naming conventions: Make sure all Power Apps have clear, descriptive names. This makes it easier to identify what each app does and whether you need it.

Document app purposes: Keep a simple list somewhere of what each Power App does and who owns it. When it’s time to clean up, you’ll know who to ask.

Set app ownership: Every Power App in your Teams should have a clear owner responsible for maintaining it. When apps are orphaned, they tend to stick around long after they’re useful.

Test in a small team first: Before rolling out a Power App to multiple teams, test it in one small team. This prevents widespread cleanup headaches if the app doesn’t work out.

When to Keep vs. Remove Power Apps

Not sure whether an app should stay or go? Here’s a quick decision framework.

Keep the app if:

• It’s actively used by team members at least weekly
• It automates an important business process
• It contains historical data people need to reference
• It’s required for compliance or documentation purposes

Remove the app if:

• Nobody has used it in over a month
• The project or initiative it supported is complete
• There’s a better tool or app that replaced it
• It’s causing technical issues or confusion
• It was created for testing and never fully implemented

When in doubt, ask your team. Send a quick message asking if anyone still needs the app. If nobody responds or cares, that’s your answer.

Wrapping Up

Removing Power Apps from Teams doesn’t have to be complicated. Whether you’re cleaning up your personal workspace or managing apps for your entire team, the process is straightforward once you know where to look.

Remember the key points:

• Personal apps can be uninstalled with a simple right-click
• Team and channel apps require the right permissions to remove
• Removing an app from Teams doesn’t delete the underlying data
• Regular cleanup keeps your Teams workspace organized and efficient

Start with your personal app bar, then move to any teams you manage. You’ll be surprised how much cleaner and faster Teams feels when you’re not wading through unused apps.

And if you ever need an app back, you can always reinstall it from the Teams app store or Power Apps. Microsoft’s Remove an app in Microsoft Teams page covers the same paths if you want the official reference. Nothing is permanent, so don’t be afraid to experiment with what works best for your workflow.

Still tidying up Teams? These guides are worth a look next:

• Want a cleaner chat list too? See Microsoft Teams chat view settings.
• If Teams itself is acting up, try these fixes for Microsoft Teams not working.
• Prefer automation over apps? Here’s how to build a Power Automate flow with Microsoft Teams.

I’ve seen people use them interchangeably, ignore one entirely, or accidentally create duplicate workspaces because they didn’t understand how the two connect. So in this tutorial, I’m going to break down Microsoft Teams vs Microsoft 365 Groups — what each one is, how they relate to each other, and which one you should actually use for what.

Let’s start from the beginning.

What Is a Microsoft 365 Group?

Think of a Microsoft 365 Group as a behind-the-scenes membership container. When you create a Group, you’re essentially creating a list of people and automatically giving them access to a shared set of resources — without you having to manually set permissions for each tool.

Here’s what gets created automatically when you set up a Microsoft 365 Group:

• A shared inbox in Outlook (email sent to the group’s address lands in one place, and every member can read and reply to those group conversations)
• A shared calendar that all members can access (here’s how to create a shared calendar in Microsoft Teams)
• A SharePoint team site for storing and collaborating on documents
• A OneNote notebook for shared notes
• A Planner plan for task management

So in a nutshell, a Microsoft 365 Group is the plumbing underneath your collaboration tools. It’s the backbone that connects your people to the right resources across the Microsoft 365 suite.

You can create a Microsoft 365 group on its own, without Teams, right from Outlook on the web. In the Groups view, open the New group drop-down and pick New group (the same menu also has New mail and New event):

The New group form asks for a name, an email address, a description, a sensitivity label (if your organization uses them), and a Privacy setting. I filled it in with a demo name and then clicked Discard, because a real group gets its own inbox, calendar, SharePoint site, and Planner right away:

A quick real-world example: Let’s say you have a Marketing team. You create a Microsoft 365 Group called “Marketing Team.” Everyone added to that group now automatically gets access to the shared inbox, the SharePoint documents, the Planner board, and the calendar — all in one go. You didn’t have to go into SharePoint and add each person manually, or set up Planner from scratch. It just happens.

What Is Microsoft Teams?

Microsoft Teams is a real-time communication and collaboration platform. If you’ve ever used Slack, Teams is Microsoft’s answer to that — but with a lot more built in.

With Teams, you get:

• Chat — instant messaging, both one-on-one and in groups
• Channels — organized conversation spaces within a team (more on this in a moment)
• Video and audio calls — for meetings, check-ins, and full-blown conferences
• File sharing — share and co-edit documents right inside the app
• App integrations — add tabs for things like Power BI, Planner, websites, or third-party tools (see how this works in Microsoft Teams for project management)

Teams is the front-end, visible workspace where people actually work day to day. It’s where your conversations happen, your meetings run, and your files are shared in context.

How Do They Actually Relate to Each Other?

This is the part that trips most people up. Here’s the key thing to understand:

Every time you create a Microsoft Team, a Microsoft 365 Group is automatically created behind the scenes.

You don’t see it happening. You don’t have to do anything. But Microsoft is quietly setting up that Group to handle the membership and shared resources that Teams needs to function. (If you haven’t built one yet, here’s how to create a team in Microsoft Teams.)

So when you create a team called “Project Phoenix,” Microsoft also:

• Creates a Microsoft 365 Group called “Project Phoenix”
• Spins up a SharePoint site for document storage
• Creates a group mailbox (hidden from Outlook by default when the team is created in Teams; groups created in Outlook or SharePoint stay visible there)
• Sets up a OneNote notebook

You can see this on my SPGuides demo team. Its SharePoint site shows a Teams icon next to the site name, and the left navigation has Conversations, Notebook, and Calendar links. Those come from the Microsoft 365 group, not from Teams:

To jump from a team to that site, open any channel’s Shared tab, select More options (…) in the toolbar, and choose Open in SharePoint. Each standard channel is just a folder in that site’s document library:

Think of it this way: Microsoft 365 Groups is the engine, and Microsoft Teams is the car. You interact with the car every day. You rarely think about the engine — but it’s doing all the hard work underneath.

And here’s something else worth knowing: if you already have a Microsoft 365 Group and want to upgrade it to a full Teams workspace, you can do that. In Teams, select New items above your chat and channel list, then New team > More create team options > From group. Pick the group and select Add team. Teams warns you that this permanently adds Teams to the existing group.

You’ll only see groups you own that aren’t already connected to a team and have fewer than 10,000 members. The new team keeps the group’s name, privacy, sensitivity, and members, and you become its owner. Your existing inbox, files, and calendar stay right where they are.

Microsoft Teams vs Microsoft 365 Groups: Side-by-Side

Let me put the key differences in a simple table so you can see them at a glance:

What Are Channels in Teams?

Since Channels keep coming up, I want to take a moment to explain them clearly — because they’re a unique feature that Groups simply doesn’t have.

Inside every Microsoft Team, you have Channels. A channel is a dedicated space for conversations around a specific topic, project, or workstream. For a deeper look, see Microsoft Teams team vs channel.

For example, imagine you’re managing a software development team. Your Team might have channels like:

• General — for announcements and broad updates
• Frontend Dev — where frontend developers discuss their work
• Bug Reports — where the team logs and discusses issues
• Releases — for coordinating deployments

Each channel has its own conversation thread, its own Shared tab for files (older versions of Teams called it Files), and you can even pin custom tabs to it (like a specific document, a Power BI report, or a website). Standard channels store their files in the team’s SharePoint site, while a private channel gets its own separate site.

Here’s the thing — Groups doesn’t have this concept at all. With a Group, everything goes into one shared inbox and one shared document library. There’s no way to break things down into topics the way channels let you.

So if your team communicates heavily and works across multiple workstreams, Teams with channels is going to be far more organized and useful.

When Should You Use Microsoft 365 Groups?

Microsoft 365 Groups work well in specific scenarios. Here’s where they really shine:

• Email-based communication — If your team’s primary collaboration style is still email, a Group gives everyone a shared inbox and address.
• Distribution lists — You need to email a set of people regularly (e.g., hr-team@yourcompany.com).
• Light collaboration — Teams that just need shared access to documents and a calendar without needing real-time chat.
• Background infrastructure — When IT admins need to manage permissions and shared resources for a set of users without building out a full Teams workspace.

Groups are essentially ideal when the work doesn’t need a dedicated real-time workspace, but the team still needs common access to resources.

When Should You Use Microsoft Teams?

Teams is the right choice when you need an active, dynamic collaboration space. Use Teams when:

• Your team works in real-time — you need fast replies, quick decisions, and live coordination
• You have multiple projects or workstreams — channels let you keep everything organized and separate
• You run regular meetings — Teams has native meeting scheduling, joining, recording, and transcription
• You need app integrations — you want to pull in tools like Planner, Power BI, or third-party apps into your workspace
• You’re working with remote or hybrid teams — video calls, screen sharing, and async chat all live in one place

For most modern teams doing actual day-to-day work, Teams is the better home base.

Managing Membership: What You Need to Know

Here’s a practical tip that a lot of people miss. Because Teams is built on top of a Microsoft 365 Group, the membership is shared. So if you add or remove someone in Teams, they’re also added or removed from the underlying Group.

But here’s the catch: if you add or remove someone directly from the Group (via the Microsoft 365 admin center, Microsoft Entra ID, or Exchange Online PowerShell), it can take up to 24 hours for that change to show up in Teams. On the other hand, if you make the change inside Teams itself, it updates much faster.

So the best practice? Always manage your team membership from inside Microsoft Teams — not from the admin center — to make sure everything stays in sync quickly.

In Teams, hover over the team name, select More options (…), and choose Add member. The same menu has Manage team for the full member list and roles, and Delete team, which matters for the next section:

Also, if you remove someone from a Team, they lose access to the SharePoint site, the Planner board, and other connected resources almost immediately. The one small exception is that they may still see the Teams chat for about two hours after removal. That’s just how the backend sync works.

Deleting a Team vs Deleting a Group

This is another area where people get caught off guard.

• If you delete a Team in Microsoft Teams, it disappears immediately from everyone’s view. The channel conversations, files, and the team’s SharePoint site go with it, because deleting the team deletes the Microsoft 365 group behind it.
• If you delete the underlying Microsoft 365 Group, it also removes the shared mailbox, marks the SharePoint site for deletion, and removes Teams meeting invites. This process takes about 20 minutes to fully propagate.

The good news is that there’s a 30-day soft-delete window — both Groups and Teams can be restored within 30 days before they’re permanently gone. So if someone accidentally deletes a team, don’t panic. An admin can restore the Microsoft 365 group (in the Microsoft 365 admin center under Teams & groups > Deleted groups), and the team comes back with its channels and tabs. It can take up to 24 hours for a restored team to show up in Teams. If you’re not sure a team is finished, archive it instead, since archived teams can be reactivated anytime. Microsoft explains the details in its Microsoft 365 Groups and Microsoft Teams guide.

A Quick Recap: Which One Should You Use?

Here’s my honest take:

• If you’re just setting up shared access to email and files for a group of people → Microsoft 365 Group is enough.
• If your team needs to communicate, collaborate, meet, and work together daily → Microsoft Teams is what you want.
• If you’re already using Microsoft 365 Groups and want to level up → Add Teams to your existing Group. You don’t have to start over.

And remember — behind every Team, there’s a Group doing the heavy lifting. They’re not competitors. They’re partners. Teams just makes the whole experience visible, organized, and a lot more practical to work in.

Want to keep going? These guides pick up where this one stops:

• Wondering where SharePoint fits in? Read Microsoft Teams vs SharePoint.
• Ready to work with files in your new team? Here’s how to share files in Microsoft Teams.

The good news? Once you know where to look, it’s pretty straightforward to move files from OneDrive to Microsoft Teams. In this tutorial, I’ll walk you through multiple methods so you can pick whichever one fits your situation best.

Before We Start: Understanding How OneDrive and Teams Connect

Here’s something worth knowing first: OneDrive and Microsoft Teams are not two separate islands. They’re deeply connected in Microsoft 365.

When you share a file inside a Teams channel, it actually gets stored in a SharePoint document library behind the scenes. When you share a file in a Teams chat, it gets stored in your OneDrive. So when you “move” a file from OneDrive to Teams, what you’re really doing is moving it from your personal OneDrive folder to a shared Teams/SharePoint location where everyone on the team can access it.

In the new Teams, Microsoft has also made OneDrive the central file hub inside Teams itself. The old Files app in the app bar has been replaced by the OneDrive app, so when you open it, you’re looking at the same OneDrive you see in a browser — just with better team collaboration layers on top.

Why does this matter? Because once you move a file to a Teams channel, everyone in that channel can see and edit it. No more sending email attachments back and forth. Everyone works from the same file, and no duplicates pile up. (For the bigger picture, here’s how to share files in Microsoft Teams in channels and chats.)

Method 1: Move Files Directly from OneDrive Web App

This is my favorite method when I need to move multiple files at once and want full control over where they land.

Steps:

1. Open OneDrive in your browser (go to onedrive.com) and sign in with your Microsoft 365 work or school account.
2. Find the file or folder you want to move. You can select multiple files by checking the circle that appears on the left of each file when you hover.
3. Right-click on the file (or click the three-dot menu that appears on hover).
4. Select Move to.
5. The Move to dialog opens. Under Quick access on the left, you’ll see the sites you use, including your Teams sites. Each Microsoft Teams team has a connected SharePoint site, and it appears in this list. If a team is missing, make sure you’re a member of it; if no other sites show up at all, your organization doesn’t allow moving files across sites.
6. Click the Team you want to move the files to. You’ll then see an In channels section with a folder for each channel (General, Project A, etc.), above the rest of the site library.
7. Navigate into the right channel folder.
8. Click Move here.

Here’s what that looks like with a demo file. I right-clicked SPGuides Launch Checklist 2026.docx in my OneDrive, and the menu shows both Move to and Copy to:

In the Move to dialog, I picked the SPGuides team site under Quick access, and the General channel folder showed up under In channels:

Inside the General folder, the breadcrumb confirms where the file will land. Then it’s just Move here:

That’s it. The file disappears from your personal OneDrive and lands in the Teams channel you selected. Open the channel’s Shared tab and you’ll see it there:

One thing to know: only the file properties that the destination library supports come along with the file. If the team’s library keeps fewer versions than your OneDrive, you’ll get a warning before the move, and you can choose to move anyway.

Pro tip: If you’re not sure which folder belongs to which channel, the folder names usually match the channel names exactly. The “General” channel, for example, will have a “General” folder.

Method 2: Move Files from Inside Microsoft Teams

You can also do this entirely within the Teams app — no need to open OneDrive in a browser separately.

Steps:

1. Open Microsoft Teams (desktop app or web).
2. On the left app bar, click the OneDrive icon (in the new Teams it replaced the old Files app).
3. You’ll land on My files — this is your personal OneDrive storage.
4. Hover over the file you want to move. A check circle will appear on the left — click it to select it.
5. Click the three-dot menu (More options) that appears.
6. Select Move to.
7. The same Move to dialog opens. You can choose:
   • My files — to move it to a different folder within your OneDrive
   • Quick access — pick the team’s site to move it to a specific Teams channel
8. Select the Team, then the channel folder under In channels.
9. Click Move here.

This method is great if you’re already working inside Teams and don’t want to switch tabs or open a browser.

Note: You can also select multiple files before hitting “Move to.” Just check each file using the circle on the left, then click “More options” on any one of them and proceed.

Method 3: Upload Files to a Teams Channel Directly

Sometimes you don’t need to “move” a file — you just want to get it into Teams quickly, and keeping the original in OneDrive is fine. In that case, you can upload it directly.

Steps:

1. In Microsoft Teams, navigate to the Team and Channel you want to upload the file to.
2. Click the Shared tab at the top of the channel (older versions of Teams called it Files).
3. Click Create or upload in the top toolbar.
4. Select Files upload from the menu (or Folder upload if you want to upload an entire folder).
5. Your file explorer opens. Navigate to your local machine or OneDrive sync folder and pick the file.
6. Click Open and the file uploads to that channel.

This creates a copy of the file in Teams. If you want to remove the original from OneDrive after this, you’d need to do that manually. So this method works best if you’re okay with having copies in both places, or if the original is already on your desktop/local machine (synced from OneDrive).

Method 4: Share a OneDrive File Link in Teams (When You Don’t Want to Move It)

Here’s a method people often overlook — and honestly, sometimes it’s the right answer. Instead of physically moving the file, you share a link to it inside Teams.

This means:

• The file stays in your OneDrive.
• Everyone in Teams can access it through the link.
• You’re all editing the same file — no duplicates.

Steps:

1. In Teams, open a chat or a channel.
2. Start a message (in a channel, select Post in channel first), then click the Attach file paperclip icon under the message box. In some layouts it sits under Actions and apps (+).
3. Select Attach cloud files to pick from OneDrive (or Browse Teams and Channels for a file that’s already in a team).
4. Browse to the file you want to share and select it.
5. If Teams asks whether to Share a link or Upload a copy, choose Share a link.
6. Click Send (or Post in a channel).

The file appears in the chat or channel as a clickable link. Anyone in the conversation can open it directly from their browser or Teams — and they’ll be editing the live version in OneDrive.

This is the approach Microsoft actually recommends for collaboration. It keeps your file in one place and prevents the classic problem of three people each working on “ProjectPlan_FINAL_v3_reallyFinal.xlsx.”

Method 5: Drag and Drop via File Explorer (Sync Method)

If you have the OneDrive desktop sync client installed, your OneDrive folders show up in Windows File Explorer like regular folders. And if your Teams channels are also synced to File Explorer (which they can be), you can literally drag and drop files from one folder to another.

To sync a Teams channel to File Explorer:

1. Go to the Teams channel.
2. Click the Shared tab.
3. Click More options (…) in the toolbar, then Sync.
4. A sync confirmation will appear — click Open Microsoft OneDrive or follow the prompts.
5. The channel’s folder will now appear under your organization’s name (the building icon) in File Explorer.

You’ll also see Add shortcut to OneDrive in the same toolbar. It adds the channel folder to your OneDrive, so it shows up and syncs inside your OneDrive folder in File Explorer, which works just as well for drag and drop.

Now to move files:

1. Open File Explorer.
2. On the left, you’ll see your personal OneDrive (under your name) and the synced Teams/SharePoint folders.
3. Simply drag the files from your OneDrive folder into the Teams channel folder.

This is probably the most natural way for people who prefer working in File Explorer rather than the browser. It feels like moving files between folders on your own computer — because it basically is.

Which Method Should You Use?

Here’s a quick way to think about it:

• Moving a lot of files at once? → Use Method 1 (OneDrive web app) or Method 5 (File Explorer sync).
• Already inside Teams and moving one or two files? → Use Method 2 (move from within Teams).
• Just want teammates to access the file without actually moving it? → Use Method 4 (share a link).
• Uploading fresh files that aren’t in OneDrive yet? → Use Method 3 (direct upload to Teams channel).

A Few Things to Keep in Mind

• Permissions update automatically. Once a file is in a Teams channel, everyone in that channel has access to it. You don’t need to set individual permissions.
• Moving is permanent (in Teams terms). When you “Move to” a Teams channel, the file leaves your personal OneDrive. It won’t show in “My files” anymore. You’ll find it under the Teams channel’s Shared tab.
• Copying is different from moving. Teams gives you both options — “Move to” and “Copy to.” If you’re unsure and want to keep the original safe while testing, use “Copy to” first. (A copy in the same tenant isn’t a real backup, though; here’s how to back up Microsoft Teams files properly.)
• Channels = folders in SharePoint. Each Teams channel has a corresponding folder in a SharePoint document library. What you see in the Teams Shared tab is literally that SharePoint folder. Private and shared channels are the exception: each one has its own separate SharePoint site, so a private channel appears as its own site in the Move to dialog. For more on how the two apps fit together, see Microsoft Teams vs SharePoint.
• Co-authoring works after the move. Once the file is in a Teams channel, multiple people can open and edit it at the same time — Word, Excel, PowerPoint all support real-time co-authoring in Microsoft 365.

Final Thoughts

Moving files from OneDrive to Microsoft Teams is honestly one of those things that sounds more complicated than it is. Once you understand that Teams channels are backed by SharePoint folders — and that your personal OneDrive is just another connected storage location — the whole thing clicks into place.

My recommendation for most people: use the OneDrive web app (Method 1) for bulk moves, and use the “share a link” approach (Method 4) for day-to-day collaboration. That way you’re keeping your file management clean and your team working from a single source of truth.

Want to keep going with Teams files? These guides pick up where this one stops:

• Not sure which channel a file belongs in? Learn the difference between a team and a channel in Microsoft Teams.
• Wrapping up a project? Here’s how to archive files in Microsoft Teams.

Microsoft keeps your data available as long as your subscription is active, but it doesn’t protect you from accidental deletion, a disgruntled team member wiping files, or ransomware. That responsibility falls on you (or your IT admin).

In this tutorial, I’ll show you how to backup Microsoft Teams files with every practical method — from the simplest manual download to setting up retention policies in the Microsoft Purview portal. Let’s get into it.

First, Understand Where Teams Stores Your Files

Before you back anything up, you need to know where Teams actually keeps your files. Spoiler: Teams itself doesn’t store files. It uses two other Microsoft services under the hood.

Here’s how it breaks down:

• Channel files — Any file you upload or share inside a Teams channel is stored in a SharePoint document library. Each team gets its own SharePoint site, and each standard channel gets its own folder inside that site. Private and shared channels are the exception: each one gets its own separate SharePoint site. (If you’re new to this, here’s how to share files in Microsoft Teams in channels and chats.)
• Chat files — Files you share in a one-on-one or group chat go into your OneDrive for Business, inside a folder called “Microsoft Teams Chat Files.”
• Meeting recordings — These are stored in the organizer’s OneDrive (for regular, non-channel meetings) or the channel’s SharePoint folder (for channel meetings).
• Wiki content — Classic wiki tabs have been retired, but old wiki pages (and any OneNote notebooks they were exported to) still sit in the team’s SharePoint site.

This is actually good news. It means you can back up your Teams files by going directly to SharePoint or OneDrive. You don’t always have to dig around inside Teams itself. For a deeper look at how the two apps fit together, see Microsoft Teams vs SharePoint.

Method 1: Manually Download Files from Teams

This is the most straightforward approach if you just need a quick one-time backup. It takes a few minutes and requires no admin access.

For channel files:

1. Open Microsoft Teams and go to the channel you want to back up.
2. Click the Shared tab at the top of the channel (older versions of Teams called it Files).
3. Select the files or folders you want to download (click the circle next to each name to select several at once).
4. Click the Download button (or right-click and choose Download). If you picked more than one item, you get a single .zip file.
5. Save the files to your local drive or an external hard drive.

Once you select files, the toolbar switches to file actions, including Download and Copy to (more on that one in Method 3):

For chat files:

1. Open the chat conversation where files were shared.
2. Click the Shared tab at the top of the chat (older versions called it Files).
3. Select and download the files you need.

The catch: This is a one-time process. If you add new files tomorrow, they won’t be included in this backup. It’s useful when you archive files in Microsoft Teams at the end of a project, but not as an ongoing strategy.

Method 2: Sync Teams Files to Your Local PC via OneDrive

This is one of my favorite methods because it works automatically once you set it up. Since Teams channel files are stored in SharePoint, you can sync that entire SharePoint library to your computer using the OneDrive sync client.

Here’s how to do it:

1. Go to the Teams channel whose files you want to sync.
2. Click the Shared tab.
3. Click the Sync button in the toolbar (you may need to click the three-dot menu to find it).
4. If prompted, click Open Microsoft OneDrive to confirm.
5. The files will now appear in a local folder on your PC under your company’s OneDrive sync folder.

Once synced, you’ll always have a local copy of all those channel files on your machine. Any changes made in Teams automatically reflect on your PC, and vice versa.

Pro tip: You can also open the channel files in SharePoint directly by clicking Open in SharePoint inside the Shared tab, then hitting the Sync button from there. This gives you more control over which folders you sync. You’ll also see Add shortcut to OneDrive; it adds the folder to your OneDrive so it syncs along with your own files, and it’s the same two-way connection.

One important warning: If you delete a synced file from your local folder, it gets deleted from Teams and SharePoint too. So don’t treat the sync folder as a “safe local archive” — it’s a two-way mirror, not a backup.

To keep a true local backup, copy files from your sync folder to a separate folder that is not inside your OneDrive sync path.

Method 3: Back Up Files via SharePoint (For Channel Files)

Since channel files live in SharePoint, you can go straight to SharePoint to download or manage them. This is especially useful for admins who want to back up an entire team’s file library.

Steps:

1. In Teams, go to the channel and click the Shared tab.
2. Click Open in SharePoint (in the top toolbar or the three-dot menu).
3. You’ll land on the SharePoint document library for that channel.
4. Select all files and folders you want to download.
5. Click Download — SharePoint will zip everything into a single .zip file for you (one download can include up to 10,000 files).
6. Save that zip file to your backup location.

Here’s the same channel folder opened in SharePoint, with three files selected and ready to download:

Want a second copy that stays in the cloud? Select the files and use Copy to to copy them into another SharePoint library or your OneDrive. It isn’t a true backup, because the copy lives in the same tenant, but it does protect you if someone deletes or overwrites the originals.

For a full team backup, go to the root of the SharePoint site (not just one channel folder) and download the entire Documents library at once. Remember that private and shared channels have their own sites, so download those separately.

Admin tip: You can also use SharePoint’s built-in Recycle Bin as a short-term recovery tool. Deleted files stay in the recycle bin for 93 days. So if someone accidentally deletes a file, you can restore it without needing a formal backup — as long as you catch it within that window.

Method 4: Back Up Chat Files via OneDrive

Chat files are a bit different since they live in each user’s OneDrive rather than SharePoint. Here’s how to get to them:

1. Open OneDrive (select the OneDrive icon in the Teams app bar, or go to onedrive.com) and sign in with your work account.
2. Look for a folder called Microsoft Teams Chat Files.
3. Select the files you want to back up.
4. Click Download.

If you’re an admin trying to back up files from a departing employee’s account, you’ll need to access their OneDrive before their account is deleted. When the account is deleted, the user’s manager gets access by default, and the OneDrive is kept for 30 days (admins can raise that retention period in the SharePoint admin center). After that, it moves to the recycle bin for 93 days, where only an admin can restore it with PowerShell.

Method 5: Use Microsoft Purview Retention Policies (Admin Method)

This is the proper enterprise-grade way to protect Teams data, and it’s what IT admins should be using. Retention policies don’t create a “backup” you can download, but they prevent data from being permanently deleted — which is often what you actually need.

Here’s how to set one up:

1. Sign in to the Microsoft Purview portal at purview.microsoft.com.
2. Select Solutions → Data Lifecycle Management → Policies → Retention policies.
3. Select New retention policy.
4. Give the policy a name (e.g., “Teams Files Retention”).
5. Choose a Static policy, then on the locations page turn on:
   • Microsoft 365 Group mailboxes & sites (standard channel files and channel meeting recordings)
   • SharePoint classic and communication sites (the separate sites for private and shared channels)
   • OneDrive accounts (chat files and recordings of regular meetings)
6. Set your retention period — for example, retain data for 5 years.
7. Click through and save the policy.

Once active, even if someone deletes a file from Teams, a copy is kept in the Preservation Hold Library in SharePoint behind the scenes. An admin can recover it from there, or find it with an eDiscovery search in the Purview portal. A new policy can take up to seven days to apply.

PowerShell alternative: If you prefer scripting it, you can use this command in PowerShell (after installing the ExchangeOnlineManagement module, which gives you Security & Compliance PowerShell):

Connect-IPPSSession
New-RetentionCompliancePolicy -Name "Teams Backup" -SharePointLocation All -ModernGroupLocation All -OneDriveLocation All
New-RetentionComplianceRule -Name "Teams Backup Rule" -Policy "Teams Backup" -RetentionDuration 1825 -RetentionComplianceAction Keep

This creates a policy that keeps every file in your SharePoint sites, Microsoft 365 group sites (where standard channel files live), and OneDrive accounts for five years (1,825 days). The Teams channel message and chat locations cover messages only, not files, and they need a policy of their own. If you want a copy of the conversations themselves, see how to export Microsoft Teams chat history using PowerShell.

Note: Retention policies need a license that includes Microsoft Purview data lifecycle management, such as Microsoft 365 E3, E5, or Business Premium.

Method 6: Use Microsoft 365 Backup (Native Admin Tool)

Microsoft 365 Backup is Microsoft’s native backup service, managed directly in the Microsoft 365 admin center. It backs up SharePoint sites (and so Teams channel files), OneDrive accounts, and Exchange mailboxes, with point-in-time restore.

How to check if it’s available for your tenant:

1. Sign in to the Microsoft 365 admin center at admin.microsoft.com.
2. The first time, set up pay-as-you-go billing for Microsoft 365 Backup with an Azure subscription (under Billing in the admin center).
3. Go to Settings → Microsoft 365 Backup.
4. If it’s enabled on your tenant, you can set up backup policies for SharePoint sites and OneDrive accounts.

This tool lets you restore to a specific point in time, which is a game changer for ransomware scenarios. Restore points go back one year by default, and you can set the window anywhere from three months to two years. Keep in mind it’s billed pay-as-you-go through an Azure subscription, based on how much data you protect — it’s not included in any Microsoft 365 plan. You need to be a SharePoint Administrator, Microsoft 365 Backup Administrator, or Global Administrator to set it up.

Method 7: Use a Third-Party Backup Tool

If you want set-it-and-forget-it automated backups without managing retention policies yourself, third-party tools are worth considering. Some popular options include:

• Veeam Backup for Microsoft 365 — Well-known for enterprise use, supports granular restore of Teams data.
• MSP360 — Good for managed service providers managing multiple tenants.
• CloudAlly — Simple interface, supports scheduled backups and point-in-time recovery.
• SysCloud — Strong compliance features and ransomware alerts.

These tools typically connect to your Microsoft 365 tenant via the Microsoft Graph API, pull a copy of your Teams data (files, messages, and sometimes meeting recordings), and store it in their own cloud storage or a location of your choice.

The biggest advantage: automation. You schedule backups, they run in the background, and you can restore individual files, channels, or entire teams with a few clicks.

The downside: They cost money, and you’re trusting a third party with your data. Make sure whatever tool you choose supports end-to-end encryption and complies with your industry’s data regulations.

What About Meeting Recordings?

Meeting recordings don’t get backed up through the file methods above because they’re stored separately. Here’s how to handle them:

• Channel meeting recordings are stored in the SharePoint document library of that channel, under a Recordings folder. You can back these up using the SharePoint download method above.
• Recordings of regular (non-channel) meetings go to the organizer’s OneDrive in a Recordings folder.

To download a recording manually, go to the relevant OneDrive or SharePoint location, find the recording file (it’ll be an .mp4), and download it. Here’s the full walkthrough to download a Microsoft Teams recording.

Quick Comparison: Which Method Should You Use?

A Few Things to Keep in Mind

• Deleted Teams and channels: When you delete a team, its Microsoft 365 group stays soft-deleted for 30 days. An admin can restore the group within that window (from the Microsoft 365 admin center or with PowerShell), which brings back the team, its channels, and its files.
• Test your backups: Whether you’re using a retention policy or a third-party tool, test the restore process at least once a quarter. A backup you’ve never tested is just hope dressed as a plan.
• Departing employees: When someone leaves, archive or transfer their OneDrive data before deleting their account. Microsoft gives you 30 days, but don’t cut it close.
• External shared files: Files shared with guests or external users may behave differently depending on your tenant’s sharing settings. Double-check that your backup includes files in shared and private channels too, since each of those channels has its own SharePoint site.

Want to keep going with Teams files and recordings? These guides pick up where this one stops:

• Not sure where to put a file? Learn the difference between a team and a channel in Microsoft Teams.
• Recording meetings you’ll need later? Here’s how to record a Microsoft Teams meeting.
• Cleaning up old recordings? See how to delete a meeting recording in Microsoft Teams.

In this tutorial, I’ll answer does Microsoft Teams notify screenshots for chats, meetings, and company devices, and show what Teams Premium can do to block captures.

The Short Answer

No, Microsoft Teams does not notify anyone when a screenshot is taken. There’s no pop-up, no alert, and no log entry saying “John took a screenshot at 3:12 PM.” Whether you use the Windows Snipping Tool, a keyboard shortcut, or a third-party screen capture app, Teams won’t detect or report it. (Here’s every way to take a screenshot in Microsoft Teams on desktop and mobile.)

That said — things are changing. Microsoft has now rolled out a Teams Premium feature called Prevent screen captures that can actually block screenshots rather than notify about them. More on that below.

Why Teams Doesn’t Notify Screenshots

This isn’t an oversight on Microsoft’s part. It’s a deliberate design choice.

Teams is built as an enterprise collaboration tool, and taking screenshots of your own screen is considered a local device action. The Teams app doesn’t have access to your operating system’s screenshot mechanisms — it can’t “listen” for them the way an app like Snapchat does on mobile.

Microsoft’s privacy policy also plays a role here. The platform is designed to not monitor or log what users do on their own devices outside of Teams’ own activity logs. So even from a compliance standpoint, screenshot detection was never part of the roadmap for the standard Teams product.

The only capture alert you’re likely to see comes from your own Mac, and it’s about Teams sharing your screen, not about screenshots. If that pop-up confuses you, see what it means when Microsoft Teams is capturing your screen.

Does Teams Notify Screenshots in Chats?

No. If someone takes a screenshot of your Teams chat — whether it’s a private message or a group conversation — you won’t get any notification. There’s no read receipt style alert for screenshots, no banner, nothing.

This applies to:

• Direct messages (DMs) between two people
• Group chats with multiple participants
• Channel conversations inside a Teams workspace
• Files and documents shared in chat

So if you shared something sensitive in a Teams chat, anyone reading it could screenshot it without you ever knowing.

Does Teams Notify Screenshots in Meetings?

Same answer — no. During a Teams meeting, participants can take screenshots freely using any method they like, and no one in the meeting gets notified.

This includes:

• Windows Snipping Tool (Win + Shift + S)
• Print Screen key (PrtScn)
• Mac screenshot shortcut (Cmd + Shift + 4)
• Android and iPhone screenshots on the mobile Teams app
• Third-party tools like Snagit or Lightshot

The meeting keeps running, the other participants see nothing unusual, and there’s no timestamp or log of the capture in Teams.

Can Your IT Admin or Organization See If You Took a Screenshot?

This one is a bit different, and it depends on how your organization manages devices.

If you’re using a personal device, your IT admin generally cannot see if you took a screenshot. Teams doesn’t report that information to the admin center.

However, if you’re on a company-managed device — one enrolled in Microsoft Intune or another MDM (Mobile Device Management) solution — the situation changes. IT admins can configure device-level policies through Intune that:

• Block screenshots entirely on Android and iOS devices
• Enforce app protection policies that prevent screenshots from being taken within managed apps (the app protection setting for this is on Android)

So the question isn’t really “does Teams detect screenshots?” — it’s “does your device management policy allow screenshots at all?”

If your phone is managed by your company’s IT department and they’ve set a policy to block screenshots in managed apps, you’ll find that any screenshot attempt on the Teams app just captures a blank or black screen. You won’t necessarily get an error message, but the screenshot simply won’t contain the Teams content.

The Big New Feature: Prevent Screen Capture (Teams Premium)

This is the most important update to know about right now.

Microsoft rolled out a Prevent Screen Capture feature as part of Microsoft Teams Premium, the paid add-on license for Teams. This is a significant change from the “no screenshot control” status quo.

Here’s what it does and how it works:

What the Feature Does

When a meeting organizer enables this setting, anyone who tries to screenshot during that meeting gets a black rectangle where the meeting window should be (on Windows), or the capture is blocked outright (on iPhone and Android). Microsoft says it works against built-in device tools and most third-party capture apps. It can’t stop someone from pointing a phone camera at the screen, though.

It doesn’t notify anyone that a screenshot was attempted — it just blocks the content from showing up in the capture.

How It Behaves on Different Devices

This is genuinely useful for high-stakes meetings — things like legal discussions, finance briefings, or HR conversations where sensitive information is on screen.

Who Can Enable It?

Only meeting organizers or co-organizers can turn this on, and they need a Teams Premium license to do so. Attendees don’t need Premium — only the organizer does.

Attendees on unsupported platforms (Teams on Mac desktop, Teams on the web, and virtual desktops) are automatically shifted to audio-only mode when this feature is on. That’s Microsoft’s way of saying: “If we can’t protect the content on your device, you don’t get to see the video feed.”

How to Turn It On

Enabling it is pretty straightforward:

1. Open your Teams Calendar
2. Open the meeting you want to protect
3. Select Options
4. Go to Advanced protection
5. Turn on the Prevent screen captures toggle
6. Select Apply

That’s it. The setting applies for that specific meeting. It is off by default and has to be enabled manually per meeting — it doesn’t apply globally to all meetings by default. Turn it on before the meeting starts; if you switch it on mid-meeting, it only takes effect after everyone leaves and rejoins. It works for private scheduled meetings, not town halls.

Without a Teams Premium license, you won’t see Advanced protection at all. Here’s Meeting options in our SPGuides tenant, which has no Premium license: the left menu goes straight from Participation to Recording & transcription, Copilot and other AI, and Accessibility.

While you’re in Options, it’s worth knowing how automatic recording in Microsoft Teams works too, since that section sits right there.

Other Privacy Tools in Teams Worth Knowing

Even if you’re not on Teams Premium, there are a few other things worth knowing about protecting your content:

• Watermarks (Teams Premium): You can enable watermarks that overlay each participant’s email address on the shared video or screen. This doesn’t block screenshots, but it makes every capture traceable back to the person who took it. That alone tends to deter most people. Your admin turns watermarks on in a Teams meeting policy, and the organizer should switch them on before the meeting starts.
• Sensitivity Labels (Teams Premium): IT admins create sensitivity labels in Microsoft Purview, and organizers apply them to the meeting invite (the Sensitivity button in the screenshot above). A label can enforce video watermarks, block copying and forwarding of meeting chat, captions, and transcripts, limit who can record, and turn on encryption. Copy blocking doesn’t stop screen captures, though.
• Intune MDM Policies: If your organization uses Intune, admins can block screen captures on managed Android and iOS devices at the system level.
• End-to-End Encryption: Teams supports E2E encrypted one-to-one calls and meetings (meeting organizers need Teams Premium; calls don’t), which adds strong data protection during transmission. Recording, live captions, and transcription are turned off in E2EE sessions — though this doesn’t stop screenshots.

What Should You Do If You’re Worried About Screenshots?

Here’s my honest, practical take.

If you’re sharing anything sensitive in a Teams meeting, the safest assumption is that someone could screenshot it, especially if you’re on standard Teams without Premium.

A few things you can do:

• Enable Prevent Screen Capture if your org has Teams Premium — it’s the most direct solution
• Use watermarks so any screenshot is traceable
• Inform participants verbally or in writing at the start of a meeting that screenshots are not allowed — this creates accountability even if Teams doesn’t enforce it technically
• Avoid sharing documents on screen that you wouldn’t be comfortable being screenshot — share them via secure links with proper permissions instead, or share a single window in Microsoft Teams rather than your whole desktop
• Check with your IT admin if you think your company device has policies that restrict screenshots — they’ll know what’s in place

A related message confuses many users: “Microsoft Teams is capturing your screen” — that guide explains when it appears and how to stop it.

Quick FAQs

Can someone screenshot my Teams profile picture?
Yes, without any notification to you.

Does Teams notify when someone screens records a meeting?
Yes for Teams’ own recording: when someone starts a built-in recording or transcription, every participant gets a notification in their Teams desktop, web, or mobile app (see how to record a Microsoft Teams meeting). External screen recorders (like OBS or Camtasia) aren’t detected or announced.

Can the Teams admin see if I screenshotted something?
On a personal device — no. On a managed corporate device — possibly, depending on what Intune or MDM policies are in place.

Is the Prevent Screen Capture feature available for free Teams users?
No. Only organizers and co-organizers with Microsoft Teams Premium can turn it on; attendees don’t need Premium. Microsoft covers the details in Prevent screen captures in Microsoft Teams meetings.

Wrapping Up

The bottom line: standard Microsoft Teams does not notify screenshots, doesn’t detect them, and doesn’t log them. But with the Teams Premium “Prevent Screen Capture” feature now live, organizers finally have a real tool to block screen captures during sensitive meetings — not just hope that people behave themselves. If your organization deals with confidential information regularly, it’s worth a serious look at Teams Premium just for this feature alone.

If you’re tightening up privacy in Teams, these guides can help next:

• Want to review the app’s privacy options? Start with the Microsoft Teams settings that matter most.
• Need a capture of your own? Here’s how to record your screen in Microsoft Teams without a meeting.
• Already recorded a meeting? Learn how to download a Microsoft Teams recording.
• Removing something you regret posting? See how to delete chats in Microsoft Teams.

What Does This Message Actually Mean?

Let’s clear this up first, because the wording is admittedly a bit scary.

When macOS (especially Sequoia and later versions) says “Microsoft Teams is capturing your screen,” it’s using Apple’s own privacy alert system. Since macOS Monterey, Apple shows privacy indicators in the menu bar when an app uses your microphone (the orange dot) or records your screen. In macOS Sequoia, screen recording has its own purple indicator, and you can click it or open Control Center to see which app is capturing your screen.

So here’s the thing: this is macOS telling you something, not Teams doing something shady. Teams needs screen recording permission to let you share your screen during meetings. That’s completely normal and expected. If you’re new to it, this guide shows how to share your screen on Microsoft Teams step by step.

The message typically shows up in two situations:

• You’re actively sharing your screen in a Teams meeting
• Teams is running in the background and macOS still detects it has screen recording access

On Windows, you won’t see this exact notification, because Windows doesn’t announce screen sharing with a macOS-style privacy alert.

Why Does It Keep Appearing Even When You’re Not in a Meeting?

This is the part that frustrates most people. You close the meeting, maybe even quit Teams, but the notification still shows up.

Here are the most common reasons this happens:

• Teams didn’t fully quit. On Mac, clicking the red X doesn’t always close an app completely. Teams may still be running in the background as a helper process.
• macOS Sequoia is extra chatty. Starting with macOS Sequoia, Apple shows screen recording alerts and reminders more often, and the indicator can linger for a few seconds after an app stops capturing. Even if you’re intentionally sharing your screen, you’ll keep seeing reminders.
• Teams is still holding a capture session. The permission alone doesn’t trigger the alert; macOS shows it when an app actually captures the screen. If Teams or a leftover Teams helper didn’t release the capture after your share ended, the alert stays. Users on Microsoft Q&A have reported this as a Teams bug that an update or reinstall clears.
• It’s actually another app. Sometimes the alert names a different app or helper, such as a browser, a recording tool, or a security agent. Read the app name in the alert or the menu bar indicator before you blame Teams.

Fix 1 — Check and Reset Screen Recording Permissions on Mac

This is the first thing I’d try. Here’s how to do it:

1. Click the Apple menu (🍎) in the top-left corner
2. Go to System Settings
3. Click on Privacy & Security
4. Scroll down and select Screen & System Audio Recording (it’s called Screen Recording on macOS Ventura and Sonoma)
5. Find Microsoft Teams in the list
6. Toggle it off, wait a few seconds, then toggle it back on
7. Quit and reopen Teams. If the alert sticks around, restart your Mac

Why does toggling it help? It essentially resets the permission flag. macOS clears the cached state and Teams re-requests access fresh the next time you open it.

Want to stop Teams from capturing your screen at all? Leave the Microsoft Teams toggle off in that list. Teams then can’t see your screen, and you won’t be able to share it in meetings until you turn the toggle back on.

If Teams isn’t even showing up in that Screen Recording list, it means you never granted it permission. In that case:

• Open Microsoft Teams
• Try to start a screen share in any meeting (even a test meeting with yourself)
• macOS will prompt you to allow screen recording
• Click Open System Settings, then enable it from there
• Quit and reopen Teams. Microsoft notes that Teams needs a restart after you grant the permission, so you’ll drop out of the meeting and rejoin

Fix 2 — Force Quit Teams Properly on Mac

If the notification shows up after you’ve already closed a meeting, Teams is probably still running in the background.

Here’s the proper way to fully quit it:

1. Right-click the Teams icon in your Dock
2. Select Quit

Or, use Activity Monitor:

1. Open Activity Monitor (search it in Spotlight)
2. Search for “Teams” in the search bar
3. If you see any Teams processes running, click them and hit the X button to force quit
4. Confirm by clicking Force Quit

After doing this, the screen capture notification should go away within a few seconds. macOS takes a short moment to update the indicator.

There’s actually a neat workaround that many people in the Microsoft community swear by: schedule a quick meeting with yourself, share your screen for about 10 seconds, then stop the share and end the meeting. A lot of users reported the persistent indicator went away after this.

Fix 3 — Fix Screen Sharing Permission on Windows

On Windows, the message “Microsoft Teams is capturing your screen” usually doesn’t appear as a system notification. But you might still run into issues where Teams can’t share your screen, or it asks for permissions every time.

Here’s how to sort out screen sharing permissions on Windows 10 and 11:

1. Press Windows + I to open Settings
2. Go to Privacy & Security
3. Scroll to the App permissions section
4. Select Screenshots and screen recording (on recent Windows 11 builds)
5. Make sure the main toggle is on and, if Microsoft Teams is listed, that its toggle is on too

If that doesn’t help, try repairing the Teams app:

1. Go to Settings → Apps → Installed apps
2. Search for Microsoft Teams
3. Click the three-dot menu and select Advanced options
4. Scroll down to find Repair
5. Click Repair and restart Teams

Repair fixes the app without touching its data. If that doesn’t help, select Reset on the same page. Reset deletes the app’s local data, so you’ll sign in again, and it’s the way Microsoft suggests to clear the new Teams cache on Windows.

Fix 4 — Clear the Teams Cache

Clearing the cache is one of those all-purpose fixes that solves a surprising number of Teams problems. A bloated or corrupted cache can cause Teams to misbehave — including holding onto screen recording state when it shouldn’t.

On Mac:

1. Quit Teams completely (use Activity Monitor to be sure)
2. Open Finder
3. Press Cmd + Shift + G, go to ~/Library/Group Containers/, and move the UBF8T346G9.com.microsoft.teams folder to the Trash
4. Do the same for ~/Library/Containers/com.microsoft.teams2 (Teams rebuilds both folders the next time it starts)
5. Reopen Teams and sign in again

On Windows:

1. Close Teams
2. Press Windows + R, type %userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams and hit Enter (classic Teams used %appdata%\Microsoft\Teams)
3. Delete all files and folders inside
4. Reopen Teams

After clearing the cache, Teams essentially starts fresh. It re-downloads its local data and the permission issues often disappear. For screenshots of every step, see how to clear Microsoft Teams cache.

Fix 5 — Update Microsoft Teams

This sounds obvious, but it’s worth checking. An outdated Teams build is a common cause of stuck screen capture alerts on macOS Sequoia, and updates fix these bugs.

To update Teams:

• Select Settings and more (…) next to your profile picture at the top of Teams
• Go to Settings → About Teams
• Check your version there. New Teams updates itself, and when an update is ready a banner appears at the top: select Update → Update and restart Teams

If you’re on the new Teams (which most people are by now), updates happen in the background. But it’s still good to check, especially if you’ve been ignoring that “update available” notification for a while.

Fix 6 — Reinstall Microsoft Teams

If nothing above works, a fresh reinstall is your best option. (If Teams won’t even open or load, start with why Microsoft Teams is not working instead.) Here’s how to do it cleanly:

On Mac:

1. Quit Teams fully
2. Drag the Microsoft Teams app from your Applications folder to the Trash
3. Also delete the leftover ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams and ~/Library/Containers/com.microsoft.teams2 folders
4. Download the latest version from microsoft.com/microsoft-teams/download-app
5. Install and sign in

If macOS refuses to open the new copy, follow the fixes for Microsoft Teams is damaged and can’t be opened.

On Windows:

1. Go to Settings → Apps → Installed apps
2. Find Microsoft Teams and click Uninstall
3. Download the fresh installer from Microsoft’s website
4. Install and log in again

What About the “Prevent Screen Capture” Feature in Teams Premium?

This is a separate thing that’s worth knowing about, especially if you’re an admin or meeting organizer.

In late 2025, Microsoft rolled out a feature called Prevent Screen Capture for Teams Premium subscribers. This is designed to stop meeting participants from taking screenshots or recording the screen during sensitive meetings.

Here’s how it works:

• It’s turned off by default — organizers have to enable it per meeting
• On Windows desktop, screenshots show a black rectangle over the Teams window
• On iOS and Android, screenshots and recordings are blocked, and users see a message saying screen capture is restricted
• On platforms that don’t support it (Teams on Mac desktop, Teams on the web, and virtual desktops), attendees join in audio-only mode
• Organizers and co-organizers need Teams Premium; attendees don’t
• It does not stop someone from physically photographing their screen with another device

To enable it as a meeting organizer:

1. Open Calendar in Teams and open the meeting
2. Select Options, then go to Advanced protection
3. Turn on the Prevent screen captures toggle
4. Select Apply. Do this before the meeting starts; if you turn it on mid-meeting, it only takes effect after everyone leaves and rejoins

Note: This requires a Teams Premium license. If you don’t have one, this option won’t appear.

Also worth knowing — Teams does not currently send a notification when someone takes a screenshot in a meeting. There’s no built-in alert system for that. If you need a capture of your own meeting or chat, here’s how to take a screenshot in Microsoft Teams.

Quick Tips to Avoid Screen Capture Headaches

Before wrapping up, here are a few practical habits that will save you from these issues:

• Share a specific app window instead of your full screen. This limits what Teams captures and reduces permission-related noise. In the share screen panel, choose a specific window rather than “Entire screen.”
<