How to Install Microsoft Edge on Fedora 44

Fedora users who rely on Microsoft 365, SharePoint, Edge Sync, or Copilot often need Microsoft’s browser instead of a generic Chromium build. You can install Microsoft Edge on Fedora with DNF from Microsoft’s RPM repository, or use the Flathub wrapper when Flathub packaging fits your desktop workflow better than package-manager integration.

Current Fedora releases, including Fedora 44 and Fedora 43, use the same DNF5 workflow for the RPM method. Fedora does not package Edge in its default repositories, so the main decision is whether you want Microsoft’s DNF-managed RPM packages or the stable-only Flatpak from Flathub.

Install Microsoft Edge on Fedora Linux

Use this method comparison to choose the install path before adding a repository or Flatpak remote.

Method	Source	Channels	Updates	Best Fit
Microsoft RPM Repository	Microsoft Edge RPM repository	Stable, Beta, Dev	Through DNF	Most Fedora desktops, managed systems, and users who want native package updates
Flatpak from Flathub	Unverified Flathub wrapper	Stable	Through Flatpak	Users who prefer Flathub packaging and do not need beta or dev channels

The RPM repository is the best default for most Fedora users. It keeps Edge in the normal DNF update path, exposes stable, beta, and dev packages, and avoids hard-coding one versioned RPM URL.

Microsoft Edge RPM Download and Repository Notes

If you arrived looking for a Microsoft Edge RPM download, use the repository method unless you have a specific offline packaging workflow. Microsoft’s Linux software repository documentation describes packages.microsoft.com as a public repository for DNF/YUM clients, while the versioned RPM files and directory listings are moving targets rather than stable copy-paste install URLs.

If a search result or older command points you at a Debian .deb package, do not install that file on Fedora. Use the RPM repository or Flathub so updates, signatures, and removal stay aligned with Fedora’s package tools.

Install Microsoft Edge with DNF from the RPM Repository

Update Fedora Packages

Refresh Fedora first so DNF uses current repository metadata before adding Edge:

sudo dnf upgrade --refresh

These commands use sudo for system package changes. If your account cannot run sudo yet, add the account to Fedora’s wheel-based admin path with the Fedora sudoers setup guide.

Import the Microsoft RPM Signing Key

Import Microsoft’s original RPM signing key used by the Edge packages:

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

Confirm the key fingerprint appears in the RPM database:

rpm -q gpg-pubkey --qf '%{VERSION}\n' | grep -i '^bc528686b50d79e339d3721ceb3e94adbe1229cf$'

Expected output:

bc528686b50d79e339d3721ceb3e94adbe1229cf

Create the Microsoft Edge DNF Repository File

Microsoft’s published config.repo for Edge currently sets gpgcheck=0. Create a small repository file with RPM package signature checks enabled:

printf '%s\n' \
'[microsoft-edge]' \
'name=microsoft-edge' \
'baseurl=https://packages.microsoft.com/yumrepos/edge-stable' \
'enabled=1' \
'gpgcheck=1' \
'gpgkey=https://packages.microsoft.com/keys/microsoft.asc' | sudo tee /etc/yum.repos.d/microsoft-edge.repo > /dev/null

Refresh DNF and Confirm Edge Packages

Refresh metadata after writing the repository file:

sudo dnf makecache --refresh

Confirm the repository exposes the stable, beta, and dev package names:

dnf --repo=microsoft-edge repoquery --latest-limit=1 --qf '%{name} %{arch} %{repoid}\n' microsoft-edge-stable microsoft-edge-beta microsoft-edge-dev

Expected output:

microsoft-edge-beta x86_64 microsoft-edge
microsoft-edge-dev x86_64 microsoft-edge
microsoft-edge-stable x86_64 microsoft-edge

Install Microsoft Edge from DNF

Install the stable channel for normal browsing:

sudo dnf install microsoft-edge-stable

Check the installed version:

microsoft-edge --version

The command prints a single Microsoft Edge version line. The exact build changes as Microsoft publishes browser updates:

Microsoft Edge 148.0.3967.70

Install beta or dev only when you need pre-release browser behavior for testing. These channels install as separate applications and can coexist with stable:

Microsoft Edge Beta:

sudo dnf install microsoft-edge-beta

Microsoft Edge Dev:

sudo dnf install microsoft-edge-dev

Confirm the installed package source when you need to audit where Edge came from:

dnf info --installed microsoft-edge-stable | grep -E '^(Name|Version|Release|Architecture|From repository)'

Relevant output includes:

Name            : microsoft-edge-stable
Architecture    : x86_64
From repository : microsoft-edge

Install Microsoft Edge via Flatpak on Fedora

