Azure Strategy: Evaluating the Case for Orbital Data Centers

You are a product manager on Microsoft Azure. Would it make sense for Azure to operate a data center in orbit? Give a recommendation and the reasoning that supports it. ```hint Start from the job, not the rocket Decide which customers and workloads would be better served by compute in orbit than by a ground region, and why, before judging feasibility and cost. ``` ### Clarifying Questions - Does "data center in space" mean general-purpose cloud capacity for customers on Earth, or compute for data that is already in orbit, such as satellite imagery? - Which goal matters most to Azure here: new revenue, power and capacity for growth, sustainability, or reach and resilience where ground regions are thin? - Should the recommendation cover the next few years or a decade-long bet? - Is building and operating spacecraft in-house in scope, or should I assume Azure works through launch and satellite partners? ### What a Strong Answer Covers - A precise definition of the proposal and the goal it would serve for Azure - Target customers and workloads, separating those that truly need orbit from those better served on the ground - Feasibility and unit economics against a ground region: launch, power, heat rejection, radiation, maintenance, bandwidth and latency - Build, partner or wait options, ending in a clear recommendation and the milestones that would change it - Risks: regulation and data sovereignty, debris and end-of-life disposal, reputation and opportunity cost ### Follow-up Questions - What would have to be true about launch prices and hardware lifetimes for orbital capacity to compete with a new ground region, and how would you track those signals? - A major cloud rival announces an orbital compute pilot. Does that change your recommendation? - How would you scope a first pilot so that it ends in a clear go or no-go decision?