The new Edge browser for Windows 10 and MacOS. Microsoft Based on the same engine that drives Google's Chrome browser, Microsoft's new Edge browser is now available for Windows and MacOS. Configure Microsoft Edge policy settings for macOS using a.plist.; 3 minutes to read; In this article. This article describes how to configure Microsoft Edge on macOS using a property list (.plist) file. You'll learn how to create this file and then deploy it to Microsoft Intune. On the troubleshooting page, it says Edge Insider builds are 'available on macOS 10.10 Yosemite or higher', but after I downloaded the Canary 76.0.167.0 installer package, it says 'Microsoft Edge Canary Update 76.0.167.0 can't be installed on this disk. OS X version. Jan 15, 2020 Note. This article applies to Microsoft Edge version 77 or later on Windows 8 and Windows 10. For Windows 7 and macOS, see the Set Microsoft Edge as default browser policy. Mar 10, 2020 Microsoft Edge on macOS The Chromium engine has allowed for a complete refresh of Microsoft Edge, as the new browser evolved beyond the world of Windows to become a cross-platform application that.
This article explains how you can set Microsoft Edge as the default browser on Windows and macOS.
Note
This article applies to Microsoft Edge version 77 or later on Windows 8 and Windows 10. For Windows 7 and macOS, see the Set Microsoft Edge as default browser policy.
You can use the Set a default associations configuration file Group Policy or the DefaultAssociationsConfiguration Mobile Device Management setting to set Microsoft Edge as the default browser for your organization.
To set Microsoft Edge Stable as the default browser for html files, http/https links, and PDF files use the following application association file example:
Note
To set Microsoft Edge Beta as the default browser, set ApplicationName to 'Microsoft Edge Beta' and ProgId to 'MSEdgeBHTML'. To set Microsoft Edge Dev as the default browser, set ApplicationName to 'Microsoft Edge Dev' and ProgId to 'MSEdgeDHTML'.
Note Does office for mac 2016 work with el capitan.
The default file associations aren't applied if Microsoft Edge isn't installed on the target device. In this scenario, users are prompted to select their default application when they open a link or a htm/html file.
You can set Microsoft Edge as the default browser on domain-joined devices by configuring the Set a default associations configuration file group policy. Turning this group policy on requires you to create and store a default associations configuration file. This file is stored locally or on a network share. For more information about creating this file, see Export or Import Default Application Associations.
The example in the next screenshot shows an associations file named appassoc.xml on a network share that is accessible from the target device.
Note
If this setting is enabled and the user's device is domain-joined, the associations configuration file is processed the next time the user signs on.
To set Microsoft Edge as the default browser on Azure Active Directory joined devices follow the steps in the DefaultAssociationsConfiguration Mobile Device Management setting using the following application association file as an example.
Note
To set Microsoft Edge Beta as the default browser, set ApplicationName to 'Microsoft Edge Beta' and ProgId to 'MSEdgeBHTML'. To set Microsoft Edge Dev as the default browser, set ApplicationName to 'Microsoft Edge Dev' and ProgId to 'MSEdgeDHTML'.
Attempting to programmatically set the default browser on macOS causes a prompt to appear for the end user. This prompt is a macOS security feature that can only be automated away by using an AppleScript.
Because of this limitation, there are two main methods for setting Microsoft Edge as the default browser on a macOS. The first option is to flash the device with an image of macOS where Microsoft Edge has already been set as the default browser. The other option is to use the Set Microsoft Edge as default browser policy, which prompts the user to set Microsoft Edge as the default browser.
When using either of these methods, it is still possible for a user to change the default browser. This is because for security reasons, the default browser preference can’t be blocked programmatically. For this reason, we recommend that you deploy the Set Microsoft Edge as default browser policy even if you create an image with Microsoft Edge as the default browser. If the policy is set and a user changes the default browser from Microsoft Edge the next time they open Microsoft Edge, they will be prompted to set it as the default.

Update 6/4/19: In addition to the Canary Channel we released last week, you can now download the Dev channel for macOS from the Microsoft Edge Insider website. This release enables dark mode, which makes your tabs, address bar, toolbar, menus, and other elements use dark colors if you have your macOS theme set to “Dark Mode.” We’ll expand dark mode in the coming weeks to include other parts of Microsoft Edge, such as settings and management pages. Check it out, and let us know your thoughts using the “Send feedback” smiley, the Microsoft Edge Insider forums, or by reaching out on Twitter.
Last month, we announced the first preview builds of the next version of Microsoft Edge for Windows 10. Today, we are pleased to announce the availability of the Microsoft Edge Canary channel for macOS. You can now install preview builds from the Microsoft Edge Insider site for your macOS or Windows 10 PC, with more Windows version support coming soon.
Microsoft Edge for macOS will offer the same new browsing experience that we’re previewing on Windows, with user experience optimizations to make it feel at home on a Mac. We are tailoring the overall look and feel to match what macOS users expect from apps on this platform.
We are committed to building a world class browser with Microsoft Edge through differentiated user experience features and connected services. With this initial release, we have made several changes to the user interface to align with the Microsoft design language whilst making it feel natural on macOS.
Examples of this include a number of tweaks to match macOS conventions for fonts, menus, keyboard shortcuts, title casing, and other areas. You will continue to see the look and feel of the browser evolve in future releases as we continue to experiment, iterate and listen to customer feedback. We encourage you to share your feedback with us using the “Send feedback” smiley.
Additionally, we are designing user experiences that are exclusive to macOS, by leveraging specific hardware features available on Mac. For example, providing useful and contextual actions through the Touch Bar like website shortcuts, tab switching and video controls, as well as enabling familiar navigation with trackpad gestures.
The new Microsoft Edge preview builds for macOS are available through preview channels that we call “Microsoft Edge Insider Channels.” We are starting by launching the Microsoft Edge Insider Canary Channel, which you can download and try at the Microsoft Edge Insider site. This channel is available starting today on macOS 10.12 and above. The Dev Channel will be released very soon, and once available, you’ll be able to download and install it side-by-side with the Canary Channel. You can learn more about our approach and what to expect from the different channels in our blog post from last month.
With our new Chromium foundation, you can expect a consistent rendering experience across the Windows and macOS versions of Microsoft Edge, as well as the same powerful developer tools you’ll find on Windows.
For the first time, web developers can now test sites and web apps in Microsoft Edge on macOS and be confident that those experiences will work the same in the next version of Microsoft Edge across all platforms. (Note that platform-specific capabilities, like PlayReady content decryption on Windows 10, should continue to be feature detected for the best experience on those platforms.)
As with our Windows preview builds, our new macOS version also includes support for installable, standards-based Progressive Web Apps which you can inspect and debug using the browser developer tools. We’re working to make PWAs feel at home alongside your native apps, so when installed they will appear in your Dock, app switcher, and Spotlight just like a native app.
We’re delighted to share our first Microsoft Edge Canary build for macOS with you! Getting your feedback is an important step in helping us make a better browser – we consider it essential to create the best possible browsing experience on macOS. We hope you’ll try the preview today, and we look forward to your feedback and participation in the Microsoft Edge Insider community.
If you encounter any issues, and to give feedback or share suggestions with the team, head over to the Microsoft Edge Insider community forums, get in touch with us on Twitter, or just use the “Send feedback” option in the Microsoft Edge menu to let us know what you think.
For web developers, if you encounter an issue that reproduces in Chromium, it’s best to file a Chromium bug. For problems in the existing version of Microsoft Edge, please continue to use the EdgeHTML Issue Tracker.
We look forward to hearing from you!
– The Microsoft Edge Team