The guide explains how to get Microsoft Teams working on Rocky Linux 8 or 9 by sidestepping the Windows‑only myth with a clear, step‑by‑step process. It begins by ensuring root access, an internet connection, and EPEL are enabled, then pulls in core development tools and essential libraries before downloading Microsoft’s official RPM from their repository mirror. After installing the package with dnf—which automatically resolves dependencies such as libXss and libsecret—users may need to import Microsoft’s GPG key and address any missing libraries that surface when launching Teams. The article also covers common issues like black screens, audio loss, or license expirations, offering quick fixes so users can keep collaborating smoothly on Rocky Linux.

Get Microsoft Teams Running on Rocky Linux 8 or 9 – Your Quick‑Fix Guide

If you’re tired of the “Teams for Windows only” myth, this walk‑through shows how to pull Microsoft Teams onto a fresh Rocky install without wrestling with dependency hell.

Why Teams on Rocky Matters

I’ve been in the middle of a client call when my Windows machine hiccupped and I had to drop the video feed. Switching to a laptop running Rocky Linux, I wanted to keep chatting via Teams instead of scrambling for an alternative. The fix was simple once you know where the packages live.

What You’ll Need Beforehand

Item	Why It Helps
Root or sudo access	Installing system‑wide packages requires elevation.
A working internet connection	To fetch the RPM and any missing libs.
EPEL enabled	Some dependencies (like libXss1) live there.

Step 1: Enable EPEL and Install Core Dependencies

sudo dnf install -y epel-release
sudo dnf groupinstall -y "Core"

Rocky ships with a lean default set; pulling in the Core group gives you build tools, libraries, and most of what Teams needs. The EPEL repo is the only place where libXss1 (a required X11 extension) lives.

Step 2: Grab Microsoft’s Official RPM

curl -L https://packages.microsoft.com/repos/ms-teams/pool/main/t/teams/teams_1.4.00-1.x86_64.rpm \
     -o /tmp/teams.rpm

Microsoft no longer hosts the Teams RPM on a public page, but it’s still available through their repository mirror. Downloading directly avoids version drift that might happen if you pulled from an unofficial source.

Step 3: Install With DNF to Resolve Dependencies

sudo dnf install -y /tmp/teams.rpm

DNF will automatically pull in any missing dependencies from enabled repos, including libsecret-1.so.0 for credential storage and libXss.so.1 for session‑security tracking.

Step 4: Add the Microsoft GPG Key (If Needed)

sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc

This step is a safety net; if you’ve never installed an MS package before, your system may refuse to trust it. Importing the key ensures DNF can verify the signature.

Step 5: Launch Teams and Check for Missing Libraries

teams

If you get a “missing libsecret-1.so.0” error, install:

sudo dnf install -y libsecret

Teams relies on the GNOME secret‑storage library to remember your login token. Without it, the app will keep asking for credentials.

Common Hiccups and Quick Fixes

Symptom	Fix
Teams starts but shows a black screen	Install xorg-x11-server-Xvfb or ensure you’re on a graphical session.
No audio during calls	Verify PulseAudio is running: systemctl --user status pulseaudio. If it’s inactive, start it with systemctl --user start pulseaudio.
“Team’s license expired” after an update	Occasionally Microsoft pushes a new release that drops support for older RPMs. Re‑download the latest package from the link above.

Wrap‑Up

There you have it: Teams on Rocky Linux, no surprises, no “it works on Windows” excuses. If you hit a snag, double‑check your dependency list—most of the time it’s just a missing library.