Flatpak is a good fit when you prefer Flathub packaging and Flatpak-managed runtime updates. The Flathub listing is currently unverified and not affiliated with Microsoft, and Edge declares broad browser permissions, so treat this method as a packaging choice rather than a strict privacy boundary. Use the RPM repository when you need Microsoft’s package source, beta builds, or dev builds.

Flatpak is preinstalled on Fedora Workstation, Silverblue, and Kinoite. Minimal or server installations may need sudo dnf install flatpak first, and Edge still needs a graphical desktop session to launch normally.

Enable Flathub

Fedora may already have the Fedora Flatpak remote, but Edge is distributed through Flathub. Add Flathub if it is not configured yet:

sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

Install Microsoft Edge with Flatpak

Install the stable Flathub build:

sudo flatpak install flathub com.microsoft.Edge

If Flatpak prints a warning that /var/lib/flatpak/exports/share is not in XDG_DATA_DIRS, restart your desktop session before relying on the Activities launcher. The app can still run immediately with flatpak run com.microsoft.Edge.

If Flatpak reports Unable to load summary from remote flathub, the Flathub remote may be disabled. Re-enable it, then repeat the install command:

sudo flatpak remote-modify --enable flathub

Verify the Flatpak Installation

Check that Edge appears in your Flatpak app list:

flatpak list --app --columns=application,branch,installation | grep -E '^com[.]microsoft[.]Edge[[:space:]]'

Expected output:

com.microsoft.Edge    stable    system

Print the browser version from the Flatpak package:

flatpak run com.microsoft.Edge --version

The command prints a single version line, with the build number changing over time:

Microsoft Edge 148.0.3967.70

Launch Microsoft Edge on Fedora

Launch Microsoft Edge from the Command Line

Terminal launch commands are useful when you need to confirm which installed Edge channel starts.

Stable RPM build:

microsoft-edge

RPM beta or dev builds:

microsoft-edge-beta
microsoft-edge-dev

Flatpak build:

flatpak run com.microsoft.Edge

Launch Microsoft Edge from the Desktop

On Fedora GNOME, Edge appears in Activities after installation. Open Activities, search for Microsoft Edge, and launch it. Stable, beta, and dev RPM channels appear as separate app entries when more than one channel is installed.

Configure Microsoft Edge on Fedora After First Launch

On first launch, Edge asks about privacy defaults, new-tab layout, and optional Microsoft account sign-in for sync. Skip sign-in if you want the browser profile to stay local to the Fedora machine.

Troubleshoot Microsoft Edge Issues on Fedora

Fix Microsoft Edge GPG Key Errors

If DNF reports a GPG check failure while installing Edge, the Microsoft signing key is usually missing or stale. Relevant output may include:

Error: GPG check FAILED
Public key for microsoft-edge-stable-148.0.3967.70-1.x86_64.rpm is not installed

Re-import the key and confirm the fingerprint:

sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
rpm -q gpg-pubkey --qf '%{VERSION}\n' | grep -i '^bc528686b50d79e339d3721ceb3e94adbe1229cf$'

Then refresh metadata before installing again:

sudo dnf makecache --refresh

Repair the Microsoft Edge Repository File

If DNF reports 404 errors or references an old Microsoft Edge repository URL, rewrite the repository file with the current Fedora-safe source:

printf '%s\n' \
'[microsoft-edge]' \
'name=microsoft-edge' \
'baseurl=https://packages.microsoft.com/yumrepos/edge-stable' \
'enabled=1' \
'gpgcheck=1' \
'gpgkey=https://packages.microsoft.com/keys/microsoft.asc' | sudo tee /etc/yum.repos.d/microsoft-edge.repo > /dev/null

sudo dnf makecache --refresh

Microsoft Edge Does Not Launch

If Edge does not launch from Activities, verify the installed command first:

microsoft-edge --version
command -v microsoft-edge
rpm -qf "$(command -v microsoft-edge)"

Relevant output for the RPM build includes:

Microsoft Edge 148.0.3967.70
/usr/bin/microsoft-edge
microsoft-edge-stable-148.0.3967.70-1.x86_64

The exact version and release string can differ after browser updates.

For RPM installs, verify package files have not been modified or removed:

rpm -V microsoft-edge-stable

No output means package files match the installed RPM. Reinstall the package if file mismatches appear.

For Flatpak installs, confirm the app ID and source remote:

flatpak info com.microsoft.Edge

Fix Microsoft Edge Flatpak Sandbox Access Problems

Flatpak sandbox rules can block Edge from folders outside the default allowed paths. Check current filesystem permissions first:

flatpak info --show-permissions com.microsoft.Edge | grep filesystem

Grant broader access only when a workflow needs it:

flatpak override --user --filesystem=home com.microsoft.Edge

