What Happened

Microsoft Research published Aurora 1.5: Extending open foundation models for weather and Earth-system applications on July 9, 2026. On the same date, the organisation released a preprint titled Aurora 1.5: Fine-Tuning a Foundation Model for Medium-Range Ensemble Weather Prediction. The work is led by contributors from Microsoft Corporation, the Microsoft AI for Good Lab, Microsoft Research Accelerator, and the University of Cambridge.

The important update is that Aurora 1.5 is not merely a broad research highlight with undisclosed weather capabilities. The preprint describes a specific atmospheric forecasting objective: skillful medium-range ensemble weather prediction. In weather forecasting, an ensemble is a collection of forecasts that represents a range of plausible atmospheric evolutions. That differs materially from a single deterministic forecast, because users often need to assess forecast uncertainty as well as a central expected outcome.

Microsoft positions Aurora 1.5 as a fine-tuned variant of Aurora, its atmospheric foundation model. The underlying Aurora model was pretrained on diverse, heterogeneous atmospheric data. Aurora 1.5 then applies a three-stage fine-tuning process intended to improve medium-range ensemble prediction. This is a more concrete claim than simply calling the work an Earth-system foundation model: the paper specifies the target timeframe, the modelling approach, and a comparison with the European Centre for Medium-Range Weather Forecasts operational ensemble, commonly called ECMWF ENS.

The reported headline result is substantial but should be read precisely. According to the preprint, Aurora 1.5 ENS outperforms the ECMWF ENS operational ensemble on 88.9% of upper-air and single-level target variables in the medium range, defined in the paper as days 1–10. This is a result across the paper’s evaluation targets; it does not mean Aurora 1.5 wins every variable, every lead time, every region, or every possible weather-use case.

The Numbers That Matter

Several details remain outside the supplied verified material. The sources do not establish a commercial API, cloud service availability, pricing, supported deployment hardware, licensing terms, model-weight access terms, or a guaranteed operational service level. The blog title refers to extending open foundation models, but it does not, in the available context, define precisely which artefacts are open or under which licence. Those questions matter for adoption and should...