How to Install Microsoft Edge on Debian Linux

Microsoft Edge provides Debian users with a Chromium-based browser that syncs bookmarks, passwords, and tabs across Windows, macOS, Linux, Android, and iOS devices. If you work across multiple operating systems, need seamless Microsoft 365 integration, or want Chrome extension compatibility with lower memory usage, Edge addresses these requirements through Microsoft’s official APT repository.

This guide walks through importing Microsoft’s GPG signing key, configuring the repository using modern DEB822 format on Debian 11, 12, and 13, installing your preferred Edge channel (stable, beta, or dev), and cleanly removing the browser and repository when needed. By the end, you will have Edge integrated into your Debian package management workflow with automatic security updates through APT.

Update Debian Before Installing Microsoft Edge

Before adding a new third-party repository, update your existing Debian packages so the base system is current. This reduces the chance of dependency conflicts when APT pulls in Microsoft Edge and its required libraries. Run the following command to refresh the package index and apply any available upgrades:

sudo apt update && sudo apt upgrade

This runs interactively so you can review and confirm the package changes. Add -y if you want to accept upgrades non-interactively (for example, sudo apt update && sudo apt upgrade -y).

Install Required Packages for Microsoft Edge

Next, make sure Debian has the helper tools needed to download and validate Microsoft’s repository key. Most desktops already include these utilities, but it is safe to install or refresh them with a single command. This includes curl for downloading files and gnupg for GPG key verification:

sudo apt install curl gnupg ca-certificates -y

Add the Microsoft Edge APT Repository on Debian

Import the Microsoft GPG Key

APT uses GPG keys to verify that packages really come from the repository they claim to originate from. Import the Microsoft signing key from the official ASCII-armored source and store it in a dedicated keyring under /usr/share/keyrings so you can reference it from the repository configuration:

curl -fsSL https://packages.microsoft.com/keys/microsoft.asc \
  | gpg --dearmor \
  | sudo tee /usr/share/keyrings/microsoft-edge.gpg > /dev/null

This command downloads Microsoft’s ASCII-armored public key, converts it to binary format with gpg --dearmor, and stores it in the system keyring directory. Storing the key under /usr/share/keyrings and referencing it with Signed-By is the modern practice; avoid using the deprecated apt-key workflow.

Verify the Microsoft GPG Key Fingerprint

Before trusting the key, verify its fingerprint against Microsoft’s published value to ensure authenticity. After saving the keyring locally, display the fingerprint:

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

/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 fingerprint must match BC52 8686 B50D 79E3 39D3 721C EB3E 94AD BE12 29CF as documented on Microsoft’s Linux packages page. If the fingerprints do not match, do not add the repository and investigate further.

Before adding any third-party repository, confirm the vendor explicitly supports your Debian release. Check Microsoft’s official repository documentation to verify which suites and architectures are published for Edge. Following the vendor’s published instructions reduces the chance of unexpected package or compatibility issues.

Create a Microsoft Edge Repository File

Microsoft Edge for Linux is only published for amd64 (x86_64) architectures. It does not work on ARM, ARM64, or other architectures. To check your system architecture, run dpkg --print-architecture. If it does not return amd64, the repository will not provide Edge packages and installation will fail.

Use the modern DEB822 .sources format to define the Microsoft Edge repository. This format works on all supported Debian releases (11, 12, and 13). The example below targets typical 64-bit amd64 systems:

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

The DEB822 .sources format works on Debian 11 (Bullseye), Debian 12 (Bookworm), and Debian 13 (Trixie). All supported Debian releases fully support this modern repository format.

Refresh the APT Cache After Adding Microsoft Edge

After adding the repository definition, refresh your APT package list so Debian can see the new Microsoft Edge packages:

sudo apt update

After updating the package index, verify the Microsoft Edge packages are visible to APT with apt-cache policy:

apt-cache policy microsoft-edge-stable

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

The output confirms APT can see the Microsoft Edge repository and shows the latest available version. The Installed: (none) line indicates the package is not yet installed on your system.

Install Microsoft Edge on Debian

With the repository configured and the package index updated, you can install the Microsoft Edge browser. The stable build is the recommended option for daily use on most Debian desktops and laptops.