This user-scoped override opens your full home directory to Edge, even when the app was installed system-wide. If you only need one folder, use a narrower override instead of home, then restart Edge.

Repair a Broken Microsoft Edge Flatpak Install

If the Flatpak build crashes repeatedly or behaves inconsistently, preview repairable objects first:

sudo flatpak repair --dry-run

If the dry run reports repairable objects, apply the repair:

sudo flatpak repair

If issues continue, reinstall the app from Flathub:

sudo flatpak uninstall com.microsoft.Edge
sudo flatpak install flathub com.microsoft.Edge

Update and Remove Microsoft Edge on Fedora

Update Microsoft Edge

Update Edge with the same package manager used for installation.

RPM installations:

sudo dnf upgrade microsoft-edge-stable

Use microsoft-edge-beta or microsoft-edge-dev instead when you installed one of those channels. For more DNF package workflow examples, see the DNF5 install commands on Fedora.

Flatpak installations:

sudo flatpak update com.microsoft.Edge

Update every system Flatpak app and runtime at once with:

sudo flatpak update

Remove RPM-Installed Microsoft Edge

Removing the RPM package deletes the browser binaries but leaves local profile data in your home directory. Back up the profile first when you need to keep bookmarks, passwords, extensions, or local browser state:

mkdir -p ~/edge-backup
shopt -s nullglob
profiles=(~/.config/microsoft-edge*)
shopt -u nullglob

if ((${#profiles[@]})); then
  cp -r "${profiles[@]}" ~/edge-backup/
else
  echo "No Microsoft Edge RPM profiles found"
fi

Remove the installed Edge channel:

Stable:

sudo dnf remove microsoft-edge-stable

Beta:

sudo dnf remove microsoft-edge-beta

Dev:

sudo dnf remove microsoft-edge-dev

After removing every Edge RPM channel you used, confirm no Edge RPM package remains:

rpm -q microsoft-edge-stable microsoft-edge-beta microsoft-edge-dev || true

Expected output when all three RPM channels are absent:

package microsoft-edge-stable is not installed
package microsoft-edge-beta is not installed
package microsoft-edge-dev is not installed

Remove the repository file when you no longer want Edge packages to appear in DNF:

sudo rm -f /etc/yum.repos.d/microsoft-edge.repo
dnf repo list --all | grep -i microsoft-edge || echo "No Microsoft Edge repository entries found"

Expected output after repository cleanup:

No Microsoft Edge repository entries found

The Microsoft RPM signing key can be shared with other Microsoft repositories. Remove it only if Edge was the only Microsoft RPM source on the system:

if rpm -q gpg-pubkey --qf '%{VERSION}\n' | grep -qi '^bc528686b50d79e339d3721ceb3e94adbe1229cf$'; then
  sudo rpmkeys --delete bc528686b50d79e339d3721ceb3e94adbe1229cf
fi

rpm -q gpg-pubkey --qf '%{VERSION}\n' | grep -i '^bc528686b50d79e339d3721ceb3e94adbe1229cf$' || echo "Microsoft Edge signing key is not installed"

Expected output after trust cleanup:

Microsoft Edge signing key is not installed

Remove RPM User Data

This permanently deletes local Edge profile data. Export bookmarks and save passwords elsewhere before running these commands.

rm -rf -- ~/.config/microsoft-edge ~/.cache/microsoft-edge
rm -rf -- ~/.config/microsoft-edge-beta ~/.cache/microsoft-edge-beta
rm -rf -- ~/.config/microsoft-edge-dev ~/.cache/microsoft-edge-dev

Remove Flatpak-Installed Microsoft Edge

Remove the Flathub app with Flatpak:

sudo flatpak uninstall com.microsoft.Edge

Confirm the system-scope app entry is gone:

flatpak list --system --app --columns=application | grep -Fx com.microsoft.Edge || echo "Microsoft Edge Flatpak is not installed"

Expected output after Flatpak removal:

Microsoft Edge Flatpak is not installed

Delete Flatpak profile data only when you want a full local reset:

This permanently removes the Flatpak Edge profile, including local browser state stored under your account.

rm -rf -- ~/.var/app/com.microsoft.Edge

Related Fedora Guides

For nearby desktop workflows, install Microsoft fonts on Fedora to improve Office document compatibility, or add Visual Studio Code on Fedora from Microsoft’s editor repository. If you want a Chromium-family browser without Microsoft account integration, compare this setup with Google Chrome on Fedora or Chromium on Fedora.

Conclusion

Microsoft Edge is installed on Fedora through either DNF-managed RPM packages or the Flathub wrapper. After the first launch, import browser data from edge://settings/importData, review privacy controls at edge://settings/privacy, and keep updates tied to the package source you chose.