During such moments, it is inevitable to question whether Microsoft truly cares about its reputation or if, in today’s times, large tech companies are solely guided by profits and their stock value. Historically significant companies associated with figures like Bill Gates and Steve Ballmer seem increasingly faced with that dilemma.
It is hard not to think of the contrast: that a widely used commercial software should fail in such a critical environment as a space mission. The case of Microsoft Outlook during the Artemis program not only draws attention but also raises uncomfortable questions.
It was not an isolated failure. Both email systems available for the crew encountered problems simultaneously, forcing them to seek technical support from Earth.
While it is understandable that daily-use tools may fail, it becomes less so in environments where redundancy is key. Such incidents highlight the risks of relying on closed software in systems where transparency and auditability could make a difference.
This reopens a debate that never fully closes: the role of open source in critical environments. Should such systems rely more on open, auditable, and controllable solutions?
It is not about idealizing open source—which has also suffered vulnerabilities, even exploited by state actors—but recognizing its structural advantages in terms of transparency and control.
Microsoft Outlook’s failure did not occur at any random moment but during tests related to Artemis II, where realistic mission conditions are simulated.
According to reports, the issue manifested itself during operations where the crew needed to use the email system for non-critical internal communications. The most striking aspect is that the error affected both instances of Outlook available on board simultaneously, forcing intervention from Earth to restore service.
This detail reinforces the hypothesis of a shared failure—whether due to configuration, synchronization, or common dependency—and questions the effectiveness of implemented redundancy.
Meanwhile, the industry context does not help in building trust. Recent movements at major tech companies, such as mass layoffs at Oracle and other firms, along with the growing replacement of developers by AI-based solutions, raise a legitimate question: is software quality being compromised for speed and cost reduction?
There are no simple answers. But there is one certainty: when systems fail even in space, it is time to reconsider what kind of technology we are building and who we decide to trust.