All posts by Microsoft Edge Team

Get started with Collections in Microsoft Edge – Microsoft Edge Blog

We’re excited to announce that Collections is now enabled by default for all Microsoft Edge Insiders in the Canary and Dev channels (build 80.0.338.0 or later). Following our initial preview behind a feature flag two months ago, we have been adding in new features and functionality. For those who enabled the feature flag – thank you! We have been listening to your feedback and are excited to share the improvements we’ve made.We designed Collections based on what you do on the web. If you’re a shopper, it will help you collect and compare items. If you’re an event or trip organizer, Collections will help pull together all your trip or event information as well as ideas to make your event or trip a success. If you’re a teacher or student, it will help you organize your web research and create your lesson plans or reports. Whatever you are doing on the web, Collections can help.
Recent improvements to Collections
We’ve been working hard to add more functionality and refine the feature over the last couple months – some of which were directly informed by your feedback.
Here are some of the improvements we made, based on your input:
Access your collections across your devices: We’ve added sync to Collections. We know some of you have seen issues around sync, your feedback has been helping us improve. We know this is an important scenario and are ready for you to try it. When you are signed into Microsoft Edge preview builds with the same profile on different computers, Collections will sync between them.
Open all links in a collection into a new window: We’ve heard you’d like an easy way to open all sites saved in a collection. Try out “Open all” from the “Sharing and more” menu to open tabs in a new window, or from the context menu on a collection to open them as tabs in the current window so you can easily pick up where you left off. We’ve also heard that you want an easy way to save a group of tabs to a collection. This is something that we are actively working on and are excited to share when it is ready.
Edit card titles: You’ve been asking for the ability to rename the titles of items in collections, so they are easier for you to understand. Now you can. To edit a title, right click and choose “Edit” from the context menu. A dialog will appear giving you the ability to rename the title.
Dark theme in Collections: We know you love dark theme, and we want to make sure we provide a great experience in Collections. We’ve heard some feedback on notes which we’ve addressed. Try it out and let us know what you think.
 “Try Collections” flyout: We understand that if you’re an active user of Collections that we were showing you the “Try Collections” flyout even though you previously used the feature. We’ve now tuned the flyout to be quieter.
Sharing a collection: You’ve told us that once you’ve collected content you want to share it with others. We have lots of work planned to better support sharing scenarios. One way you can share today is through the “Copy all” option added to the “Sharing and more” menu, or by selecting individual items and copying them via the “Copy” button in the toolbar.

Once you’ve copied items from your Collection, you can then paste them into your favorite apps, like OneNote or Email. If you are pasting into an app that supports HTML you will get a rich copy of the content.

Try out Collections
You can get started by opening the Collections pane from the button next to the address bar.
When you open the Collections pane, select Start new collection and give it a name. As you browse, you can start to add content related to your collection.

Send Feedback
Now that we’re on by default, we hope that more of you will give us a try. Thank you again to all of you that have been using the feature and sending us feedback. If you think something’s not working right, or if there’s some capability you’d like to see added, please send us feedback using the smiley face icon in the top right corner of the browser.

Thanks for continuing to be a part of this preview!

Improving Tracking Prevention in Microsoft Edge – Microsoft Edge Blog

Today, we’re excited to announce some improvements to our tracking prevention feature that have started rolling out with Microsoft Edge 79. In our last blog post about tracking prevention in Microsoft Edge, we mentioned that we are experimenting with ways that our Balanced mode can be further improved to provide even greater privacy protections by default without breaking sites. We are looking to strike a balance between two goals:Blocking more types of trackers – Microsoft Edge’s tracking prevention feature is powered by Disconnect’s tracking protection lists. We wanted to build off our initial implementation of tracking prevention in Microsoft Edge 78 and maximize the protections we offered by default by exploring blocking other categories of trackers (such as those in the Content category) in Balanced mode. These changes resulted in Microsoft Edge 79 blocking ~25% more trackers than Microsoft Edge 78.
Maintaining compatibility on the web – We knew that blocking more categories of trackers (especially those in the Content category) had the potential to break certain web workflows such as federated login or embedded social media content.
We learned through experimentation that it is possible to manage these tradeoffs by relaxing tracking prevention for organizations with which a user has established a relationship. To determine this list, we built on-device logic that combines users’ personal site engagement scores with the observation that some organizations own multiple domains that they use to deploy functionality across the web. It’s worth mentioning that this compatibility mitigation only applies to Balanced mode; Strict mode will continue to block the largest set of trackers without any mitigations.

