If you remember downloading a Microsoft Teams .deb, you are not imagining it. That client existed, and thousands of Linux setup notes still point toward it. The awkward truth is that those instructions now lead people toward an unsupported application instead of a working meeting.

On Ubuntu today, Microsoft’s supported routes are Teams for Web and the installable web experience called a Progressive Web App (PWA). The PWA gets its own window and launcher, but it is still Teams on the web, hosted and updated by Edge or Chrome. Once that boundary is honest, the setup becomes much less mysterious.

Start with a tab; earn the app window later

Open Teams on the web in a current desktop release of Microsoft Edge, Google Chrome, or Firefox. Microsoft currently supports the latest three versions of those browsers on Linux. Sign in with the work, school, or personal account that owns the meeting or organization you need.

  1. Open https://teams.microsoft.com/ by typing the address or following the official Microsoft link—not an installer advertisement.

  2. Complete your organization’s sign-in, multifactor authentication, and device-compliance prompts. A tenant can restrict access even when the browser itself is supported.

  3. Allow notifications only if this browser profile is the place where you want work alerts to appear.

  4. Open Settings and more → Settings → Devices, choose the intended speaker, microphone, and camera, and use the available preview or test-call option before a real meeting.

  5. Join a low-stakes test meeting and verify incoming audio, microphone level, camera preview, and screen sharing separately.

A PWA changes the frame, not the service underneath

If the browser tab works and you want a desktop-like launcher, install Teams as a PWA from Edge or Chrome. Microsoft’s Teams PWA documentation names those two browser hosts. In either browser, open Teams first, then use the install icon in the address bar or the browser’s app-install menu. The wording can move as browsers update, so trust the install affordance shown for teams.microsoft.com rather than a screenshot from an old release.

  • What you gain: a separate Teams window, an application launcher, convenient pinning, and browser-managed updates.

  • What you do not gain: a native Linux Teams binary, independent offline operation, or automatic parity with the Windows and macOS desktop clients.

  • What remains in charge: the hosting browser’s cookies, permissions, extensions, update lifecycle, and enterprise policies.

  • If installation is absent: keep using the ordinary supported browser tab. The install prompt can be unavailable because of browser support, a managed policy, or the site’s current installability state.

Give the meeting only the permissions it needs

Camera, microphone, notifications, and screen capture cross several boundaries: Ubuntu, the browser, the Teams site, and sometimes your organization’s policy. When one layer says no, reinstalling the PWA rarely changes anything.

Camera or microphone missing

  • Use the padlock or site-controls icon beside the Teams address and set Camera and Microphone to Allow, then reload Teams.

  • In Teams device settings, select the real device rather than an unplugged headset, monitor output, or stale virtual camera.

  • Close another application that may hold the device, and check the laptop’s physical camera shutter or microphone-mute key.

  • Test the camera and microphone in another browser site or a local Ubuntu application. If they fail there too, the problem sits below Teams.

  • If controls are locked, ask the administrator which browser and device policies apply. Repeatedly clearing cookies cannot override tenant policy.

Screen sharing offers the wrong thing—or nothing

  • Approve the browser’s screen-capture prompt and deliberately choose a screen, window, or tab. Do not share the whole desktop by reflex when a single window is enough.

  • On a Wayland desktop, screen capture commonly travels through the desktop portal and PipeWire. A missing chooser can indicate a portal/session problem rather than a Teams account problem.

  • Confirm the organization allows screen sharing for your meeting role. A disabled control may be policy, not Linux incompatibility.

  • Test sharing before presenting confidential material, especially with multiple displays. Verify the preview shows the intended surface.

No notifications after you close the window

  • Allow notifications for the Teams origin in the same browser profile that hosts the session.

  • Check Ubuntu’s notification settings and Do Not Disturb, then check Teams notification preferences.

  • The browser must be able to run the web app in the background. Power-saving, sleeping-tab, and enterprise policies can stop delivery.

  • Do not enable auto-start or background execution on a shared computer merely to make alerts more persistent.

The limitations matter most on your busiest day

Microsoft describes Teams for Web as close to the desktop experience, but not identical. Its current limitations include simultaneous availability and notifications across multiple accounts or tenants, pop-out chat and channel windows, and avatars or background effects other than blur. Some third-party or line-of-business apps also require third-party cookies.

  • Multiple organizations: do not assume every signed-in tenant will notify you at once. Confirm which account is active before waiting for an alert.

  • Restricted cookies: create the narrowest exception your administrator approves for the affected Microsoft or line-of-business origin; globally enabling third-party cookies is a broad privacy tradeoff.

  • Offline use: a launcher does not turn this cloud collaboration service into an offline desktop suite. Expect chat history, meetings, presence, and current files to depend on connectivity.

  • VDI: Microsoft does not support Teams for Web in VDI environments. Use the organization’s approved virtualized Teams deployment instead of treating a browser tab as equivalent.

  • Mobile browser: Microsoft’s web client documentation does not support mobile browsers. Use the supported mobile application on a phone or tablet.

If an old Microsoft package is still hanging around

An upgraded workstation may still contain the retired teams or teams-insiders package. First ask Ubuntu’s package database what is actually installed. These checks do not start Teams or contact Microsoft.

Terminalbash
dpkg-query -W -f='${binary:Package}\t${Version}\n' teams teams-insiders 2>/dev/null

Read the result before cleaning anything

  • No output normally means neither historical package name is installed. That is not an error that needs repairing.

  • A returned package and version prove only that dpkg knows about it; they do not make the retired client supported.

  • An unofficial wrapper may use another package name. Identify its publisher and installation source before removal.

Terminalbash
sudo apt remove teams

Risk level: caution. Review the command before running it.

Removal is deliberately narrower than erasure

  • apt remove removes that package while leaving unrelated browsers and Microsoft 365 data alone.

  • If the query reported teams-insiders instead, substitute that exact package name. Do not paste both names blindly into a production workstation.

  • APT may leave a historical repository definition or user cache. Inspect those separately; do not recursively delete hidden directories just because their names contain “Teams.”

  • Removing a local package does not sign other browser sessions out. Review the Microsoft account’s sessions and your organization’s offboarding policy when access must actually end.

Before tomorrow’s call, prove the path end to end

  • The Teams URL opens in a currently supported browser release on Ubuntu.

  • The intended account and tenant appear in the profile menu.

  • Speaker output, microphone input, and camera preview use the expected devices.

  • A test share exposes only the selected window or screen.

  • A test notification appears while the PWA or browser runs as your policy permits.

  • You understand which current web limitations affect your workflow and have a meeting-link fallback.

A few nearby Linux desk notes

Microsoft pages checked for this rewrite