Azure Service Fabric 6.5 release

6/18 Update: The roll out of this release is on pause as some issues were discovered. We'll update this thread once the refresh starts rolling out with the updated version numbers with the download links. Thanks for your patience. 

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

Breaking announcements

  • This is the last release where we are releasing the Visual Studio tools for Service Fabric for VS 2015. Customers are advised to move to VS 2019.

What's new in Service Fabric 6.5?

In addition, the release contains many new features, bug fixes, supportability, reliability and performance improvements. For the full list of all the changes, refer to the release notes.

Comments (6)
  1. Windows 2019 node support?

    1. Neticated says:

      I’d also like to know when do you plan to support Server 2019?
      As far as I can tell, documentation still only lists: Windows Server OS installed (valid versions: 2012 R2, 2016, 1709, or 1803)
      Is that correct??

      1. The documentation has been updated recently. From SF Blog:

        “We now support Windows Server 2019 and Windows Server 1809 for Azure and Standalone Service Fabric Clusters starting from 6.4.654.9590. “

  2. jackhanbond says:

    VS 2019 support for mesh?

  3. This release breaks DNS resolution in Docker.. None of my java services running in SF nodes can resolve SQL, Service Bus or Cosmos DB.. Name resolution failure. This is a Linux Cluster.

    Reverting to v6.4.661.1 resolved the problem.

  4. Neticated says:

    The 6.5 upgrade is pretty cool, thanks SF team!
    In particular, for an on-premise gmsa cluster:
    a) deleting invalid nodes is no longer a hacky/confusing experience
    b) SF and SF Explorer is much better at showing correct Node up/down/error status and showing most recent/relevant events

Comments are closed.

Skip to main content