The Chromium project’s site engagement score is a measure of how engaged a specific user is with a specific site. Site engagement scores can range from 0 (meaning a user has no relationship with a site) to 100 (meaning that a user is extremely engaged with a site). Activities such as browsing to a site repeatedly/over several days, spending time interacting with a site, and playing media on a site all cause site engagement scores to increase, whereas not visiting a site causes site engagement scores to decay exponentially over time. You can view your own site engagement scores by navigating to edge://site-engagement.
It’s also worth noting that site engagement scores are computed on your device and never leave it. This means that they are not synced across your devices or sent to Microsoft at any time.
Through local experimentation, we found that a site engagement score of 4.1 was a suitable threshold to define a site that a user has an active relationship with. While this value is subject to change based on user feedback and future experiments, it was selected as an initial value for two reasons:
It is low enough to ensure successful interactions with a site that a user has not previously had a history of engagement with.
It is high enough to ensure that sites a user visits infrequently will drop off the list relatively quickly.
While site engagement helps signal which sites are important to individual users, allowing third party storage access/resource loads from only these sites would not consider the fact that organizations can serve content that users care about from multiple domains, which can still result in site breakages.
Combining site engagement with organizations
In our last blog post about tracking prevention, we introduced the concept of an organization, that is, a single company that can own multiple domains related to their business (such as Org1 owning “org1.test” and “org1-cdn.test”). We also shared that in order to keep sites working smoothly, our tracking prevention implementation groups such domains together and exempts storage/resource blocks when a domain in one organization requests resources from another domain in that same organization.
In order to keep sites that users engage with working as expected while also increasing the types of trackers that we block by default, we combined the concept of an organization together with site engagement to create a new mitigation. This mitigation takes effect whenever a user has established an ongoing relationship with a given site (currently defined by a site engagement score of 4.1 or greater). For example, consider the following organization which owns two domains:
Social Org
social.example
social-videos.example
A user will be considered to have a relationship with Social Org if they have established a site engagement score of at least 4.1 with any one of its domains.
If another site, content-embedder.example, includes third-party content (say an embedded video from social-videos.example) from any of Social Org’s domains that would normally be restricted by tracking prevention, it will be temporarily allowed as long as the user’s site engagement score with Social Org’s domains is maintained above the threshold.
If a site does not belong to an organization, a user will need to establish a site engagement score of at least 4.1 with it directly before any storage access/resource load blocks imposed by tracking prevention will be lifted.
What does this mean?
By exempting sites and organizations that you have an ongoing and established relationship with from tracking prevention, we can ensure that the web services and applications you care about continue to work as you expect across the web. Leveraging site engagement also allows us to only unblock content that is likely to be important to you and reflects your current needs. This ensures that actions such as briefly visiting a site or seeing a popup aren’t enough to unblock content by themselves. If content does get unblocked due to you interacting with a site, it is always unblocked in a temporary manner that is proportional to how highly engaged you are with that site/its parent organization. By combining these exemptions with more strict blocking of trackers by default, we can provide higher levels of protection while still maintaining compatibility on the ever-evolving set of sites that you engage with.
It’s worth noting that tracking prevention, when enabled, will always block storage access and resource loads for sites that fall into the Fingerprinting or Cryptomining categories on Disconnect’s tracking protection lists. We will also not apply the site engagement-based mitigation outlined above for our most privacy-minded users who opt into tracking prevention’s Strict mode.

The best way to learn what’s changed with tracking prevention in Microsoft Edge 79 is to take a look at the table below:
Along the top are the categories of trackers as defined by Disconnect’s tracking protection list categories.
Along the left side are comparisons of the improvements made to our tracking prevention feature broken down into Basic, Balanced, and Strict.
The letter “S” in a cell denotes that storage access is blocked.
The letter “B” in a cell denotes that both storage access and resource loads (i.e. network requests) are blocked.
A “-“ in a cell denotes that no block will be applied to either storage access or resource loads.
The “Same-Org Mitigation” refers to the first mitigation that we introduced in our previous blog post and recapped above.
The “Org Engagement Mitigation” refers to the second mitigation based on site engagement that we introduced earlier in this post.

Advertising
Analytics
Content
Cryptomining
Fingerprinting
Social
Other
Same Org Mitigation
Org Engagement Mitigation
Basic

Microsoft Edge 78



B
B


Enabled
Not impl.
Microsoft Edge 79



B
B


Enabled
N/A
Balanced

Microsoft Edge 78
S


B
B
S

Enabled
Not impl.
Microsoft Edge 79
S

S
B
B
S
S
Enabled
Enabled1
Strict 2

Microsoft Edge 78
B
B

