Fedora users who rely on Microsoft 365 usually hit the same wall: Edge is not in the default repositories. Install Microsoft Edge on Fedora and you get OneDrive sync, profile sign-in, and Copilot in a Chromium browser without leaving Linux.
You can install Edge either from Microsoft’s RPM repository with DNF (stable, beta, and dev channels) or from Flathub as a Flatpak (stable only). This guide walks through both paths, then covers verification, troubleshooting, updates, and clean removal.
Install Microsoft Edge on Fedora Linux
Use the table below to pick the method that matches your workflow.
| Method | Source | Release Channels | Updates | Best For |
|---|---|---|---|---|
| Microsoft RPM Repository | Microsoft Edge RPM repository | Stable, Beta, Dev | Automatic via dnf upgrade | Native DNF integration with all three release channels |
| Flatpak from Flathub | Flathub Stable | Stable only | Automatic via flatpak update | Application sandboxing and system isolation |
The RPM method is the best default for most Fedora users because it includes stable, beta, and dev channels with normal DNF updates. Pick Flatpak when sandbox isolation matters more than having the beta channel.
Install Microsoft Edge with DNF from the RPM Repository
Microsoft’s Linux download page mostly highlights the
.debpackage, but the official RPM repository is active and ships stable, beta, and dev builds. The steps below use that repository so Edge updates arrive through regular DNF upgrades.
Update Fedora Packages
Update Fedora first so DNF refreshes metadata before you add the Edge repository:
sudo dnf upgrade --refreshThis guide uses
sudofor commands that need root privileges. If your account does not have sudo access yet, follow the guide to add a user to sudoers on Fedora.
Import Microsoft GPG Key
Import Microsoft’s signing key before you install packages from the Edge repository:
sudo rpm --import https://packages.microsoft.com/keys/microsoft.ascA successful key import returns no output.
Create the Microsoft Edge RPM Repository File
Create the repository file directly. This avoids the temporary config.repo profile, which ships with gpgcheck=0:
sudo tee /etc/yum.repos.d/microsoft-edge.repo > /dev/null << 'EOF'
[microsoft-edge]
name=microsoft-edge
baseurl=https://packages.microsoft.com/yumrepos/edge
enabled=1
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://packages.microsoft.com/keys/microsoft.asc
EOFThis gives you one clean repository file and avoids add-it-then-delete-it cleanup later.
Install Microsoft Edge from the RPM Repository
Install the stable channel:
sudo dnf install microsoft-edge-stableCheck the installed version:
microsoft-edge --versionMicrosoft Edge 145.x.xxxx.xx
Your build number will differ because Microsoft pushes new Edge updates continuously.
If you need pre-release builds, install beta or dev instead. These channels change faster and can break more often, but they install as separate applications so you can keep stable installed too:
Microsoft Edge Beta:
sudo dnf install microsoft-edge-betaMicrosoft Edge Dev:
sudo dnf install microsoft-edge-devConfirm the repository file was written correctly:
cat /etc/yum.repos.d/microsoft-edge.repo[microsoft-edge] name=microsoft-edge baseurl=https://packages.microsoft.com/yumrepos/edge enabled=1 gpgcheck=1 repo_gpgcheck=0 gpgkey=https://packages.microsoft.com/keys/microsoft.asc
This confirms package signature checks are enabled with gpgcheck=1.
Install Microsoft Edge via Flatpak on Fedora
Flatpak runs Edge in a sandbox, which can reduce host-system impact from browser bugs or overly broad file access.
Flatpak is pre-installed on Fedora Workstation, Silverblue, and Kinoite. If you use a minimal installation or server variant, install it first with
sudo dnf install flatpak.
Enable the Flathub Repository
Fedora may already have the Fedora Flatpak remote, but Edge is distributed through Flathub. Add Flathub if it is not already configured:
sudo flatpak remote-add --system --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo--if-not-exists keeps this command idempotent, so rerunning it will not duplicate the remote.
Install Microsoft Edge with Flatpak
Flathub currently provides the stable build of Edge. The beta channel is not published there, and the dev listing is no longer maintained.
Install the stable build:
sudo flatpak install --system flathub com.microsoft.Edge -yIf Flatpak reports Unable to load summary from remote flathub, the Flathub remote exists but is disabled. Re-enable it with:
sudo flatpak remote-modify --system --enable flathubAfter enabling the remote, run the install command again.
Verify the Flatpak Installation
Check that Edge appears in your Flatpak app list:
flatpak list | grep -i edgeExpected output:
Microsoft Edge com.microsoft.Edge stable system
You can also print the Edge version directly:
flatpak run com.microsoft.Edge --versionMicrosoft Edge 145.x.xxxx.xx
Launch Microsoft Edge on Fedora
Launch Microsoft Edge from the Command Line
CLI launch commands are useful for scripts, remote sessions, and quick troubleshooting.
Launch RPM-Installed Microsoft Edge
Stable RPM build:
microsoft-edgeIf beta or dev is installed, use:
microsoft-edge-betamicrosoft-edge-devLaunch Flatpak-Installed Microsoft Edge
For Flatpak installs, launch by app ID:
flatpak run com.microsoft.EdgeLaunch Microsoft Edge from the Desktop
On Fedora GNOME, Edge appears in Activities after installation.
Open Activities, search for Microsoft Edge, and launch it. If you installed stable, beta, and dev, each channel appears as a separate app entry.
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 this browser profile to stay local to the Fedora machine.
Troubleshoot Microsoft Edge Issues on Fedora
Fix Microsoft Edge GPG Key Errors
If DNF throws a GPG error while installing Edge, the Microsoft signing key is usually missing or stale. A common error looks like:
Error: GPG check FAILED Public key for microsoft-edge-stable-145.x.xxxx.xx-1.x86_64.rpm is not installed
Re-import the key:
sudo rpm --import https://packages.microsoft.com/keys/microsoft.ascThen refresh metadata to verify the repository loads cleanly:
sudo dnf makecache --refreshmicrosoft-edge 100% | 9.2 KiB/s | 1.5 KiB | 00m00s Metadata cache created.
If this completes without a GPG failure, rerun the Edge install command.
Microsoft Edge Does Not Launch
If Edge does not launch from the app menu, run it in a terminal first so you can see startup errors:
microsoft-edge 2>&1 | head -20For RPM installs, verify package files have not been modified or removed:
rpm -V microsoft-edge-stableNo output means package files are intact. If you see file mismatches, reinstall the package.
For Flatpak installs, confirm app metadata and origin:
flatpak info com.microsoft.EdgeThis confirms the app ID and source remote. If the remote is wrong or missing, reinstall from Flathub.
Fix Microsoft Edge Flatpak Sandbox Access Problems
Flatpak sandbox rules can block Edge from folders outside the default allowed paths. If file pickers cannot reach a directory you use, check current filesystem permissions first:
flatpak info --show-permissions com.microsoft.Edge | grep filesystemGrant broader access only when needed:
sudo flatpak override --system com.microsoft.Edge --filesystem=homeThis opens your full home directory to Edge. If you only need one location, 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, run a repair first:
sudo flatpak repair --systemIf issues continue, reinstall the app:
sudo flatpak uninstall --system com.microsoft.Edge
sudo flatpak install --system flathub com.microsoft.Edge -yThis pulls a clean copy from Flathub.
Update and Remove Microsoft Edge on Fedora
Update Microsoft Edge
Update Edge with the same package manager you used for installation.
For RPM installations:
sudo dnf upgrade microsoft-edge-stableReplace microsoft-edge-stable with microsoft-edge-beta or microsoft-edge-dev for those channels.
For more package management examples, see DNF5 install commands on Fedora.
For Flatpak installations:
sudo flatpak update --system com.microsoft.EdgeOr update all installed Flatpak applications at once:
sudo flatpak update --systemRemove RPM-Installed Microsoft Edge
Removing the RPM package deletes the browser binaries but leaves your local profile data in place.
Your bookmarks, saved passwords, and browsing data are stored in
~/.config/microsoft-edge/(for stable) or the corresponding channel directory. To preserve this data before removal, back it up withmkdir -p ~/edge-backup && cp -r ~/.config/microsoft-edge* ~/edge-backup/.
Stable version:
sudo dnf remove microsoft-edge-stableBeta version:
sudo dnf remove microsoft-edge-betaDeveloper version:
sudo dnf remove microsoft-edge-devIf you no longer want Edge packages to appear in DNF, remove the repo file and verify it is gone:
sudo rm /etc/yum.repos.d/microsoft-edge.repodnf repo list --all | grep -i edgeNo output confirms the repository has been removed.
Remove User Data (Optional)
The uninstall leaves profile data behind. To wipe bookmarks, history, saved passwords, and extensions, remove the config directory:
rm -rf ~/.config/microsoft-edge*This permanently deletes all your Edge profile data. Back up any important bookmarks or passwords before running this command.
Remove Flatpak-Installed Microsoft Edge
For Flatpak installs, remove the app with flatpak uninstall:
Stable version:
sudo flatpak uninstall --system com.microsoft.EdgeTo delete Flatpak profile data for the stable build:
This permanently removes local Edge data from the Flatpak app directories. Back up anything you want to keep before running the command.
rm -rf ~/.var/app/com.microsoft.EdgeFrequently Asked Questions About Microsoft Edge on Fedora
No. Microsoft Edge is proprietary software and is not packaged in Fedora’s official repositories. You need to add Microsoft’s RPM repository or install the Flatpak from Flathub.
The RPM version installs directly into the system and provides all three release channels (stable, beta, dev) with updates through DNF. The Flatpak version runs in a sandbox with restricted system access and currently offers the stable channel only. RPM is better for full system integration; Flatpak is better for isolation.
config.repo to install Microsoft Edge on Fedora?
No. You can create /etc/yum.repos.d/microsoft-edge.repo directly with gpgcheck=1 and then install microsoft-edge-stable with DNF. This avoids the temporary config.repo profile and keeps the repository setup simpler.
dnf install for Microsoft Edge?
Use sudo dnf install microsoft-edge-stable for the stable channel. Pre-release channels use microsoft-edge-beta or microsoft-edge-dev.
On Fedora, the repository method is usually better because Edge updates arrive through normal dnf upgrade runs and all channels are available from one source. Standalone RPM workflows require more manual maintenance.
Yes. Although Microsoft’s official download page only shows the .deb package for Linux, the RPM repository at packages.microsoft.com/yumrepos/edge/ is actively maintained with all three release channels receiving regular updates.
Conclusion
Microsoft Edge on Fedora is now running with either native DNF updates or Flatpak sandboxing, based on the method you picked. Next, import browser data through edge://settings/importData, tune privacy controls at edge://settings/privacy, and round out your Microsoft workflow with Microsoft fonts on Fedora and Visual Studio Code on Fedora.
On Fedora 41, with dnf5, the commands have changed a bit:
“`
sudo rpm –import https://packages.microsoft.com/keys/microsoft.asc
sudo dnf config-manager addrepo –from-repofile=https://packages.microsoft.com/yumrepos/edge/config.repo
sudo dnf install microsoft-edge-stable
“`
Thanks Steve, I need to update most of my Fedora guides with DNF 5 now released. Cheers for the message.