Microsoft is once again urging companies that depend on IE mode, Edge's Internet Explorer compatibility feature, to start planning the migration of their business apps. No new end date has been set, and the existing policy of supporting the feature through at least the end of 2029 still stands. But modernizing legacy apps can take years, depending on how many dependencies there are and how complex they are. Even companies that have already made Edge their default browser may still have app migration work ahead if they continue to rely on IE technology inside it.
2029 Is Not a Confirmed End Date
The latest notice reaffirms the support policy announced in 2021. According to The Register, Microsoft used a message in its admin center to call on organizations to modernize existing systems that depend on IE technology. The takeaway for companies is not that the feature will stop working tomorrow, but that it is time to turn migration plans into concrete ones.
When reading the deadline, it is important to distinguish between "at least through 2029" and "ending in 2029." Microsoft's lifecycle FAQ says IE mode will be supported through at least 2029 on supported operating systems. It also states the following about any end-of-support announcement:
"Microsoft will provide at least one year of notice before IE mode support ends."
This condition means you cannot assume IE mode will stop the moment 2030 begins. At the same time, the latest notice does not confirm how far support will extend beyond 2029. Nor is it a promise that you can wait for an end date to be announced before starting. The minimum notice period and the time your own migration needs should be estimated separately.
It also helps to keep this apart from the end of the IE11 desktop app. Support for that ended on June 15, 2022, on certain operating systems, while IE mode inside Edge has been maintained separately. Although both carry the IE name, the standalone browser and the compatibility feature are covered differently.
Why IE Dependencies Remain After Moving to Edge
Edge's IE mode does not automatically convert old sites to modern web technology. According to Microsoft's technical documentation, regular sites use the Chromium engine, while legacy sites use the Trident MSHTML engine from IE11. Users see a single browser, but different engines handle the pages behind the scenes.
The compatibility it preserves includes ActiveX controls, a mechanism long used to let web pages draw on additional software components. IE mode also supports legacy document modes, which helps organizations keep using sites built for IE. However, some features, such as IE toolbars, are not supported, so it is not a guarantee that every IE capability is reproduced as is.
Companies can manage which sites open in IE mode through tools such as the Enterprise Mode Site List. Being able to handle regular sites and sites that need compatibility in a single browser is an operational advantage. On the other hand, the fact that employees open Edge every day does not tell you whether business apps now run on the standard engine.
For example, if an internal system can complete its processing only in IE mode, that system still needs the compatibility feature even if the company has finished rolling out the browser. When planning app migration, the most revealing question is not how many devices have Edge installed, but what would stop working if IE mode were turned off. Because the compatibility feature exists, organizations can keep operations running while deciding the order in which to modify their apps.
Check the OS Support Conditions Too
Microsoft's support policy comes with a condition: it applies on supported operating systems. So the fact that IE mode is supported through 2029 does not mean Windows itself can keep being used as is. Whether each device's OS is still supported needs to be checked separately.
The official FAQ explains that if you continue to receive security updates after an OS reaches end of support, you may need an Extended Security Updates (ESU) license, where available. The IE mode documentation also calls for applying the latest Windows and Edge updates. Knowing how long IE mode will be supported and keeping the devices actually in use in a supported state are both necessary tasks.
The same caution applies to the components used by apps. That IE mode can handle ActiveX does not mean each embedded component will continue to be maintained. Microsoft's documentation lists Silverlight as an example of a supported feature but notes that its support has already ended. Confusing something that works with something that is still supported, components included, can lead to overlooking what needs updating.
In short, a migration plan built around the browser alone will fall short. When identifying the sites that open in IE mode, also check the OS of the devices in use and the components the business apps require. Only with that combination can you decide what to update first.
Start by Finding Which Operations Open in IE Mode
A practical place for administrators to begin is matching the IE mode site list against actual usage. Confirming whether the sites left in the settings are the same as those now used for work helps narrow the scope of the investigation. Microsoft's notice likewise encourages taking inventory of dependencies and considering how to modernize, whether by updating or replacing apps.
In practice, linking each URL on the list to a business function and an owner makes later decisions easier. For apps the company can modify itself, investigate what needs changing; for products from outside vendors, check whether a version that supports standard mode exists. Items that need replacement or rebuilding can be listed in the plan separately from those that only need maintenance updates.
Testing should also go beyond checking whether the top page displays. For a task in which users log in, enter data, and print a report, for example, try that whole sequence in standard mode. This is a way of deciding test items to suit each company's systems, not a claim that every app can be migrated by the same procedure.
As well as watching for any formal end-of-support notice, organizations should confirm whether they can finish the necessary work from start to finish without IE mode. Once owners and test scope are set and processing in standard mode has been verified, they can steadily reduce the number of sites that depend on the compatibility feature.