How to Install Microsoft Edge on Debian 13, 12 and 11

Microsoft account sync is the main reason to install Microsoft Edge on Debian instead of using a generic Chromium build. Edge is Chromium-based, so Chrome Web Store extensions still work, while favorites, passwords, profiles, and Microsoft 365 sessions stay tied to your Microsoft account. Updates still arrive through APT once Microsoft’s repository is configured.

These instructions use Microsoft’s official Linux package repository on Debian 13 (Trixie), Debian 12 (Bookworm), and Debian 11 (Bullseye). They cover the stable, beta, and dev channels, explain the official .deb download option, and include cleanup for stale package indexes, repository conflicts, and removal.

Install Microsoft Edge on Debian

Debian’s default repositories do not package Microsoft Edge, so a clean install starts with Microsoft’s Linux package repository. This repository method avoids stale one-time package URLs and lets APT handle browser updates after the first setup.

Update Debian Package Lists

Refresh package metadata before adding the Microsoft source:

sudo apt update

These commands use sudo for system changes. If your user account cannot run sudo yet, sign in as root or follow the guide to add a user to sudoers on Debian before continuing.

If the update shows pending base-system upgrades, review them with:

sudo apt upgrade

Install Microsoft Edge Repository Prerequisites

Install the tools required to download the signing key, validate HTTPS certificates, and write the repository keyring. Some Debian desktop and minimal installs do not include curl by default, so install the prerequisites explicitly:

sudo apt install curl gpg ca-certificates -y

The curl command downloads the Microsoft key, gpg converts it into an APT keyring, and ca-certificates lets APT and curl validate HTTPS endpoints correctly.

Confirm Debian Uses amd64

The Microsoft Edge browser packages in this repository are published for Debian amd64 systems, also called x86_64. Check your architecture before writing the source file:

dpkg --print-architecture

A supported system returns:

amd64

If the command returns arm64, armhf, or another value, the Edge browser package will not have an installable candidate on that Debian system. Use another browser or a supported amd64 Debian install instead.

Use the Repository Instead of a Stale .deb URL

Microsoft’s official Edge download page for Linux offers a .deb package, but the repository path is better for repeatable Debian installs. Avoid copying versioned package URLs from the repository pool, such as microsoft-edge-stable_145.0.x_amd64.deb, because old pool links can disappear or stop matching the current package index.

Do not use Microsoft’s generic packages-microsoft-prod.deb package or /debian/<version>/prod repository for Edge. Those repository packages are for other Microsoft Linux products; Edge browser packages are published from the /repos/edge-stable repository used here.

This DEB822 source points APT at the same Microsoft packaging channel that the current Edge package manages after installation.

Add the Microsoft Edge Signing Key

Download Microsoft’s Edge repository key and save it as a dedicated binary keyring:

curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor --yes -o /usr/share/keyrings/microsoft-edge.gpg

Verify the saved keyring fingerprint before trusting the repository:

gpg --no-default-keyring --keyring /usr/share/keyrings/microsoft-edge.gpg --with-fingerprint --list-keys

The fingerprint should match Microsoft’s documented original repository key:

/usr/share/keyrings/microsoft-edge.gpg
--------------------------------------
pub   rsa2048 2015-10-28 [SC]
      BC52 8686 B50D 79E3 39D3  721C EB3E 94AD BE12 29CF
uid           [ unknown] Microsoft (Release signing) <gpgsecurity@microsoft.com>

The same fingerprint appears on Microsoft’s Linux packages documentation for microsoft.asc. If your output differs, stop and recheck the key URL before adding the repository.

Create the Microsoft Edge DEB822 Source File

Create the Microsoft Edge source in DEB822 format. The Suites: stable value is Microsoft’s repository suite, not your Debian codename:

printf '%s\n' \
'Types: deb' \
'URIs: https://packages.microsoft.com/repos/edge-stable' \
'Suites: stable' \
'Components: main' \
'Architectures: amd64' \
'Signed-By: /usr/share/keyrings/microsoft-edge.gpg' | sudo tee /etc/apt/sources.list.d/microsoft-edge.sources > /dev/null

Refresh APT and Confirm the Edge Candidate

Refresh APT again so Debian reads the Microsoft Edge source:

sudo apt update

Confirm the stable package is visible:

apt-cache policy microsoft-edge-stable

Relevant output should show a candidate from Microsoft’s stable Edge repository. The exact version changes as Microsoft publishes new browser builds:

microsoft-edge-stable:
  Installed: (none)
  Candidate: x.x.x-1
  Version table:
     x.x.x-1 500
        500 https://packages.microsoft.com/repos/edge-stable stable/main amd64 Packages

Install Microsoft Edge Stable on Debian

Install the stable browser channel for daily use:

sudo apt install microsoft-edge-stable

Optional: Install Microsoft Edge Beta or Dev on Debian

Microsoft also publishes beta and dev packages from the same repository. These channels can run beside stable in separate profiles, but keep stable as the normal browser unless you need preview builds for testing.

Install the beta channel with:

sudo apt install microsoft-edge-beta

Install the dev channel with:

sudo apt install microsoft-edge-dev

Check package visibility first if you only want to confirm the preview channels without installing them:

apt-cache policy microsoft-edge-beta microsoft-edge-dev

Verify and Launch Microsoft Edge on Debian

Verify the Installed Edge Version

Check the installed stable build from the terminal:

microsoft-edge --version

The command returns the installed browser version:

Microsoft Edge x.x.x

For preview channels, use the command that matches the channel you installed.

microsoft-edge-beta --version

microsoft-edge-dev --version

Start Microsoft Edge from the Terminal

Launch the channel you installed from a graphical terminal session:

microsoft-edge

microsoft-edge-beta

microsoft-edge-dev

Edge needs an active graphical desktop session to open a browser window. A package can install over SSH or in a terminal-only environment, but the browser itself is a desktop application.

Launch Microsoft Edge from Debian GNOME

On Debian GNOME, open Activities, search for Microsoft Edge, and start the browser from the application launcher. Beta and dev builds appear as separate launcher entries when those packages are installed.

Update Microsoft Edge on Debian

Microsoft Edge updates through APT after the repository is configured. Refresh package metadata first:

sudo apt update

Upgrade only the stable Edge package with:

sudo apt install --only-upgrade microsoft-edge-stable

Use the matching package name if you installed a preview channel.

sudo apt install --only-upgrade microsoft-edge-beta

sudo apt install --only-upgrade microsoft-edge-dev

Use a normal system upgrade when you want to update Edge and the rest of Debian together:

sudo apt upgrade

Hold or Unhold Microsoft Edge Updates

If you need to pause a channel temporarily, hold the exact package name:

sudo apt-mark hold microsoft-edge-stable

Allow updates again with:

sudo apt-mark unhold microsoft-edge-stable

For beta or dev, replace microsoft-edge-stable with the exact preview package name.

Remove Microsoft Edge from Debian

Remove only the channel package you installed. Start with stable if that is your browser channel:

sudo apt remove microsoft-edge-stable

For preview channels, remove only the matching package.

sudo apt remove microsoft-edge-beta

sudo apt remove microsoft-edge-dev

Review optional dependency cleanup before removing anything else. Reused systems can have older kernels or unrelated packages marked as autoremovable:

sudo apt autoremove --dry-run

If the dry run only lists packages you are comfortable removing, run:

sudo apt autoremove

Remove the Microsoft Edge Repository and Key

Only remove the repository after all Edge channels are gone. The current Edge package can manage the same source and key files, so do not delete them while another Edge channel remains installed.

sudo rm -f /etc/apt/sources.list.d/microsoft-edge.sources
sudo rm -f /usr/share/keyrings/microsoft-edge.gpg
sudo rm -f /etc/default/microsoft-edge
sudo apt update

Confirm the repository is gone from APT’s candidate list:

apt-cache policy microsoft-edge-stable

After the source has been removed and APT has refreshed, the output should no longer show packages.microsoft.com as a candidate source. Some systems may print N: Unable to locate package microsoft-edge-stable instead.

Optional: Remove Microsoft Edge User Data

Package removal does not delete browser profiles, bookmarks, saved passwords, extensions, or cache data from your Linux user account. List any Edge profile directories first:

find "$HOME/.config" "$HOME/.cache" -maxdepth 1 -type d -name 'microsoft-edge*' -print 2>/dev/null

The next commands permanently delete local Edge profile data for your account, including saved passwords, bookmarks, browsing history, extensions, and cache files. Export or sync anything you need before removing these directories.

Close Edge, then remove only the channel-specific profile and cache directories you no longer need. For stable, use:

rm -rf "$HOME/.config/microsoft-edge" "$HOME/.cache/microsoft-edge"

For beta or dev, use the matching profile path:

rm -rf "$HOME/.config/microsoft-edge-beta" "$HOME/.cache/microsoft-edge-beta"

