Posted in: Intune, Windows 10

Microsoft Edge for Windows 10 deployment in Intune


Following up on Winston’s Edge deployment in MECM posts (Part 1 and Part 2), here is some helpful info to deploy Microsoft Edge for Windows 10 via Intune.

Microsoft provides the following information to deploy the Edge browser via Intune:


*Requires your endpoints to be Windows 10 1709 or later. (Which, face it, if you’re not meeting this requirement, you’ve got issues bigger than Edge to worry about)

*CONTRARY to the Microsoft documentation, different language packs are available during the App Settings configuration and deployment process.  There is no indication if these packs are in Preview or GA release.  Nothing to be surprised about here.

Deployment Configuration

The most unique aspect for Edge deployment on Windows 10 is that Edge is a separate, standalone app type.  Pretty sweet what Microsoft can and will do for their own software.  Microsoft 365 Apps (AKA Office) and Defender ATP are the only other apps that get this special treatment, as of this writing.

Note that this deploys version 77 and later of the Microsoft Edge browser.  Though I don’t know of any reason why you’d want an earlier version of the browser…

Microsoft using specific categories for their own software

Once you select the app you are presented with the App information pane.  A majority of this info is pre-filled, and I can think of no reason to change the URLs for Information and Privacy.  Description and Developer should also be left alone.

The App Name is pretty straightforward, but something you may want to consider is adding the deployment ring to which this app will be deployed.


That’s how we all operate, right?  Something worth considering though is your initial pilot to test Edge within your environment.  Even though the new Edge is Chromium-based, some web apps may not work right.  And, as a future post will discuss, there are options to configure within Edge to deploy Enterprise mode, so that you can eventually rid your organization of the much loved and extra secure Internet Explorer.  Additionally, as seen later in this post, the Edge app configuration allows you to decide which channel of Edge is deployed, stable, beta, or dev.

So, that all being said, you can customize the name of the app, so that when you’re in the Intune/Endpoint Manager dashboard, you can easily see which deployment of the application you are working with, without having to dig into the deployment properties.

No need to change most of Microsoft’s pre-filled text

As you may also notice in my screenshot, I have selected “No” to the option of showing the app “as a featured app in Company Portal”.  I am making this a mandatory installation for all devices in my selected Ring, so users will not need to search for this app in and install from the Company Portal.  If only there were a way to leave the app out of the Company Portal altogether….

Click Next to continue.

App Settings

The App Setting screen is where you can decide which channel will be deployed.  Options available are Stable, Beta and Dev. The images below are captioned with the explanation offered at the link above.

Stable channel is the recommended channel for deploying broadly in Enterprise environments. It updates every six weeks, each release incorporating improvements from the Beta channel.
Beta channel is the most stable Microsoft Edge preview experience and the best choice for a full pilot within your organization. With major updates every six weeks, each release incorporates the learnings and improvements from the Dev channel.
Dev channel is ready for enterprise feedback on Windows, Windows Server and macOS. It updates every week and contains the latest improvements and fixes.

KEY NOTE: Once deployed, Edge will automatically update based on the channel selected.  At this time there are no other granular controls for Edge updates.  So, if you are concerned about stability, the Stable channel should be deployed to your production deployment ring.

The icon you see on this screen is the same Desktop, Start Menu, and Company Portal icon that your users will see.

As you can also see in the screenshots above, various Language options are available as well.

Select OK to continue.

Deployment Assignments

Lastly, select which groups will receive the deployment.  As with most apps, you can deploy the app as a requirement for select or all Users or Devices, or select groups.  You can also make the app available to users in the Company Portal on their enrolled devices.  If the deployment you created does not work for your users, you can assign groups or users that will have the app uninstalled.


And there you have it, within 15 minutes you’ve configured a Microsoft Edge for Windows 10 deployment in Intune for your users.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.