Installing Microsoft Edge on AlmaLinux 9 involves adding Microsoft’s GPG key and creating a repository file that points to the Edge packages, then using dnf to pull in either the stable or dev build. The tutorial walks through importing the key with rpm, writing a repo configuration into /etc/yum.repos.d, and running `sudo dnf install microsoft-edge-stable` (or replacing the package name for the dev channel). It also covers common hiccups—dependency errors that can be fixed by enabling EPEL, unsigned‑package warnings that usually mean the key import failed, and architecture mismatches where only x86_64 is supported. Once installed you launch Edge with the `microsoft-edge` command, check its version to confirm the update, and are encouraged to reach out if any issue slips through.

Installing Microsoft Edge on AlmaLinux 9

Want to bring the same Chromium‑based browser you use on Windows to your AlmaLinux server or desktop? This quick guide shows how to pull in Microsoft Edge from Microsoft’s own repository and get it running on AlmaLinux 9 without any bloatware or manual RPM juggling.

1. Grab Microsoft’s GPG key

Every sane package manager wants a signed key before you trust a repo. Run:

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

That tells `dnf` the packages coming from Microsoft are legit.

2. Drop the Edge repo into place

Create `/etc/yum.repos.d/microsoft-edge.repo` with the following content. Using `tee` under sudo keeps file‑ownership tidy:

cat <<EOF | sudo tee /etc/yum.repos.d/microsoft-edge.repo
[microsoft-edge]
name=Microsoft Edge Repository
baseurl=https://packages.microsoft.com/repos/edge/
enabled=1
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.asc
EOF

If you hit “permission denied” on the `tee` step, double‑check you’re using a user with sudo rights.

3. Install the stable build

With the repo ready, install Edge:

sudo dnf install microsoft-edge-stable

That pulls in all dependencies and drops the `microsoft-edge` binary into `/usr/bin`.

Why this matters: Without adding the GPG key or the correct baseurl, `dnf` will refuse to download anything. The repo file also ensures you always get the latest updates via ordinary system upgrades.

4. (Optional) Get the Dev channel

If you like early‑access features, swap the package name:

sudo dnf install microsoft-edge-dev

The dev build lives in the same repo but is flagged with a different RPM name.

5. Troubleshoot common hiccups

• Dependency errors – On a minimal AlmaLinux image you might see “missing libnss3-compat”. Add EPEL first:

  sudo dnf install epel-release
  sudo dnf update

Then re‑run the Edge install.

• “Package is not signed” – This usually means the GPG key import failed or the repo file was edited incorrectly. Re‑import the key and double‑check the `gpgkey` URL in your `.repo`.
• “Could not find a matching package” – The architecture mismatch (e.g., trying to install on arm64 when only x86_64 is available). Edge currently ships only for 64‑bit x86. Verify with:

  uname -m

6. Launch and verify

Open a terminal or your desktop menu, type `microsoft-edge`, and the browser should spin up. Check the version to confirm you’re running the latest stable build:

microsoft-edge --version

You should see something like “Microsoft Edge 120.x.x.x”.

Happy surfing! If you run into a snag that wasn’t covered here, drop me a line or check out the Microsoft Edge for Linux documentation – it’s surprisingly concise once you’ve pulled the repo in.