Install the Microsoft Edge Stable Build

Install the stable Microsoft Edge package with the following command:

sudo apt install microsoft-edge-stable

Optional: Install Microsoft Edge Beta or Dev Builds

If you want to preview upcoming features or test changes before they reach the stable channel, you can install the beta or dev builds. These packages install alongside the stable version, so you can keep your main browser unchanged while testing new features in a separate profile. Microsoft updates the stable channel every 6 weeks, the beta channel receives features approximately 6 weeks ahead of stable, and the dev channel updates weekly with the latest experimental changes.

To install the beta build of Microsoft Edge, run:

sudo apt install microsoft-edge-beta

To install the dev (nightly-style) build, use:

sudo apt install microsoft-edge-dev

The beta and dev channels are not recommended for production systems or critical workstations because features can change quickly and stability decreases as you move toward earlier development stages. Use stable for daily work, beta for previewing upcoming features with reasonable stability, and dev only when you specifically need to test cutting-edge browser behavior or validate web applications against future Edge releases before they reach wider audiences.

Verify Microsoft Edge Installation

After installation completes, confirm Edge is installed and working by checking the installed version:

microsoft-edge --version

Microsoft Edge 142.0.3595.94

The version number confirms APT successfully installed Edge from the Microsoft repository. If you installed beta or dev builds, use microsoft-edge-beta --version or microsoft-edge-dev --version respectively.

Launch Microsoft Edge on Debian

Start Microsoft Edge from the Terminal

You can start Edge directly from a terminal session. This is useful when you want to see log messages in real time or launch a specific channel with flags. Use the command that matches the build you installed:

microsoft-edge

microsoft-edge-beta

microsoft-edge-dev

Launch Microsoft Edge from the Desktop Environment

For everyday use, you will typically start Microsoft Edge from your graphical desktop environment. On GNOME-based desktops, follow these steps:

1. Click Activities in the top-left corner of the screen.
2. Select Show Applications (the grid of dots icon, usually at the bottom-left of the screen).
3. Scroll through the application list or use the search box to look for Microsoft Edge, then click the icon to launch the browser.

To set Microsoft Edge as your default browser from the command line, use one of these commands depending on your desktop environment. On systems that support xdg-utils:

# Set Edge as default for the current user
xdg-settings set default-web-browser microsoft-edge.desktop

# Alternatively, use update-alternatives (system-wide selection, may require a .desktop name)
sudo update-alternatives --config x-www-browser

Manage Microsoft Edge Updates and Removal on Debian

Update Microsoft Edge Packages

Microsoft Edge receives security fixes and feature updates through the same APT mechanism as other packages on your system. Therefore, you can manage Edge updates using familiar Debian package management commands. To check for updates across all configured repositories, including Microsoft’s, run:

sudo apt update

To upgrade Microsoft Edge along with other available package updates, use:

sudo apt upgrade

If you want to prevent a package from being upgraded (for example, to keep a stable channel pinned while you test beta/dev), you can hold it with apt-mark:

# prevent upgrades to the stable package
sudo apt-mark hold microsoft-edge-stable

# later, to allow upgrades again:
sudo apt-mark unhold microsoft-edge-stable

For more control you can use APT pinning via /etc/apt/preferences.d/. Pinning allows finely grained control over which versions or origins are preferred. See your distribution documentation for details.

If you prefer to upgrade only Edge without touching the rest of the system, target the specific package for the channel you installed, for example:

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

Remove Microsoft Edge from Debian

Remove the Microsoft Edge Package

If you no longer need Microsoft Edge, you can remove the package for the channel you installed. Use one of the following commands, depending on which build is present on your system:

sudo apt remove microsoft-edge-stable

sudo apt remove microsoft-edge-beta

sudo apt remove microsoft-edge-dev

To also remove configuration files stored under /etc, you can use purge instead of remove:

sudo apt purge microsoft-edge-stable

After removing Edge, run an additional cleanup to remove orphaned dependencies that are no longer needed:

sudo apt autoremove

Remove the Microsoft Edge APT Repository

