Microsoft Azure Service Fabric 9.0 First Refresh Release
Azure Service Fabric 9.0 First Refresh is now available!
We are excited to announce that 9.0 First Refresh release of the Service Fabric runtime has started rolling out to the various Azure regions along with tooling and SDK updates. The updates for .NET SDK, Java SDK and Service Fabric runtimes will be available through Web Platform Installer, NuGet packages and Maven repositories in 7-10 days within all regions.
Packages and Versions
- Service Fabric Runtime
- Ubuntu 18 - 9.0.1035.1
- Windows - 9.0.1028.9590
- Service Fabric for Windows Server
- Service Fabric Standalone Installer Package - 9.0.1017.9590
- .NET SDK
- Windows .NET SDK - 6.0.1028
- Microsoft.ServiceFabric - 9.0.1028
- Reliable Services and Reliable Actors - 9.0.1028
- ASP.NET Core Service Fabric integration - 9.0.1028
- Java SDK
- Java for Linux SDK - 1.0.6
- Service Fabric PowerShell and CLI
- AzureRM PowerShell Module - 0.3.15
- SFCTL - 11.0.1
Future Retirement and Deprecation Path Callouts
Read more about these in the release notes linked below.
- Retired support for ASP.NET Core 1.0
- Deprecated support for .NET Core 2.x
- (Upcoming) Deprecation of support for .NET 5.0
- (Upcoming) Retirement of support for Ubuntu 16.04
- (Upcoming) Deprecation of support for BinaryFormatter based remoting exception serialization
- (Upcoming) Archival and removal of older version of Service Fabric packages from the Download Center
Current Breaking Changes
Also, see feature items for breaking change details.
- Guest Executable and Container Applications: Guest executable and container applications created or upgraded in Service Fabric clusters with runtime versions 7.1+ are incompatible with prior Service Fabric runtime versions (e.g. Service Fabric 7.0).
Following scenarios are impacted: - An application with guest executables or containers is created or upgraded in an Service Fabric 7.1+ cluster.
The cluster is then downgraded to a previous Service Fabric runtime version (e.g. Service Fabric 7.0).
The application fails to activate. - A cluster upgrade from pre-SF 7.1 version to Service Fabric 7.1+ version is in progress.
In parallel with the Service Fabric runtime upgrade, an application with guest executables or containers is created or upgraded.
The Service Fabric runtime upgrade starts rolling back (due to any reason) to the pre-SF 7.1 version.
The application fails to activate.
To avoid issues when upgrading from a pre-SF 7.1 runtime version to an Service Fabric 7.1+ runtime version, do not create or upgrade applications with guest executables or containers while the Service Fabric runtime upgrade is in progress. - The simplest mitigation, when possible, is to delete and recreate the application in Service Fabric 7.0.
- The other option is to upgrade the application in Service Fabric 7.0 (for example, with a version only change).
If the application is stuck in rollback, the rollback has to be first completed before the application can be upgraded again.
For more details, please read the release notes
Published on:
Learn moreRelated posts
What’s new with Azure Repos?
We thought it was a good time to check in and highlight some of the work happening in Azure Repos. In this post, we’ve covered several recent ...
Part 1: Building Your First Serverless HTTP API on Azure with Azure Functions & FastAPI
Introduction This post is Part 1 of the series Serverless Application Development with Azure Functions and Azure Cosmos DB, where we explore ...
Announcing GPT 5.2 Availability in Azure for U.S. Government Secret and Top Secret Clouds
Today, we are excited to announce that GPT-5.2, Azure OpenAI’s newest frontier reasoning model, is available in Microsoft Azure for U.S. Gover...
Sync data from Dynamics 365 Finance & Operations Azure SQL Database (Tier2) to local SQL Server (AxDB)
A new utility to synchronize data from D365FO cloud environments to local AxDB, featuring incremental sync and smart strategies.
Azure Cosmos DB Conf 2026 — Call for Proposals Is Now Open
Every production system has a story behind it. The scaling limit you didn’t expect. The data model that finally clicked. The tradeoff you had ...