Classic Outlook closes suddenly for an incompatibility with Teams: Microsoft already launched the correction and asks to update

During the last few weeks several Microsoft 365 users found themselves with an annoying problem: their classic Outlook client began to close unexpectedly and in many cases offered to start the application safely. Microsoft confirmed that the cause was an incompatibility between old versions of Outlook and the latest version of the Teams meeting complement, and has already deployed a correction that should return normal to most teams.

The origin of the decision was a lack of coordination between buildings: teams with classic Outlook in old versions that loaded the new Teams Meeting Add-in (build 1.26.02603) were blocked. Microsoft noted that, for example, the facilities in Current Channel with Outlook equal to or prior to Version 2402 (Build 17328.20142) were especially likely to hit that complement. The company registered the incident on its service panel and published a support note with technical details and the state of the repair; you can see the incident entry at the Microsoft 365 management center at EX1254044 and the explanation in the support document updated in support.microsoft.com.

The good news is that Microsoft indicates that the problem is already solved: the solution is being distributed through an update of Microsoft Teams (version 26058.712.4527.9297). To ensure that the error disappears, the official recommendation is to update both Teams and the classic Outlook client to their latest versions. If possible, apply those updates should remove unexpected closures and prevent Outlook from opening safely.

If for some reason it cannot be updated immediately - for example, in corporate environments with strict change controls or specific version dependencies - there are temporary alternatives. One option is to run online repair of Office (Online Repair) applications to reinstall the client and its components; Microsoft maintains a guide on how to carry out that repair in support.microsoft.com (Repair an Office application). Another provisional solution is to disable the Teams meeting complement from Outlook: opening Outlook in safe mode (holding the Ctrl key when starting the application or following the instructions in How to Open Outlook in Safe Mode), and from there go to File > Options > Complements and disable the "Microsoft Teams Meeting Add-in for Microsoft Office." When you restart Outlook without that plugin, the blockages are avoided until the final update can be applied.

This episode is not isolated: in recent months Microsoft has had to correct several problems that affected classic Outlook. An error that generated 0x800CCC0F and 0x80070057 codes was resolved when synchronized Gmail and Yahoo accounts, and previously there was a conflict following the December 2025 updates that prevented the opening of encrypted messages. In addition, Microsoft continues to investigate another behavior that causes "Can't connect to the server" errors by creating groups in Classic Outlook when the Exchange Web Services (EWS) service is enabled for a tenant; the company published information about that case in your support site. More strange problems have also been reported, such as the mouse pointer shift in certain Microsoft 365 applications, which Microsoft has been recognizing and correcting with successive updates.

For IT administrators and professionals, the incident is a clear reminder of the importance of coordinating updates between interdependent components: supplements such as Teams are distributed with their own version cycles and can cause breakages if the main customer (in this case Outlook) was left in an earlier build. It is appropriate to plan phased deployments, test updates in a pilot group and have reversion or mitigation procedures (e.g., disable GPO supplements or through centralized configurations) to minimize impact on end users.

For most users the best practice is simple: keep up-to-date applications and, if the message appears to start safely or you experience closures, update Teams and Outlook and, if necessary, run the online repair. If the problems persist after the updates, document the reproducible steps and contact the Microsoft support by providing logs and catches will facilitate a faster resolution.

In short, although the ruling caused inconvenience and revealed the fragility of the units between products, Microsoft's response has been clear: to identify incompatibility, to publish recommendations and to deploy a correction. To avoid similar overlaps, the most prudent is to follow controlled update practices and keep communication channels open between IT users and equipment.