Troubleshooting
Meet Now on your PC is Microsoft Teams' lightweight meeting join tool that launches automatically when you click a meeting link, often appearing as a pop-up or background process in Task Manager. This feature lets you join meetings without installing the full Teams app, but it can sometimes remain active after meetings end.
Meet Now operates through Microsoft Edge's built-in WebRTC technology, creating peer-to-peer connections that reduce bandwidth usage compared to the full Teams client. 🔥 This explains why it appears as "MicrosoftEdgeCP.exe" or "Teams Meeting Add-in" in Task Manager—it's essentially a browser extension running in the background.
Many users don't realize it's still active after closing meetings, which can cause confusion about why their system resources seem unusually high during work hours.
For those concerned about system performance, Meet Now consumes significantly fewer resources than the full Teams desktop app, making it ideal for quick meetings. However, its automatic launch behavior can be problematic in shared workspaces or when testing new systems.
The good news is that disabling it through Edge's extensions manager or Task Manager gives you complete control over when it runs.
💡 In This Article
- How Microsoft Teams Meet Now Works
- Steps to Identify and Disable Meet Now on Windows
How microsoft Teams Meet Now works
Meet Now leverages Microsoft Edge's built-in WebRTC (Web Real-Time Communication) protocol to create direct peer-to-peer connections between meeting participants. Unlike the full Teams desktop app—which requires installation and runs as a separate service—Meet Now operates entirely within the browser environment.
This means it bypasses the need for system-level permissions while still delivering video, audio, and screen-sharing capabilities through your browser's native media stack. 🔥 The process starts when you click a Teams meeting link, triggering Edge to load the Teams web client in a hidden or minimized window, which then establishes the connection.
You'll often see Meet Now processes in Task Manager under names like "MicrosoftEdgeCP.exe" or "Teams Meeting Add-in". These aren't viruses—they're legitimate components of Edge's Chromium architecture handling media streams and background operations.
WebRTC connections typically use about 1-3 Mbps of bandwidth per participant (vs. 5-10 Mbps for the full Teams app), which explains why Meet Now feels lighter on system resources. The trade-off is that it lacks some advanced features like breakout rooms or certain integrations found in the desktop version.
Meet Now's lightweight design comes with a catch: it relies on Edge's sandboxed environment, which means it can't access your full system camera/microphone permissions like the desktop app. This is why you sometimes see permission prompts even after meetings end—Edge's background tabs maintain access until explicitly revoked.
The process may linger in Task Manager because Edge's architecture keeps background tabs active for quick resume, similar to how Chrome maintains tabs in memory. 💫 This behavior is especially noticeable on systems with 8GB RAM or less, where multiple background processes can impact performance.
Here's where the technical differences get interesting: Meet Now uses Edge's Automatic Tab Discarding feature, which prioritizes active tabs while allowing background meeting processes to persist. This explains why you might see high CPU usage (around 15-25%) during active meetings but not when the meeting window is minimized.
The full Teams app, by contrast, runs as a native Windows process with its own media pipeline, giving it more control over hardware acceleration but at the cost of higher resource usage.
For enterprise environments, Meet Now integrates with Microsoft Intune and Group Policy to enforce meeting policies, but these settings don't affect the basic functionality for individual users.
What most people don't realize is that Meet Now can be triggered not just by direct links, but also by calendar invites processed through Outlook's web version—creating a second potential entry point for background processes. 🌟 This dual-trigger mechanism explains why some users see Meet Now pop-ups even when they didn't click a meeting link directly.
The key difference in system impact comes down to memory management: Meet Now uses about 100-200MB RAM per meeting session, while the full Teams app can consume 300-500MB+** depending on participants and features used.
This is why Meet Now feels more responsive on older hardware—it's essentially a browser-based meeting client with minimal overhead. However, this same architecture means it lacks the deep system integration that allows the full app to handle multiple meetings simultaneously or advanced audio processing features.