Fix Cannot Join a Microsoft Teams Meeting on Teams for the Web

When you click a meeting link in Teams for the Web, the meeting window may fail to open, show a black screen, or bounce back to the lobby. This problem often comes from browser permissions, network restrictions, or an outdated browser. This article explains the root causes and gives you a step-by-step fix sequence that resolves the issue in most cases.

The Teams web client depends on the browser to handle audio, video, and screen sharing. If the browser blocks these capabilities, Teams cannot establish the meeting connection. You will also learn how to check your network firewall and how to switch to the desktop app if the web client remains unreliable.

Why Teams for the Web Cannot Join a Meeting

Teams for the Web runs inside your browser. It does not use the desktop app’s local resources. Instead, it relies on the browser’s WebRTC engine to transmit audio and video. If the browser blocks WebRTC, the meeting fails to connect.

The most common technical cause is a permission conflict. Modern browsers require explicit user consent for microphone, camera, and screen sharing. When you click “Join now,” the browser may not show the permission prompt if it is suppressed by a group policy or if the site is not trusted. Without these permissions, Teams cannot send or receive media, so the join action times out.

Another frequent cause is stale cached data. Teams stores meeting tokens and configuration files in the browser cache. If these files are corrupted or expired, the web client cannot validate your identity, and the join request is rejected. Network firewalls can also block the specific ports and domains that Teams uses for real-time media.

How the Web Client Differs from the Desktop App

The desktop app runs as a native process with direct access to your operating system’s audio and video drivers. It can also open ports automatically. The web client has no such privileges. It must ask the browser for permission each session, and the browser controls the network stack. This makes the web client more sensitive to browser settings and network policies.

Steps to Diagnose and Fix the Join Failure

Follow these steps in order. Each step targets a specific root cause. Test the join after each step to avoid unnecessary changes.

1. Check your browser version
   Open your browser’s About page. For Chrome, go to Chrome menu > Help > About Google Chrome. For Edge, go to Edge menu > Help and feedback > About Microsoft Edge. Update to the latest version. Teams for the Web requires a current browser. Older versions lack the WebRTC features that Teams needs.
2. Allow microphone and camera access
   In Chrome, go to Settings > Privacy and security > Site settings > Microphone and Camera. In Edge, go to Settings > Cookies and site permissions > Microphone and Camera. Add the Teams domain to the Allow list. Then reload the Teams page and click the meeting link again.
3. Clear cached data and cookies
   Press Ctrl + Shift + Delete to open the clear browsing data panel. Select “Cached images and files” and “Cookies and other site data.” Choose “All time” as the time range. Click Clear data. Then close the browser completely and reopen it.
4. Disable browser extensions
   Open your browser’s extensions or add-ons page. Disable ad blockers, privacy tools, and VPN extensions. These tools can block the domains that Teams uses for media. After disabling them, reload the Teams page and try to join again.
5. Verify network firewall settings
   Teams for the Web needs access to these domains: teams.microsoft.com, login.microsoftonline.com, and graph.microsoft.com. It also needs UDP ports 3478 to 3481 for media. Check your firewall or proxy logs to see if these are blocked. If you manage the network, allow these endpoints for the user’s IP range.
6. Check meeting policy settings as an admin
   If you are a Teams admin, open the Teams admin center > Meetings > Meeting policies. Select the policy assigned to the user. Under “Meeting join and lobby,” verify that “Anonymous users can join a meeting” is set to On. Also check that “Meet now in channels” is allowed. Save the policy and wait 10 minutes for propagation.
7. Use the desktop app as a fallback
   If the web client still fails, download the Teams desktop app from the official Microsoft site. Sign in with the same account. Open the meeting link in the desktop app. The app bypasses browser restrictions and often joins successfully when the web client cannot.

If Teams Still Has Issues After the Main Fix

Teams Shows a Black Screen After Joining

A black screen usually means the camera or display permission was not granted correctly. Go back to the browser’s site settings and check that the Teams domain has Camera and Display Capture set to Allow. Then restart the browser and rejoin. If the issue persists, your graphics driver may be outdated. Update the driver and test again.

Teams Keeps Returning to the Lobby

If you see the lobby message repeatedly, your account may not have the correct meeting policy. Ask your admin to verify that the user policy allows anonymous join. Also check that the meeting organizer did not set the lobby to “Only organizers.” If you are the organizer, change the lobby setting in the meeting options before starting the meeting.

Microphone or Camera Does Not Work in the Meeting

When you join, Teams shows a pre-meeting device check. If your mic or camera is not detected, click the settings gear icon and select the correct device. In the browser, confirm that the permission prompt was not dismissed accidentally. You can reset the permission by clearing site data for the Teams domain and rejoining.

Teams for the Web vs Teams Desktop App: Key Differences

Item	Teams for the Web	Teams Desktop App
Installation	None, runs in the browser	Requires download and install
Audio and video	Depends on browser permissions	Uses native system drivers
Network ports	Uses browser’s network stack	Can open UDP ports directly
Screen sharing	Requires browser screen capture permission	Uses native screen capture
Performance	May lag on large meetings	Optimized for large meetings
Best for	Quick joins on shared computers	Daily work and critical meetings

Use the web client when you are on a device without installation rights. Use the desktop app for reliability and better performance. The desktop app also supports background blur and custom layouts that the web client lacks.

You can now diagnose and fix the join failure by checking browser permissions, clearing cache, and reviewing network settings. Start with the browser permission fix because it resolves most cases. If the problem continues, use the desktop app as a reliable fallback. For recurring issues, ask your admin to review the meeting policy and network firewall rules.