B
B
B
B
Enabled
Not impl.
Microsoft Edge 79
B
B
S
B
B
B
B
Enabled
Disabled
Does not apply to Cryptomining or Fingerprinting categories.
Strict mode blocks more resource loads than Balanced. This can result in Strict mode appearing to block less tracking requests than Balanced since the trackers making the requests are never even loaded to begin with.
With our recent updates in Microsoft Edge 79, we have seen, on average, 25% more trackers blocked in Balanced mode. Close monitoring of user feedback and engagement time also showed no signs of negative compatibility impact, suggesting that the org engagement mitigation is effective at minimizing breakage on sites that users actively engage with. While this does mean that top sites have the org engagement mitigation applied more often, we believe this is an acceptable tradeoff versus compatibility, especially as more top sites are starting to give users mechanisms to transparently view, control, and delete their data.
As with all our features, we’ll continue to monitor telemetry and user feedback channels to learn more and continually improve tracking prevention in future releases. We are also exploring additional compatibility mitigations such as the Storage Access API, which we intend to experiment with in a future version of Microsoft Edge.
InPrivate Changes
In our previous blog post, we mentioned that users browsing in InPrivate will automatically get Strict mode protections. By listening to the feedback our users provided, we found that this led to unexpected behavior (such as causing sites that worked in a normal browsing window to fail to load InPrivate) and broke some important use cases. That’s why in Microsoft Edge 79, your current tracking prevention settings will be carried over to InPrivate sessions.
We are currently experimenting in our Canary and Dev channels with a switch at the bottom of our settings panel (which you can reach by navigating to edge://settings/privacy) that will allow you to re-enable Strict mode protections InPrivate by default:

We’ve also made it easier for you to view the trackers that Microsoft Edge has blocked for you. Navigate to edge://settings/privacy/blockedTrackers to test out this new experience today!

We’d love to hear your thoughts on our next iteration of tracking prevention. If something looks broken, or if you have feedback to share on these changes, we’d love to hear from you. Please send us feedback using the “smiley face” in the top right corner of the browser.
Send feedback at any time with the Send a Smile button in Microsoft Edge

As always, thanks for being a part of this journey towards a more private web!
–  Scott Low, Senior Program Manager–  Brandon Maslen, Senior Software Engineer

Join the Microsoft Edge team next week at Ignite 2019 – Microsoft Edge Blog

Next week, we will be travelling to Microsoft Ignite 2019 to share what’s new in Microsoft Edge for enterprises, IT professionals, and web developers. We’re very excited to share more about our journey with Chromium over the past year, what it means to your customers, and to hear your feedback.In this post, we’ve outlined all the breakout sessions and other activities our team will be presenting at Ignite next week, so you can easily track which sessions you want to attend or review later. This year, Ignite is also introducing Roundtable Topics, which are a great opportunity to share your experiences with the product team directly, provide feedback, and help us understand how we can empower you and your organization with Microsoft Edge.
The full list of sessions is provided below. We look forward to seeing you there! Don’t miss out—sign in using your attendee or tech community account to build your Ignite schedule today!

Monday, November 4th
2:00 – 2:45 PM ET: BRK012 – The Web: Where the rubber hits the road on security and manageability, and productivity
Join VP of Product for Microsoft Edge, Chuck Friedman, Group Product leader for Microsoft Edge Enterprise, Sean Lyndersay, and VP of Bing, Jordi Ribas to discuss how Microsoft Edge and Microsoft Search in Bing is the best browser and search for business. We can help you with a systematic approach to identity and security, high-performing intranet and internet searches, and how to think about web and app compatibility on the internet.
3:15 – 4:00 PM ET: BRK1019 – State of the browser: Microsoft Edge
Come learn about the history of Microsoft Edge and the decision to move to Chromium as well as the roadmap for enterprises and show you the 4 pillars of what the team focuses on: Rock solid fundamentals, Safety and Security, Flexible and efficient manageability and deployment, and end-user productivity.
Tuesday, November 5th
11:05 – 11:20 AM ET: MLS1020 – Microsoft Edge and Chromium: What’s new for web developers
In this Microsoft Ignite Live session, Burke Holland will interview Kyle Pflug, PM for Microsoft Edge Developer Experiences, about what the new Chromium foundation means for your web sites and web apps, and how the Microsoft Edge team is working with web standards and the Chromium community to build a better web for everyone.
1:50 – 2:10 PM ET: THR2279 – Mechanics Live: Microsoft Edge and Microsoft Search: Complete tour for IT admins and users
Join Chuck Friedman and Jeremy Chapman to get a comprehensive understanding of the enterprise-focused capabilities in the new Microsoft Edge browser. This is a 20-minute Theater session filmed in the Mechanics Live studio in the hub and you are a part of the experience.
3:05 – 3:25 PM ET: THR108 – Top 10 reasons why you’ll choose the next version of Microsoft Edge
We’re on a mission to create the best browser for the enterprise. We believe the next version of Microsoft Edge is that browser and in this session, we will share the top 10 reasons why.
Roundtable Topics
Wednesday, November 6th
 10:15 – 11:00 AM: BRK2230 – One browser for modern and legacy web apps: deploying Microsoft Edge and IE mode
We have worked with numerous companies – ranging from 1,000’s to 100,000’s of seats – to move from multiple browser environments to a single browser environment. We’ll share lessons learned and best practices for piloting and deploying the next version of Microsoft Edge by leveraging our investments in Internet Explorer mode, Configuration Manager, and Intune.
1:50 – 2:10 PM ET: THR1075 – Enterprise ready PDF solution in Microsoft Edge
Customers have communicated they want a PDF solution in the browser, so they don’t have to manage additional 3rd party software. The Microsoft Edge’s PDF solution will help you understand the investments we’re making so we can accomplish that specific feedback.
Roundtable Topics
Thursday, November 7th
12:45 – 1:30 PM ET: BRK3099 – Moving the web forward: Microsoft Edge for web developers
The next version of Microsoft Edge is built on a new foundation, powered by Chromium. This foundation will empower you with a consistent set of developer tools and enable you to deliver powerful standards-based and hybrid application experiences using web technologies. In this session, we’ll share how our upcoming release simplifies cross-browser testing and enables the latest capabilities for your sites and line of business (LOB) apps, plus our ongoing contributions to Chromium that improve the browser experience for everyone. Finally, we’ll reveal what’s next for web developers in the new Microsoft Edge.
3:40 – 4:00 PM ET: THR106 – Microsoft Edge on macOS
Microsoft Edge will be our first browser for macOS in 13 years. In this session, we share how Microsoft Edge feels at home on macOS, how you can be more productive and secure using it, and what you need to know about managing Microsoft Edge on macOS.
Roundtable Topics
Friday, November 8th
10:15 – 11:00 AM ET: BRK3253 – Protected, productive mobile browsing with Microsoft Edge and Intune
Microsoft Edge isn’t just a desktop browser. The mobile platform has been going strong for close to 2 years. This session will show you the investments we’re making to allow for a full range of experiences starting with management capabilities with Intune, customizing the end user experience, and how to migrate from the Microsoft Intune managed browser to Microsoft Edge.
11:30 AM – 12:15 PM ET: BRK2231 – Keep users productive and data secure in a cloud-first world: secure browsing with Microsoft Edge
Wrap up your Friday with a deep dive on all things security regarding Microsoft Edge. Features such as Application Guard, Conditional Access, and Microsoft Information Protection will be discussed along with other security measures to show you how Microsoft Edge is the most secure browser in the enterprise.
See you there! Don’t forget to sign in using your attendee or tech community account to build your Ignite schedule today!
– Colleen Williams, Senior Program Manager, Microsoft Edge

Update on removing Flash from Microsoft Edge and Internet Explorer – Microsoft Edge Blog

In 2017, we published a roadmap to remove Adobe Flash from Microsoft Edge and Internet Explorer by 2020. Since that post, we announced our intent to build Microsoft Edge on the Chromium open source project. In this post, we will provide an update on what to expect for the Flash retirement in Microsoft browsers.Here’s what you can expect for each Microsoft browser:
In the next version of Microsoft Edge (built on Chromium), we will continue to retire Flash in the same timeframe as other Chromium based browsers. You can learn more of that timeline in this blog post. Flash will initially be disabled, and the user will need to re-enable Flash on a site-by-site basis; Flash will be completely removed from the browser towards the end of 2020. Group policies are available for enterprise admins and IT pros to change the Flash behavior prior to that date.
For both the in-market version of Microsoft Edge (built on EdgeHTML) and Internet Explorer 11, the current experience will continue as-is through 2019. Specifically, we no longer intend to update either Microsoft Edge (built on EdgeHTML) or Internet Explorer 11 to disable Flash by default. We still plan to fully remove Flash from these browsers by December 2020, as originally communicated.
– Colleen Williams, Senior Program Manager, Microsoft Edge
[Updated to clarify the in-market EdgeHTML/IE experience – Ed.]

Collections is now available to test in the Canary channel – Microsoft Edge Blog

Today, we’re releasing an experimental preview of Collections for Microsoft Edge. We initially demoed this feature during the Microsoft Build 2019 conference keynote. Microsoft Edge Insiders can now try out an early version of Collections by enabling the experimental flag on Microsoft Edge preview builds starting in today’s Canary channel build.We designed Collections based on what you do on the web. It’s a general-purpose tool that adapts to the many roles that you all fill. If you’re a shopper, it will help you collect and compare items. If you’re an event or trip organizer, Collections will help pull together all your trip or event information as well as ideas to make your event or trip a success. If you’re a teacher or student, it will help you organize your web research and create your lesson plans or reports. Whatever your role, Collections can help.
The current version of Collections is an early preview and will change as we continue to hear from you. For that reason, it’s currently behind an experimental flag and is turned off by default. There may be some bugs, but we want to get this early preview into your hands to hear what you think.

To try out Collections, you’ll need to be on the Canary Channel which you can download from the Microsoft Edge Insider website.
Once you’re on the right build, you’ll need to manually enable the experiment. In the address bar, enter edge://flags#edge-collections to open the experimental settings page. Click the dropdown and choose Enabled, then select the Restart button from the bottom banner to close all Microsoft Edge windows and relaunch Microsoft Edge.

Once the Collections experiment is enabled, you can get started by opening the Collections pane from the button next to the address bar.

Drag/drop: When you have the Collections pane open, you can add specific content from a webpage with drag and drop. Just select the image, text, or hyperlink and drag it into the collection.

Context menu: You can also add content from a webpage from the context menu. Just select the image, text, or hyperlink, right-click it, and select Add to Collections. You can choose an existing collection to add to or start a new one.

When you add content to Collections, Microsoft Edge creates a visual card to make it easier to recognize and remember the content. For example, a web page added to a collection will include a representative image from that page, the page title, and the website name. You can easily revisit your content by clicking on the visual card in the Collections pane.

You’ll see different cards for the different types of content you add to Collections. Images added to a collection will be larger and more visual, while full websites added to a collection will show the most relevant content from the page itself. We’re still developing this, starting with a few shopping websites. Content saved to a collection from those sites will provide more detailed information like the product’s price and customer rating.

Add notes: You can add your own notes directly to a collection. Select the add note icon from the top of the Collections pane. Within the note, you can create a list and add basic formatting options like bold, italics, or underline.
Rearrange: Move your content around in the Collections pane. Just click an item and drag and drop it in the position you prefer.
Remove content: To remove content from your collection, hover over the item, select the box that appears in the upper-right corner, and then select the delete icon from the top of the Collections pane.

Once you’ve created a collection, you can easily use that content by exporting it. You can choose to export the whole collection or select a subset of content.
Send to Excel: Hit the share icon from the top of the Collections pane and then select Send to Excel. Your content will appear on a new tab with pre-populated table(s) that allow you to easily search, sort, and filter the data extracted from the sites you added to your Collection. This is particularly useful for activities like shopping, when you want to compare items.

Copy/paste: Select items by clicking the box in the upper right. A gray bar will appear at the top of the Collections pane. Select the copy icon to add those items to your clipboard. Then, paste it into an HTML handler like Outlook by using the context menu or Ctrl+V on your keyboard.
Sending content to Excel is available for Mac and Windows devices running Windows 10 and above. We’ll add support for Windows devices running Windows 7 and 8 soon. Additional functionality, like the ability to send to Word, will also come soon.

This is the just the first step in our Collections journey and we want to hear from you. If you think something’s not working right, or if there’s some capability you’d like to see added, please send us feedback using the smiley face icon in the top right corner of the browser.

Thanks for being a part of this early preview! We look forward to hearing your feedback.
– The Microsoft Edge Team

An update on disabling VBScript in Internet Explorer 11 – Microsoft Edge Blog

In early 2017, we began the process of disabling VBScript in Internet Explorer 11 to give the world the opportunity to prepare for it to be disabled by default.The change to disable VBScript will take effect in the upcoming cumulative updates for Windows 7, 8, and 8.1 on August 13th, 2019. VBScript will be disabled by default for Internet Explorer 11 and WebOCs for Internet and Untrusted zones on all platforms running Internet Explorer 11. This change is effective for Internet Explorer 11 on Windows 10 as of the July 9th, 2019 cumulative updates.
The settings to enable or disable for VBScript execution in Internet Explorer 11 will remain configurable per site security zone, via Registry, or via Group Policy, should you still need to utilize this legacy scripting language.
To provide feedback on this change, or to report any issues resulting from this change, you can use the Feedback Hub app on any Windows 10 device. Your feedback goes directly to our engineers to help make Windows even better.
– Brent Mills, Senior Program Manager

The next version of Microsoft Edge: Enterprise evaluation and roadmap – Microsoft Edge Blog

This week at the Microsoft Inspire 2019 conference, we are sharing an update on capabilities that we are investing in to make the next version of Microsoft Edge the best browser for enterprises and business customers of all sizes.The Dev Channel now has enterprise features enabled by default and is ready for evaluation and supported by detailed deployment and configuration documentation. We are also offering full support for deployment in pilot and production environments through our commercial support channels.
Dev channel builds, including offline installers and ADMX files, are available at https://www.microsoftedgeinsider.com/enterprise. We’re excited to hear from you about how these enterprise-focused features work in your environment and improve end user productivity.

In the rest of this post, we’ll share the updates we are covering at Inspire, and outline our goals and roadmap for Microsoft Edge for enterprises and business customers.
Fundamentals first
To make the next version of Microsoft Edge a great browsing experience for enterprise and business customers, we begin with the fundamentals: compatible with the modern web, fully supported across platforms, and kept secure, up-to-date, and consistent across devices. Our adoption of open source software, announced last December, coupled with a complete re-building of our engineering, deployment, and update systems, is enabling us to deliver on these commitments.
You may have already seen our new updating system in action with our Canary and Dev Channels. The preview builds deliver daily and weekly builds to all devices automatically, across all supported Windows platforms and Mac OS. These desktop platforms join the Microsoft Edge for iOS and Android platforms, (which have rich support for enterprise management with Microsoft Intune).
Internet Explorer mode
One of the features available for evaluation is Internet Explorer mode, a feature that integrates IE11 natively into Microsoft Edge. Internet Explorer mode allows users to navigate seamlessly from a modern web application to one that requires legacy HTML or plugins. You’ll no longer need a “two-browser” solution.
We know that most of our customers are using IE11 in their environments. One thing that our customers made clear to us is that their web apps that rely on IE11 tend to be critical to many of their business processes. The apps work well and don’t change, which allows customers to focus their IT resources on other problem areas. Any solution we provide would need to just work with their sites.
The team designed Internet Explorer mode to meet that need, with a goal of 100% compatibility with sites that work today in IE11, including full support for IE’s doc modes, as well as ActiveX controls, like Silverlight and Browser Helper Objects (BHOs). In addition, Internet Explorer mode appears visually like it’s just a part of the next Microsoft Edge, providing users with the latest UI features, like a smarter address bar and new tab page, and greater privacy controls for the modern web.
By leveraging the Enterprise mode site list that many customers have already built and deployed to support the two-browser solution, IT professionals can enable users of the next Microsoft Edge to simply navigate to IE11-dependent sites and they will just work. Navigating back to a modern site will be seamless. No need for a separate window or tab.
For more background on Internet Explorer mode, please check out this video discussing Microsoft Edge enterprise compatibility.
Simple to deploy and manage
Another goal of ours is to make Microsoft Edge the easiest browser deployment decision customers have ever made. This is true particularly if you have existing investments in Microsoft 365 and Microsoft technologies, but we are also deeply committed to making sure that Microsoft Edge works well with first- and third-party management tools.
The next version of Microsoft Edge supports a range of Group Policies, allowing customers to configure every aspect of the deployment and product experience. We will also support Mobile Device Management (MDM) deployments on Windows 10 (via Microsoft Intune or third-party products), as well as popular deployment and management tools on Mac OS.
Customers will be able to control the flow of updates, either by leveraging our general updating mechanisms and using policies to pause updates at a particular version while testing compatibility with a small set of pilot users, or by using the provided offline installers (MSIs and PKGs) to push updates directly to their managed devices on their own schedule.
For those customers using System Center Configuration Manager (SCCM) or Microsoft Intune, we’re working to make the deployment and configuration experience as easy as possible. We will also work with third parties, ensuring that deploying and configuring Microsoft Edge is a great experience with those tools as well.
Keeping customers and data protected
Customers tell us that their users spend 60% or more of their time on a desktop or laptop PC in a browser, making the security of the browser critical to the integrity of the organizational environment and data.
In addition to fundamental security features that are derived from Chromium (e.g. sandboxing and site isolation), our teams are working with the Chromium Security teams to help improve the core security of all Chromium-based browsers on Windows.
We’re also engineering our update systems to ensure that we can respond to vulnerabilities and get fixes out to customers as quickly as possible.
The current version of Microsoft Edge has a number of security innovations that we intend to bring forward to the next version of Microsoft Edge. This includes integrating our industry-leading Microsoft Defender SmartScreen technology into the next browser on all our supported platforms, in order to help protect users from phishing, malware, and scams.
We’re also bringing forward some of the enterprise-class security innovations that we pioneered in our existing version of Microsoft Edge, including:
Application Guard on Windows 10, a Hyper-V based technology that isolates general internet browsing into a container to protect the corporate network from exploits
Azure AD Conditional Access to help organizations keep their users productive while controlling access to corporate sites
Microsoft Information Protection to help organizations manage what users can do with the data they access through the browser
More productive at work
We’ve heard from administrators and individuals within organizations that we have an opportunity with Microsoft Edge to make daily activities easier and empower people to get more done.
Balancing compliance and access to information shouldn’t be a tradeoff. Microsoft Edge natively supports signing into the browser with Azure Active Directory (AAD) work or school accounts. This means users’ favorites and other browser data can be synced securely between devices, including Windows, macOS, iOS and Android devices, while respecting your organization’s compliance requirements. Also, once signed-in to the browser, Single Sign-on ensures that access to corporate sites will just work.
Searching for information is, of course, one of the top activities that people do in a browser, and perhaps the need is even higher for finding information within the corporate network. By combining the next Microsoft Edge with the power of the Microsoft Graph, we’re investing to bring your organization’s information to your users’ fingertips.
Every time a user opens a new tab or starts a new task, they see the new tab page (NTP). In the next version of Microsoft Edge, an Enterprise-focused NTP will be available to empower people with fast access to what they need. Users will see the corporate web apps, documents, and sites they use most, as well as recommended content from Office 365. Whether it’s highlighting the document they were collaborating on with a colleague or making them aware of important company-wide communications, the NTP dynamically brings information that’s relevant to each person.
To find internal information, what could be simpler than using the search box to find what you’re looking for? We’re infusing Microsoft Edge with native support for Microsoft Search in Bing for Microsoft 365 customers. Microsoft Search in Bing integration makes the Edge search box a one-stop shop for results from the web and from the corporate network, using Microsoft AI to extract the most relevant and useful information from the network. Administrators can even customize the suggestions and results for their specific environment.
Our commitment to online privacy protections
At Build 2019, we shared our commitment to offering greater transparency and control over your online data and highlighted one specific feature we’re working on: tracking prevention. Tracking prevention is designed to protect you from being tracked by websites that you aren’t accessing directly. Whenever a website is visited, trackers from other sites may save information in the browser using cookies and other storage mechanisms. This information may include the sites you’ve visited and the content you’re interested in, building a digital profile which can be accessed by organizations to offer personalized content when visiting other sites.
Tracking prevention is still being tested, but this feature, as well as all other privacy tools we introduce for consumer, will be available to our enterprise customers – both IT administrators and end users.

We’re excited to get these features into your hands to start hearing your feedback.
Many of the features described in the roadmap are available today in our Insider channels. Some start rolling out on our servers today and will slowly roll out over the next couple weeks. Others are still in development and will come in later updates. We believe that with today’s announcement, the enterprise feature set is complete enough for most companies to start evaluations and pilots.
Here is a breakdown of what features are available today, rolling out soon or coming in the future:

These features represent only the beginning of our commitment to making Microsoft Edge the best browser for your business across platforms, especially if you have invested in Microsoft 365.
We eagerly await your comments via the feedback tool in the new Microsoft Edge Preview builds, post in the Microsoft Edge Insider forums, or, if you are a Microsoft customer, start a conversation with your account teams today.
– Sean Lyndersay, Group Program Manager– Colleen Williams, Senior Program Manager

Introducing tracking prevention, now available in Microsoft Edge preview builds – Microsoft Edge Blog

Today, we’re releasing an experimental preview of tracking prevention for Microsoft Edge. We initially demoed this feature at Build 2019 as one of the concepts we’re exploring to offer greater transparency and control over your online data. Microsoft Edge Insiders can now try out tracking prevention by enabling the experimental flag on Microsoft Edge preview builds starting with version 77.0.203.0 (today’s Canary channel release). (Note: Today’s Canary release is not currently available for macOS due to a build issue. Tracking prevention will be available in the next update to the Canary channel on macOS.)
Tracking prevention is designed to protect you from being tracked by websites that you aren’t accessing directly. Whenever a website is visited, trackers from other sites may save information in the browser using cookies and other storage mechanisms. This information may include the sites you’ve visited and the content you’re interested in, building a digital profile which can be accessed by organizations to offer personalized content when visiting other sites.
The implementation in Microsoft Edge Insider preview builds is early and is likely to change as we hear from our customers and continue to test the feature. For that reason, it’s currently behind an experimental flag and disabled by default. There may be some bugs or site issues, but we want to get it into your hands to hear what you think.

To try out tracking prevention, you’ll need to be on a Microsoft Edge Insider preview build (version 77.0.203.0 or higher – or at least today’s Canary channel release). Once you’re on the right build, you’ll need to manually enable the experiment.
In the address bar, enter edge://flags#edge-tracking-prevention to open the experimental settings page. Click the dropdown and choose Enabled, then click the Relaunch Now button to close all Microsoft Edge windows and relaunch Microsoft Edge.

Tracking prevention can be enabled via edge://flags

That’s it! Once the tracking prevention experiment is enabled, you can go to the Microsoft Edge privacy settings page to control settings for tracking prevention. In the address bar, enter edge://settings/privacy and adjust the settings as desired:

The default tracking prevention setting is Balanced, which blocks 3rd party trackers and known malicious trackers for an experience that balances privacy and web compatibility. You can customize tracking prevention to your preferences by setting it to Strict, which blocks the majority of 3rd party trackers, or Basic, which only blocks malicious trackers.

When blocking a tracker, we aim to stop it from accessing previously stored tracking information and storing new tracking information. When tracking resources don’t add meaningful functionality to the page, we may even block them entirely. In order to do this, tracking prevention is made up of three main components.

Classification: How we determine what is considered a tracking URL.
Enforcement: The actions we take to protect our users from trackers.
Mitigations: The mechanisms we use to make sure your favorite sites still work, while offering strong default protection.

Classification
We’ve added a new component to Microsoft Edge, Trust Protection Lists, that contains the latest information on which organizations may be trying to track users on the web. This component allows us to be flexible with where we source details on what a tracker is and when we deliver updated lists to our users.
To check if the URL is considered a tracker by our classification system, we check a series of hostnames, starting with an exact match and then proceeding to check for partial matches for up to 4 labels beyond the top-level domain.
Example:
URL: https://a.subdomain.of.a.known.tracker.test/some/path
Tested hostnames:

subdomain.of.a.known.tracker.test
a.known.tracker.test
known.tracker.test
tracker.test
test

If any of those hostnames represents a known tracker, we proceed with evaluating enforcement actions intended to prevent the user from being tracked.
Enforcement
To provide protection for our users from tracking actions on the web, we take two enforcement actions against trackers:

Restrict storage access: If a known tracking resource tries to access any web storage where it may try to persist data about the user, we will block that access. This includes restricting the ability for that tracker to get or set cookies as well as access storage APIs such as IndexedDB and localStorage.
Block resource loads: If a known tracking resource is being loaded on a website, we may block that load before the request reaches the network depending on its compatibility impact and the tracking prevention setting you have set. Blocked loads may include tracking scripts, “pixels”, iframes, and more. This prevents any data potentially being sent to the tracking domain and may even improve load times and performance of the page as a side effect.

You can view the number of trackers blocked on a page by clicking the page info button next to the URL in the address bar at the top of the browser. Here you can change the tracking prevention setting on a site by site basis if you trust a site, or if something doesn’t seem to be working properly.
Mitigations
The web is a complex place and we realize there is no “one size fits all” solution to privacy. Depending on the mode of tracking prevention you enable, we will take different actions to balance our enforcement and put you in control of your personal experience on the web.
Tracker categorization
Every tracking resource is classified into a category that best represents the type of tracking activities it performs. Every tracking prevention mode uses a set of categories to represent what types of trackers will have storage access restricted or resource loads blocked.
Not all types of trackers are equal. Fingerprinting trackers are those trackers that attempt to identify you, or your browser based on its unique characteristics. Cryptomining scripts are scripts that attempt to abuse your processor and memory to generate cryptocurrencies, reducing your browser’s performance and battery life. Even when you’ve opted into our Basic mode you will be protected from these egregious types of tracking.
By default, in Balanced, all users will get a robust set of tracker categories that have storage access blocked, and a slightly smaller set that have resource loads blocked. We have taken care to ensure that these sets provide protection while ensuring compatibility as you browse the web and use your favorite applications. For example, Balanced will allow third party content to enable login flows using third party identities or social network commenting on third party sites.
Our Strict mode provides the largest set of categories to block storage access and resource loads. This is for users who don’t mind a little bit of site breakage in exchange for greater protection. This is also the default level of protection when you launch an InPrivate window.
Organizations
Not all organizations do business on the internet using just one domain name. In order to help keep sites working smoothly, we group domains owned and operated by the same organization together. For instance, we might have a grouping that says “Org1” owns the domains “org1.test” and “org1-cdn.test”. If the user visits https://org1.test/, and it tries to load a resource from https://org1-cdn.test/, we won’t take any enforcement actions against that auxiliary domain even though it’s not a first party URL. However, if another organization, Org2 (https://org2.test/), tries to load that same resource, it would be subject to restrictions because it is not part of the same organization.
We are currently experimenting with ways to provide even greater privacy protection by investigating opportunities to expand the types of trackers we block for you. For the Balanced setting, we may start to consider your recent interactions with sites. For example, for sites that you interact with in a first party context on a regular basis, access to cookies, localStorage, IndexedDB and other storage may be allowed in a broader context to ensure web functionality, like login flows or social network commenting, just works. For sites you don’t visit, we may more aggressively block that content in a third-party context. This will let us improve protection while the sites you care about continue to work across the web.
For our enterprise customers, we are experimenting with exposing policies to allow the right balance of control in order to ensure all their users are protected and existing line of business apps continue to work.

In order to help web developers identify trackers on their websites that may be affected by this feature, we’ve added some DevTools console messages to show when enforcement actions are taken. These can be used to see exactly what was restricted and help identify which parts of a site may need to be better tailored towards protecting a user’s privacy.

We want to hear from you about this feature. If you think something’s not working right or it’s blocking too much or too little, please send us feedback using the “smiley face” icon in the top right corner of the browser.

If you’re a web developer, try out the DevTools experience with tracking preventing enabled and let us know what you think. If you’re a web surfer, catch some waves and let us know how tracking prevention fits into your browsing habits.
We’ll use your feedback on this experimental feature in the Canary and Dev channels to understand potential impact to web compatibility and iterate on the experience to be helpful and easy to use.
As we gather feedback and continue to tune the feature, we will begin rolling out tracking prevention to a broader audience.
Thanks for being a part of this early preview!
– Brandon Maslen, Senior Software Engineer– Ryan Cropp, Software Engineer

Introducing Microsoft Edge preview builds for Windows 7, Windows 8, and Windows 8.1 – Microsoft Edge Blog

Today we are excited to make preview builds from the Microsoft Edge Canary channel available on Windows 7, Windows 8, and Windows 8.1. This rounds out the initial set of platforms that we began to roll out back in April, so developers and users alike can try out the next version of Microsoft Edge on every major desktop platform.
Visit the Microsoft Edge Insider site from your Windows 7, 8, or 8.1 device to download and install the preview today! The Microsoft Edge Dev channel will be coming to previous versions of Windows soon.

You will find the experience and feature set on previous versions of Windows to be largely the same as on Windows 10, including forthcoming support for Internet Explorer mode for our enterprise customers.
Delivering the next version of Microsoft Edge to all supported versions of Windows is part of our goal to improve the web browsing experience for our customers on every device, and to empower developers to build great experiences with less fragmentation. Microsoft Edge will have the same always up-to-date platform and the same developer tools on all supported versions of Windows and macOS. This will reduce developer pain on the web, while ensuring all Windows customers have the latest browsing options.
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. If you run into any issues or have feedback, please use the “Send Feedback” tool in Microsoft Edge. Simply click the smiley face next to the Menu button and let us know what you like or if there’s something we can improve.
The first Canary builds do have a few known issues, including the lack of dark mode support and no support for AAD sign-in, which we are working to resolve soon. If you need help or support, just press F1 from within Microsoft Edge Canary or Dev to visit our support website.
We hope you’ll try the preview out today, and share your feedback in the Microsoft Edge Insider community. We look forward to hearing what you think!

Introducing the first Microsoft Edge preview builds for macOS – Microsoft Edge Blog

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.
Building a “Mac-like” user experience for Microsoft Edge
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.
 
Introducing the Microsoft Edge Insider Channels for macOS
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.

A consistent platform and tools for web developers
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.
Sharing your feedback
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
Updated May 20, 2019 8:07 pm