If you have fully removed Microsoft Edge and do not plan to reinstall it, you can clean up the repository definition:

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

After removing the repository file, refresh the package list so APT no longer queries the Microsoft Edge repository:

sudo apt update

Remove the Microsoft Edge GPG Key

Finally, if you have removed both the Edge packages and repository, you can delete the now-unused GPG keyring file from /usr/share/keyrings:

sudo rm /usr/share/keyrings/microsoft-edge.gpg

Verify Repository Removal

Confirm the Microsoft Edge repository and packages are no longer visible to APT:

apt-cache policy microsoft-edge-stable

If removal was successful, this command produces no output. Any output showing version candidates indicates the repository or package references still exist.

Optional: Remove Microsoft Edge User Data

Removing the package does not automatically delete your browser profile data, which includes history, extensions, and cached files. If you want to fully wipe Microsoft Edge data for your current user, first identify what will be removed:

ls -la ~/.config/microsoft-edge* ~/.cache/microsoft-edge* 2>/dev/null

Warning: The following commands permanently delete all Microsoft Edge profile data for your account, including saved passwords, bookmarks, browsing history, extensions, and cached files. This cannot be undone. If you want to preserve any data, back up the directories first with cp -r ~/.config/microsoft-edge* ~/edge-backup.

Close the browser, then remove the configuration and cache directories:

rm -rf ~/.config/microsoft-edge*
rm -rf ~/.cache/microsoft-edge*

Run the removal as the user who owns the profile (do not prefix with sudo unless you intentionally need to remove another user’s data).

Resolve Microsoft Edge Repository Conflicts on Debian

Remove Redundant Microsoft Edge Source Files

If you install multiple Edge channels over time, the packages may create separate repository files such as microsoft-edge.list, microsoft-edge-beta.list, and microsoft-edge-dev.list under /etc/apt/sources.list.d/. Consequently, when these entries overlap with a consolidated microsoft-edge.sources file, APT warns that the repository is configured multiple times:

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/microsoft-edge.sources and /etc/apt/sources.list.d/microsoft-edge.list

First, check which repository files exist:

ls -la /etc/apt/sources.list.d/microsoft-edge*

To clean up redundant Edge repository files while preserving your canonical .sources file, remove only the legacy .list entries:

# Remove legacy .list files (suppress errors if none exist)
sudo rm -fv /etc/apt/sources.list.d/microsoft-edge.list /etc/apt/sources.list.d/microsoft-edge-beta.list /etc/apt/sources.list.d/microsoft-edge-dev.list 2>/dev/null

This targets specific .list filenames rather than using wildcards, which prevents accidentally deleting your microsoft-edge.sources configuration.

Troubleshooting Common Repository and GPG Errors

If you encounter issues during repository setup, the following diagnostics and fixes address the most common errors when adding the Microsoft Edge repository.

GPG errors (NO_PUBKEY or invalid signature)

If APT reports a NO_PUBKEY or an invalid signature, confirm the keyring exists and the Signed-By path in your .sources or .list file is correct. Re-import the key if needed:

# Re-download and install the key (example)
curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | sudo tee /usr/share/keyrings/microsoft-edge.gpg >/dev/null
sudo apt update

404 or suite not found

If apt update reports a 404 for the repository suite, confirm the Suites: value matches what Microsoft publishes. For example, some vendors publish stable while others publish by distribution codename. Inspect the repo index:

# List available suites on the vendor server (human-readable)
curl -fsSL https://packages.microsoft.com/repos/edge/dists/ | sed -n '1,200p'

# Check apt update output for exact 404 details
sudo apt update

Architecture mismatch

If packages are unavailable for your architecture, confirm the system architecture and the repo’s published architectures:

dpkg --print-architecture
# If the repo lacks your arch, you will see no candidate packages for Edge in 'apt policy'
apt policy microsoft-edge-stable

Repository configured multiple times

If APT warns the repository is configured multiple times, follow the safe cleanup steps above to remove legacy .list files and keep a single canonical .sources file.

Common Microsoft Edge Issues on Debian

Beyond repository configuration problems, you may encounter Edge-specific issues when running the browser on Debian systems. These quick fixes address the most common problems reported by users.

