Azure Service Fabric 7.2 Release

Published Oct 21 2020 01:30 PM 6,378 Views

* 11/4 Update - The Linux runtime for Service Fabric 7.2 will not become available in this release. We will rollout the updated Linux runtime in the next Service Fabric 7.2 refresh update. We are sorry for any inconveniences this may have caused, if you have any additional questions or require support please reach out to us through our support channels.


Azure Service Fabric 7.2 is now available!

We're excited to announce that 7.2 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.


What is new in Service Fabric 7.2?

This release is loaded with key features and improvements. Some of the key features are highlighted below:


Key Announcements

In addition, this release contains other new features, bug fixes, and performance improvements. For the full list of changes, please refer to the release notes.


Breaking Changes

  • Service Fabric 7.2 and higher runtime drops support for .Net core Service Fabric apps running with .Net core 2.2 runtime. .Net core runtime 2.2 is out of support from Dec 2019. Service Fabric runtime will not install .Net core runtime 2.2 as part of its dependency. Customers should upgrade their .Net 2.2 runtime SF apps to the next .Net core LTS version 3.1.
  • .Net core runtime LTS 2.1 runtime will go out of support from Aug 21, 2021. Service Fabric releases after that date will drop support for Service Fabric apps running with .Net core 2.1 runtime. Service Fabric .Net SDK will take a dependency on .Net runtime 3.* features to support Service Fabric .Net core apps.  This has no impact on Service Fabric .Net Framework SDK.
  • We will be deprecating the latest tag for OneBox container images. The new scheme for containers will substitute the current naming scheme ‘latest’ to be replaced with an OS-targeted latest set to explicitly identify the base OS for latest SF releases:
  • The default action of deleting uploaded application package is changed. If the application package is registered successfully, the uploaded application package is deleted by default. Before this default action changes, the uploaded application package was deleted either by calling to Remove-ServiceFabricApplicationPackage or by using ApplicationPackageCleanupPolicy parameter explicitly with Register-ServiceFabricApplicationType
  • Service Fabric 7.2 will become the baseline release for future development of image validation. When the feature is activated in future version e.g., Service Fabric 7.3, the cluster is not desired to rolled back down to 7.1 or lower. The version 7.2 is the baseline to which the cluster can downgrade.
Senior Member

Were there issues with the rollout?  It's November 2nd and I still haven't seen the SDK updated in Web Platform Installer, and the update still hasn't been seen by my stand-alone clusters.  Normally I get the updates to the stand-alone clusters days before I see them for my Azure clusters.  The Azure clusters have been updated for at least a week.


The reason I'm being impatient is that we have an on-prem customer installation coming up and I would rather install the most up-to-date version to avoid having to turn around and immediately update them.


@cdonovan63 The standalone cluster updates were rolled out and should now be available. If you have auto-upgrades enabled on your standalone clusters they will poll at 22:00 local time for the new update. Please let me know if you are still having any issues receiving these updates. The SDK rollout has been slightly delayed and should be available within the coming days.  

Senior Member

@Peter Pogorski Thanks for the quick response.  The standalone cluster update showed up this morning.

Occasional Visitor

When are the SDK updates going to be available?

Occasional Visitor

When cluster is set on automatic upgrade mode The upgrade does not start even though there is a new version of the cluster. As it is said in documentation "You can set your cluster to receive automatic fabric upgrades as they are released by Microsoft" is it mean that upgrade will be done after end of support of current version ?

Version history
Last update:
‎Nov 04 2020 11:35 AM
Updated by: