NASA's Artemis II crew, currently orbiting Earth in a historic mission, called Houston for tech support after Microsoft Outlook failed on their Surface Pro tablet.
Some problems follow us everywhere, even 240 miles above the planet. Commander Reid Wiseman, leading the four-person Artemis II crew aboard NASA's Orion spacecraft, radioed mission control early Thursday morning with a request that will sound familiar to anyone who has ever worked in an office. He needed help fixing Microsoft Outlook.
The glitch appeared on Wiseman's personal computing device, a Microsoft Surface Pro tablet that astronauts use for communication, scheduling, and mission data. The device lost internet connectivity, and troubleshooting revealed a deeper software conflict involving a system called Optimus, the onboard software managing tablet operations. Wiseman had already tried the universal fix of turning the device off and on again. It did not work.
"I also see that I have two Microsoft Outlooks and neither one of those are working," Wiseman told mission control, according to a clip of the exchange shared on Bluesky by space journalist Niki Grayson. He granted NASA permission to remote into the tablet and investigate.
The incident highlights a reality that often gets lost in the grandeur of space exploration: astronauts rely on the same commercial software and hardware that the rest of us do, and it breaks just as often. NASA has increasingly turned to off-the-shelf consumer technology for crewed missions, a shift designed to reduce costs and speed up development cycles. The agency's long-standing partnership with Microsoft, which supplies Surface devices and Azure cloud services to the International Space Station and now Artemis missions, is a cornerstone of that strategy.
But consumer-grade software running in extreme environments introduces unpredictable friction. Orion's cabin is pressurized and climate-controlled, yet the computing environment is anything but standard. Connectivity between the spacecraft and ground stations depends on the Tracking and Data Relay Satellite system, and intermittent links can cause sync failures, duplicate application instances, and corrupted caches. What looks like a simple Outlook glitch on the surface is likely a symptom of that fragile data pipeline.
As Engadget originally reported, NASA's live feed did not capture a resolution to the Outlook problem during the broadcast. The crew moved on to other tasks, and presumably the tech support work continued while the astronauts slept.
The Outlook incident was not even the most pressing hardware issue the crew faced during the mission. Astronauts also reported a malfunction in the fan system inside Orion's toilet, which handles urine collection. That failure carried more immediate practical consequences. NASA confirmed the issue was resolved within a few hours using contingency urinal bags as a backup. Still, the fact that a bathroom fan and an email client competed for the same level of urgent attention from mission control tells you something about the texture of long-duration spaceflight.
The Artemis II mission itself is a milestone. It is the first crewed flight of NASA's Space Launch System rocket and the Orion capsule, designed to carry astronauts around the Moon and back as a precursor to future lunar landings. The crew of four, Wiseman, Victor Glover, Christina Koch, and Jeremy Hansen, represents the first time NASA has sent a group this diverse beyond low Earth orbit. The mission duration of roughly ten days is short compared to ISS stays, but every hour is densely packed with system checks, trajectory adjustments, and equipment tests.
What This Means for Enterprise Tech in Space
For the companies building the software and hardware that ends up in orbit, incidents like this are a reminder that reliability demands a different standard in space. Microsoft has invested heavily in positioning Azure as a platform for edge computing in remote and disconnected environments, including partnerships with NASA to test cloud processing aboard the ISS. But the Artemis II Outlook glitch illustrates the gap that still exists between enterprise-grade uptime and the realities of computing through a satellite link in a moving spacecraft.
Expect NASA and its commercial partners to tighten software validation processes as Artemis missions grow longer and more complex. The next mission, Artemis III, aims to land humans on the lunar surface for the first time since Apollo 17 in 1972. Astronauts spending weeks on the Moon will need communication tools that work without constant hand-holding from Houston. The commercial tech industry, meanwhile, will keep watching. Every glitch that makes headlines is also a data point for competitors eyeing the growing market for space-rated computing infrastructure. The company that can deliver truly resilient software for extreme environments will not just win NASA contracts. It will own a category that barely existed a decade ago.