rm -rf "$HOME/.config/microsoft-edge-dev" "$HOME/.cache/microsoft-edge-dev"

Run profile cleanup as the user who owns the browser data. Do not use sudo unless you intentionally need to remove another user’s profile.

Troubleshoot Microsoft Edge on Debian

Fix APT 404 Errors While Downloading Edge

A 404 during package download usually means APT is trying to fetch an Edge build from an old package index after Microsoft rotated the pool file. The error can look like this:

While downloading https://packages.microsoft.com/repos/edge/pool/main/m/microsoft-edge-stable/microsoft-edge-stable_145.0.3800.58-1_amd64.deb: server returned status 404

Clean cached package files, force APT to refetch the Microsoft Edge index, then try the install or upgrade again:

sudo apt clean
sudo rm -f /var/lib/apt/lists/packages.microsoft.com_repos_edge*_dists_stable_*
sudo apt update
apt-cache policy microsoft-edge-stable
sudo apt install microsoft-edge-stable

If you use an APT caching proxy, clear or refresh that proxy too. Otherwise, Debian may keep receiving the stale package index even after the local cache is rebuilt.

Fix Signed-By Conflicts from extrepo

If you previously enabled Edge with Debian’s extrepo catalog and then switch to the manual DEB822 source, APT can report conflicting Signed-By values for the same Microsoft repository. The extrepo Edge entry also uses a catalog key with a SHA-1 self-signature, which can fail on newer APT verification paths.

Error: Conflicting values set for option Signed-By regarding source https://packages.microsoft.com/repos/edge/ stable: /var/lib/extrepo/keys/edge.asc != /usr/share/keyrings/microsoft-edge.gpg

Disable the extrepo source and remove its leftover source file:

sudo extrepo disable edge
sudo rm -f /etc/apt/sources.list.d/extrepo_edge.sources
sudo apt update

Fix Duplicate or Legacy Edge Source Files

Older Edge package flows and direct .deb installs can leave a legacy one-line source such as microsoft-edge.list. Check the Edge source files currently present:

find /etc/apt/sources.list.d -maxdepth 1 -name 'microsoft-edge*' -print

If APT says the same Edge target is configured in another file, such as a mistakenly edited google-chrome.list, locate every Edge repository line before deleting anything:

grep -R "packages.microsoft.com/repos/edge" /etc/apt/sources.list /etc/apt/sources.list.d 2>/dev/null

Remove only the duplicate or misplaced Edge line. Keep unrelated repository entries, such as the real Google Chrome source, intact.

If you now use the DEB822 microsoft-edge.sources file, remove the legacy .list file and refresh APT:

sudo rm -f /etc/apt/sources.list.d/microsoft-edge.list
sudo apt update

Do not remove microsoft-edge.sources unless you are removing Edge completely.

Fix GPG or NO_PUBKEY Errors

If APT reports NO_PUBKEY or an invalid signature for the Microsoft Edge source, recreate the keyring and refresh the package list:

sudo rm -f /usr/share/keyrings/microsoft-edge.gpg
curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor --yes -o /usr/share/keyrings/microsoft-edge.gpg
sudo apt update

If the error remains, inspect the source file and confirm the Signed-By value points to the same keyring path:

cat /etc/apt/sources.list.d/microsoft-edge.sources

Fix Missing Edge Packages on Non-amd64 Debian

If apt-cache policy microsoft-edge-stable shows no candidate after a clean repository setup, confirm the system architecture:

dpkg --print-architecture

Microsoft Edge for Linux is not currently published as a Debian arm64 or armhf browser package. On those systems, APT can read repository metadata but will not provide an installable Edge browser package.

Fix Microsoft Account Sync or Sign-In Problems

Microsoft account sign-in and sync can fail when the system clock is wrong or certificate trust is stale. Check whether system time synchronization is active:

timedatectl show -p NTPSynchronized --value

A synchronized system returns:

yes

Enable network time synchronization and refresh certificate authorities if needed:

sudo timedatectl set-ntp true
sudo apt install --reinstall ca-certificates

After fixing time or certificate issues, restart Edge and sign in again from a fresh browser session.

Conclusion

Microsoft Edge is installed on Debian with APT-managed updates from Microsoft’s repository, so stable and preview channels can stay current without tracking manual package downloads. If you want a different Chromium-based browser, compare it with Google Chrome on Debian, Brave Browser on Debian, or the open-source Chromium browser on Debian.