Hardware acceleration problems

If Edge feels sluggish or videos stutter, hardware acceleration may be disabled or incompatible with your GPU drivers. Common symptoms include high CPU usage during video playback and tearing or dropped frames on high-resolution displays.

Check the current GPU status by navigating to edge://gpu in the address bar. Look for entries showing “Software only” or “Unavailable” which indicate hardware acceleration is not active:

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Video Decode: Unavailable

To enable hardware acceleration, open Settings, navigate to System and performance, and toggle “Use hardware acceleration when available” to on. Restart Edge for the change to take effect. If problems persist with proprietary NVIDIA drivers, launch Edge with additional flags:

microsoft-edge --disable-gpu-driver-bug-workarounds --enable-gpu-rasterization

After restarting, return to edge://gpu and verify the status shows “Hardware accelerated” for the relevant features.

Wayland display server compatibility

On Debian systems running Wayland instead of X11, Edge may default to XWayland compatibility mode. Check your current session type:

echo $XDG_SESSION_TYPE

wayland

If you see “wayland” but Edge windows appear blurry on HiDPI displays or touchscreen gestures do not work, Edge is running through XWayland. Launch Edge natively on Wayland with:

microsoft-edge --enable-features=UseOzonePlatform --ozone-platform=wayland

To make this permanent, create a custom launcher script or edit /usr/share/applications/microsoft-edge.desktop to add the flags to the Exec line. Verify native Wayland mode by checking edge://gpu where the “GL_RENDERER” should show your GPU instead of “llvmpipe” or similar software renderers.

Video codec and DRM playback issues

Streaming services like Netflix, Disney+, and others require Widevine DRM support. If you see error messages like “This content requires Widevine” or playback fails with “M7111-1331-2206” error codes on Netflix, the DRM module may need updating.

Navigate to edge://components and locate “Widevine Content Decryption Module”. Click “Check for update” to ensure you have the latest version:

Widevine Content Decryption Module - Version: 4.10.2830.0
Status: Component updated

For codec issues with VP9 or H.264 video causing “Video playback error” messages, install additional codec libraries. If you have enabled contrib and non-free repositories on Debian, install the extra codecs:

sudo apt install libavcodec-extra

Restart Edge and retry playback. Verify codecs loaded correctly at edge://media-internals.

Microsoft account sync failures

If Edge displays “Sync is paused” or “Can’t connect to sync” errors, authentication issues are usually the cause. Common error messages include “Sync has been turned off by your administrator” even on personal accounts, or the sync icon showing a persistent warning triangle.

First verify your Debian system clock is accurate, as sync services reject authentication tokens when system time drifts more than a few minutes:

timedatectl status | grep -E 'Local time|synchronized'

               Local time: Tue 2025-12-03 10:30:00 EST
System clock synchronized: yes

If the clock is not synchronized, enable NTP sync:

sudo timedatectl set-ntp true

Check that ca-certificates is installed and current so Edge can validate SSL certificates during the OAuth login flow:

sudo apt install --reinstall ca-certificates

If sync continues failing, sign out from Settings, clear browsing data including cookies and site data, restart Edge, then sign in again with a fresh authentication session.

Create a Single Canonical Microsoft Edge Repository

After removing the duplicate source files, recreate a single repository definition so all Microsoft Edge channels share the same configuration. Use the DEB822 .sources file format:

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

Refresh the APT Cache After Fixing Repository Conflicts

Finally, update the package list again and verify that no duplicate repository warnings appear in the output:

sudo apt update

If the update completes without reporting that the Edge repository is configured multiple times, your Debian system is now using a clean, conflict-free configuration for all Microsoft Edge builds you choose to install.

Conclusion

You now have Microsoft Edge installed on Debian through the official APT repository, with automatic updates handled alongside your system packages. The repository configuration, GPG key verification, and removal process covered here follow modern Debian packaging practices using the DEB822 .sources format. For alternative browsers on Debian, see Chromium on Debian, Firefox on Debian, Google Chrome on Debian, or Opera on Debian. If Edge requires additional codecs for video streaming, the contrib and non-free repository guide explains how to enable those sources for the libavcodec-extra package.