Project: Azure Service Fabric (Orchestration & Management / Scheduling & Orchestration)
File: Service_Fabric_ReleaseNotes_65.pdf

 
 Microsoft Azure Service Fabric  6.5 Release Notes  
This release includes the bug fixes  and new features  described in this document.  This release includes runtime, SDKs , Service Fabric Tool and 
Windows Server Standalone deployments to run on -premises.  
The following packages and versions are part of this release  
Service Fabric Runtime  Ubuntu  6.5.435.1  
Windows  6.5.639.9590  
Service Fabric for Windows 
Server  Service Fabric Standalone Installer Package  6.5.639.9590  
.NET SDK  Windows .NET SDK  3.4.639  
Microsoft.ServiceFabric  6.5.639  
Reliable Services and Reliable Actors  3.4.639  
ASP.NET Core Service Fabric integration  3.4.639  
Java SDK  Java for Linux SDK  1.0.5  
Service Fabric PowerShell and 
CLI AzureRM PowerShell Module  0.3.15  
SFCTL  8.0.0  
Service Fabric Tooling  Visual Studio Tooling  2.4.11116.1  
Eclipse Tooling  2.0.7  
  
 Contents  
Microsoft Azure Service Fabric 6.5 Release Notes  ................................ ................................ ................................ ................................ .......................  1 
Breaking Announcements  ................................ ................................ ................................ ................................ ................................ ..............................  3 
What N ew in 6.5  ................................ ................................ ................................ ................................ ................................ ................................ ............  4 
New Features  ................................ ................................ ................................ ................................ ................................ ................................ .............  4 
Service Fabric Runtime  ................................ ................................ ................................ ................................ ................................ ................................ .. 5 
Service Fabric .NET SDK  ................................ ................................ ................................ ................................ ................................ ...............................  14 
Service Fabric PowerShell and CLI  ................................ ................................ ................................ ................................ ................................ ...............  15 
Repositories and Download Links  ................................ ................................ ................................ ................................ ................................ ...............  16 
Visual Studio 2015 Tool for Service Fabric – localized download links ................................ ................................ ................................ .................  19 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
 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 . 
• Protecting system entities from runaway 'user' code : From this version, users  can now set up resource protection 
between the system and user services on a node. Service Fabric will enforce  these hard resource limits for  user services to 
guarantee that all the non -system services on a node will never use more than the specified amount of resources.   Please 
refer to this section  for configuration details .   
 What New in 6.5  
This release includes supportability, reliability, performance improvements, new features, bug fixes and enhancements to ease  cluster 
and application life cy cle management.  
 New Features  
• Service Fabric Explorer will now allow you to explore the applications that you have uploaded to image store.  
• Patch Orchestration Application(POA)  customers are recommended to move to released version 1.4.0  that has a lot of self -
diagnostic improvements.  
• EventStore Service will be enabled by default f or clusters  from this release unless a customer has specifically opted out.  
• Add replica level service fabric heal th events for Stateful Services  
• Users will have better visibility into state of down seed nodes.  
• Service Fabric Application Disaster Recovery tool  allows users of Service Fabric stateful services to get back live soon in case 
the primary SF cluster encounters a disaster. The tool  constantly synchronizes the data from the application running on the 
primary cluster on the standby application on secondary using periodic backup and restore.  
• Support for .NET Core applications built from Visual Studio to be published to Linux Service Fabric cluster . 
• Azure Service Fabric CLI (sfctl)  will be installed automatically from 6.5 onwards when you upgrade or create new Azure 
Service Fabric Linux cluster . 
• SFCTL  is installed by default on MacOS/Linux OneBox cluster .  
 Service Fabric Runtime   
   
Versions  IssueType  Description  Resolution  
Ubuntu  6.5 
Windows 
6.5 
    
 Feature   Improve reliable collection replicator 
retry logic  
 
 Brief desc:  When there is network congestion or if secondary is slow in receiving messages, 
replicator would still try to flood the secondary with retries . This can exacerbate the problem . 
This feature improves the replicator retry mechanism.  
How/When to Consume it:  Feature is enabled by default  
Windows  
6.5 Bug  FabricInstallerSvc no longer writes a 
dump when timing out as part of it 
retry loop starting FabricHost.  Impact :  Excess noise for cluster health telemetry and unnecessary network usage when Fabric is 
not coming up.  
Fix:  Change logic to do silent retry . 
Ubuntu  6.5 
Windows  
6.5 Bug Made performance improvements for 
scalemin (onebox/more nodes than 
machines) scenario cluster setup and 
reset, by avoiding unnecessary file 
copies.  Impact :  SDK single machine or scalemin clusters previously had their own set of copies for 
Fabric service files  for legacy reasons , resulting in  slow cluster setup.  
Fix:  This was reworked to deprecate the need for each node to have its own set of copies of 
service files.   
GitHub link: https://github.com/Microsoft/service -fabric/issues/299  
Ubuntu  6.5 
Windows  
6.5 Bug In container  setup code for Service 
Fabric runtime deployment, have 
removed waits and retries where they 
are not necessary.  Impact :  Container configuration setup is behaving slowly  for Service Fabric node setup  & SDK 
upgrad e. 
Fix:  Improve granularity checking result codes for certain functional calls, to remove  
unnecessary waits.  
Windows  
6.5 Feature  SDK Service Fabric runtime installer 
now takes  /force fla g to automatically 
close conflicting processes.  Brief desc: For advanced users installing the SF runtime  for the SDK setup scenario  using the 
command line, can now pass /force flag to automatically close conflicting processes during the 
upgrade.  Note: This does not apply for Windows system services.  
In addition,  when not using the /force or /quiet flags, a modal dialog is presented to offer this 
functionality on demand , such as when installing through WebPI . 
How/When to Consume it:  Using the  runtime installer exe retrieved from WebPI/direct link , 
provide the new parameter through command line interface.  
Windows  
6.5 Feature  SDK Service Fabric runtime installer 
now takes /uninstall parameter  for 
easy command -line uninstallation.  Brief desc: To bring parity with functionality available in the previously deprecated MSI 
installer, the SF runtime installer exe now takes an /uninstall parameter.  
How/When to Consume it:  Using the runtime installer exe retrieved from WebPI/direct link, 
provide the new parameter through command line interface.  
Windows  
6.5 Bug Fixed crash during node state 
removal . Impact :  In the cluster node removal path, i n rare case s, calling NetCloseResource would hit a 
crash which had a risk of leaving artifacts behind during uninstall.  
Fix:  Fixed marshaling casting issue that led to Arithmeth ic OverflowException.   
 Ubuntu  6.5 
Windows 
6.5 
 Feature  Change compose application 
deployment to use the same workflow 
and store data structures with mesh 
application deployment in Cluster 
Manager.  How/When to Consume it:  
When cluster upgrade to version 6.5, compose deployments old data structures will be removed 
and new data structures will be generated. Only completed compose deployments are migrated.  
To migrate successfully, cluster upgrade ( from last 6.4 refresh release to 6.5 and 6.5 to lower 
version) and operations on compose based applications (create/upgrade/delete) are mutually 
blocking to each other. Fabric upgrade to 6.5 will fail if there is an operation on compose 
application not completed, and vice versa. To hav e this blocking logic, users of compose 
deployments must upgrade to 6.4 CU7 first and then upgrade to 6.5. Cluster upgrade that not 
across 6.5 will not be affected.  
 
The migration of compose applications is one way. If cluster is in 6.5 and then upgraded to a 
lower cluster version such as 6.4, migrated and newly created compose applications are still 
running but cannot be operated in lower cluster version.  It is only changed internally. There are 
no visible public API changes. This change does no t impact mesh application deployment.  
Ubuntu  6.5 
Windows 
6.5 
 Bug Accept new application upgrade if a 
previous application rollback fails during 
updating default services  Impact :  If an application rollback fails when updating default services, a new application 
upgrade on the same application will fail.  
Fix:  Fix to accept a new application upgrade if previous application rollback fails during 
updating default services.  
Ubuntu 6.5  Bug Service Fabric clusters on Azure can now 
be deployed using custom DNS.  Impact: Customers detailing a custom DNS server in their networking dhcpOptions would have a 
cluster fail to come up since Azure machine addresses cannot be resolved  with the DNS server.  
The workaround was to add all cluster node address entries to the machine hosts files, to act as a 
stop gap.  
How/When to Consume it:  To activate custom DNS through an ARM Azure Service Fabric  
deployment, this configuration is required under ARM Microsoft.Network/virtualNetworks 
properties section (/w your chosen dns ip):  
        "dhcpOptions": {  
          "dnsServers": [  
            "8.8.8.8"  
          ] 
        } 
Ubuntu  6.5 Feature  General machine bootstrap script has 
been provided to set up prerequisites for 
Service Fabric Linux nodes for 
deployment & upgrade scenarios  Brief desc: A common machine prerequisite setup script bootstrap.sh  has been made available, in 
sync for each relea se of the SF runtime deb package. This allows for a consistent and future -proof 
prerequisite setup and upgrade process for Azure and on -premises Service Fabric Linux nodes.  
It sets up:  
1. Base environmental packages  
2. External dependency package repositories  
3. Service Fabric CLI (sfctl)  
How/When to Consume it: Azure -deployed Service Fabric machines carry a script in the VM 
extension which is used to invoke the boo tstrap script by deriving it from the deb package. The  
 helper script is called run_b ootstrap.sh and the extension package can be retrieved from link:  
https://go.microsoft.com/fwlink/?linkid=2092882  
Ubuntu  6.5 
(& MacOS)  Feature  SFCTL is installed by default on 
MacOS /Linux  dev experience cluster  
container  Brief desc:  When creating a container using the latest Service Fabric base container 
microsoft/service -fabric -onebox , the setup script will bootstrap the machine with sfctl installed 
automatically, removing the need to run separate steps to install the CLI.  
How/When to Consume it:  MacOS /Linux  dev container setup  for container -based local cluster : 
https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -get-started -mac 
Windows 
6.5  Feature  EventStore  Service will be added by 
default to  Windows clusters  when 
runtime gets upgraded to a version >= 
6.5. Brief desc:  When clusters get created or upgraded with versions >=6.5, the EventStore  Service is 
enabled by default. If a customer wants to disable it, this can be achieved by setting the 
eventStoreServiceEnabled property on the cluster resource to false (API version for cluster 
resource should be updated to 2019 -03-01). 
https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -diagnostics -eventstore  
Windows 
6.5 Feature  Validation should not allow users to 
specify CPU shares without specifying 
number of required cores  Brief desc:  With new validation during application manifest registration, Service Fabric  does not 
allow specifying CPU shares at a code package/container level without setting the number of 
cores that is required.  Reasoning behind this is that shares are used to split CPU time between 
different code packages/containers on the same machine.  
If customer already has an application where CPU shares are specified on code package level, but 
no CPU cores on service package level, this application will work  with new fabric version. 
Customers must  change the application manifest and add CPU cores on service package level to 
successfully upgrade their apps with newer service fabric versions . 
Windows 
6.5 Feature  Add replica -level Service Fabric Events 
to be used with Reliable Collections.  Brief desc: Added replica -level Service Fabric Events for Reliable Collections . 
How/When to Consume it: Explained in the first paragraph  in: https://docs.microsoft.com/en -
us/azure/service -fabric/service -fabric -diagnostics -event -generation -operational  
Documentation: https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -
diagnostics -event -generation -operational #replica -events  
Windows 
6.5 
Ubuntu 6.5  Bug Improve error reporting when a code 
package terminates unexpectedly.  Service Fabric would provide a health message that included only an error code when a Code 
Package terminated. It was difficult for users to know why their process/container terminated and 
take action to fix it. Service Fabric will now display a more descr iptive health message with 
general debugging tips when a Code Package terminates. It will also include a link to more 
specific debugging information for common termination error codes.  
Windows 
6.5 
Ubuntu 6.5  Bug Move sf_cns plugin to a different port.  
 The sf_cns plugin runs on port 10090 (cns) and 48080 (cnm) by default. Teams are also using the 
azure cns plugin from GitHub that also runs on 10090 and 48080. Providing configuration -based  
support to run the sf_cns plugin on a different ports. The configuration controlling the sf_cns 
plugin ports are Hosting/SfCnsNetworkPluginCnsUrlPort (default is 10091) and 
Hosting/SfCnsNetworkPluginCnmUrlPort(default is 48081).   
 Windows 
6.5 
Ubuntu 6.5  
 Bug Fixed Reverse Proxy crash  of malformed 
URLs  requests  Prior to 6.3 Reverse sf event  would return 400 BadRequest, recently Reverse Proxy will crash if it 
receives a malformed request. This behavior was fixed such that it will again return 400 even if 
the URL is malformed.   
Windows 
6.5 
 Feature  Provide option to send telemetry on API 
usage through HTTP Gateway  Brief desc: API calls going through the HTTP endpoint can be collected as part of telemetry. 
Information may contain request URL, whether the operation was successful, error message, and 
the type of client the request came from, such as sfctl.  
How/When to Consume it:  Feature is disabled by default. Feature can be turned on in the 
Diagnostics sections of FabricSettings, with configurations CaptureTelemetry and 
TelemetryCapturePercentage.  
Windows 
6.5 
Ubuntu 6.5  Bug DeletionManager should delete 
checksums first and fail if not able  Brief Desc:   DeletionManager deletes part of a code package and errors out before it's able to 
finish (the deletion can fail on the OS side if it can't delete on of the files in the folder) . The 
checksum remains along with part of the code package. If that ApplicationType is re -provisioned, 
then DownloadManager will see the checksum and that the folder is still there and not overwrite 
it. SF will now try to bring up an application with a hal f-missing code package.  
Fix:  Fixed an issue where deleting files from a node would leave the cache in an error state  
Windows 
6.5 
Ubuntu 6.5  Bug Users can now specify a 
"TreatContainerUnhealthyStatusAsError" 
flag in the HealthConfig object of their 
ContainerHostPolicies.  Users can now specify a "TreatContainerUnhealthyStatusAsError" flag in the HealthConfig object 
of their ContainerHostPolicies. W hen set to true, any unhealthy statuses reported from a 
container's configured HEALTHCHECK will be treated as an error in Service Fabric's health 
reports.  
Windows 
6.5Ubuntu 
6.5 Bug Fixed an issue causing externally 
terminated containers to be cleaned 
regardless of an AutoRemove policy.  Brief desc:   
If a container crashed or was terminated externally, we shouldn't remove the container. Whether 
the container is removed should be set during activation.  
 
Windows 
6.5Ubuntu 
6.5 Bug ImageCache should clean up numbered 
temporary files on failed download  Brief Desc:  Customer is reporting they're seeing a buildup  of temporary download files in 
ImageCache. These files are created while being downloaded with a temporary name, and then 
renamed after download is complete. The files the customer is seei ng are slightly smaller than 
their code package, leading me to believe they are an artifact left due to a failed download.  
Fix: Fixed an issue where temporary files were being left in the ImageCache after a failed 
download.  
 
Windows 
6.5  
Ubuntu 6.5  Feature  Auditing f unctionality added t o REST 
api's Brief desc : Information about the http requests ( REST api’s) will be logged to a well-known  
ETW channel under the SF Operational channel with keyword audit. This audit is configurable to 
turn on or off, only actions from users with admin credentials will be logged, and requests failed 
due to authentication will be ignored. The audit will include  the credentials being presented, along 
with the request url and body.  
  
 How/When to Consume it:  Feature is disabled by default. Feature can be turned on in the 
Diagnostics sections of FabricSettings, by setting the configuration AuditHttpRequests to true.  
 
Remoting 
SDK 6.5  Bug Default Retry settings updated  Brief desc:  
We have changed the default retry settings for FabricTransientExceptions for Remoting from max 
to 10. Users will see FabricTransientExceptions and hence they need to handle those from this 
release onwards.  
Windows 
6.5 
Ubuntu 6.5  Feature  New REST API  to support querying 
image store folder size.  Brief desc:  
Service Fabric REST API support to return folder size in ImageStore. This REST API help SF 
explorer show folder information in ImageStore viewer tab. A user can see which folder consume 
large amount of space in storage and cleans up accordingly.  
/ImageStore/{contentPath}/$/FolderSize  
Documentation : https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -
visualizing -your-cluster#image store -viewer  
Windows 
6.5 
Ubuntu 6.5  
 Bug Resource governance validation should 
not allow users to specify CPU shares on 
code package level without specifying 
the number of required cores on service 
package level  Brief desc:  
With new validation during application manifest registration, Service Fabric does not allow 
specifying CPU shares a t a code package/container level without setting the number of cores that 
is required. Reasoning behind this is that shares are used to split CPU time between different code 
packages/containers on the same machine.  
If customer already has an application where CPU shares are specified on code package level, but 
no CPU cores on service package level, this application will work with new fabric version. 
Customers must change the application manifest and add CPU cores on service package level to 
successfully upgrade their apps with newer service fabric versions.  
Windows 
6.5 Feature  SF trace logs format changed to be CSV 
compliant  SF trace logs are made CSV compliant by enclosing message by double quotations after escaping 
(escape character: ") existing double quotations in the message. Custom tools developed by users 
that have a dependency on these logs need to modify the tools accordingly.  
 Example :  
Previous trace in log file:  
2019 -5-15 01:47:48.091,Warning,1896,1756,Transport.FailedToConnect@68b5725aa0,client -
10.0.0.11:19000/10.0.0.11:19000: error = 2147943625, failureCount=9. Filter by 
(type~Transport.St && ~"(?i)10.0.0.11:19000") to get listener lifecycle. Connect failure is 
expected i f listener was never started, or listener/its process was stopped before/during 
connecting.  
Current : 
2019 -5-15 01:47:48.091,Warning,1896,1756,Transport.FailedToConnect@68b5725aa0,"client -
10.0.0.11:19000/10.0.0.11:19000: error = 2147943625, failureCount=9. Filter by 
(type~Transport.St && ~""(?i)10.0.0.11:19000"") to get listener lifecycle. Connect failure is  
 expected if listener was never started, or listener/its process was stopped before/during 
connecting.  
Windows 
6.5 
Ubuntu 6.5  
 Feature  Protecting system entities from 
runaway 'user' code  Few customers encountered problems due to runaway user services consuming all the resources 
on Service Fabric nodes. The resource exhaustion (spinning CPU, memory exhaustion, 
hammering disk IO, disk space  exhaustion) resulted in several bad effects including starving other 
services on the nodes, nodes ending up in a bad state, complex mitigation and recovery steps, and 
unresponsive cluster management APIs.  
 
With this version of Service Fabric, you can now  set up resource protection between the system 
and user services on a node. Service Fabric will enforce  these hard resource limits 
for user services to guarantee that all the non -system services on a node will never use more than 
the specified amount of re sources.   
 
This release adds an additional configuration option: EnforceUserServiceMetricCapacities.  This 
config is in  the PlacementAndLoadBalancing  section of your  ClusterManifest/ClusterConfig, and 
is OFF by default (to prevent unexpected surprises for e xisting customers during upgrades).  
 
<Section  Name ="PlacementAndLoadBalancing" >    
<Parameter  Name ="EnforceUserServiceMetricCapacities"  Value ="true"  />   
</Section>   
 
{ 
"name" : "PlacementAndLoadBalancing" , 
 "parameters" : [ {  
"name" : "EnforceUserServiceMetricCapacities" ,  
"value" : "true"  } ]  
} 
 
This feature depends on Node Capacities for the Service Fabric resource governed 
https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -resource -governance  metrics 
(as of this writing Memory and CPU Cores) being set. These capacities can be set either 
automatically ( AutoDetectAvailableResources  flag is false) or manually. If no capacities are set, 
the node is considered to have infinite capacity for the given metric, and hence this feature cannot 
be used (since  SF doesn't know how much resources to reserve  for system services). 
SF will issue  a health warning if "EnforceUserServiceMetricCapacities"  is true  but capacities are  
 not specified.   
 
The specified metric capacity for the node is then divided between the user serv ices defines and 
the rest of the system. The amount dedicated to the user services vs. the amount dedicated to the 
system is controlled by the following settings:  
<Section  Name ="PlacementAndLoadBalancing" >    
<!-- 0.0 means 0%, and 1.0 means 100% -->   
<Parameter  Name ="CpuPercentageNodeCapacity"  Value ="0.8"  />   
<Parameter  Name ="MemoryPercentageNodeCapacity"  Value ="0.8"  />  
</Section>   
 
These ratios are defined by default. By default 80% of node capacity is used for user 
services  and 20% will be left to allow enough resources for the SF system 
services  (and also for any other processes/apps running on the node that are not visible to SF). 
These settings  are static and upgrades to change them will require node restarts.  User service 
capacity is  enforced  only for governed SF  metrics (Memory and CPU Cores as of this writing). 
For non -governed metrics, it's treated as a soft guarantee (violations are possible, but if they 
happen, load balancer will trigger and attempt to fix the violation by moving services  around, just 
like normal capacity violations).  The SF system services are  effectively  ungoverned , and they 
can go beyond of their quota. Effectively constraining the system components and preventing 
them from growing beyond their allotment will be  handled in an upcoming release.  
 
 
With this change, user services metric  capacity  can also be defined per Node Type. T At the 
NodeType level, a new section is added named UserServicesMetricCapacity.  Within this section, 
the same setting names and behavior can be defined and will result in the same behavior as 
described for the Cluster Manifest level settings. If metric capacity is defined in both places, node 
type definition takes precedence.  
<NodeTypes>   
<NodeType  Name ="NodeType0">   
<UserServicesMetricCapacity>    
<Parameter  Name ="CpuPercen tageNodeCapacity"  Value ="0.5"/>    
<Parameter  Name ="MemoryPercentageNodeCapacity"  Value ="0.7"/>    
 </UserServicesMetricCapacity>   
</NodeType>   
</NodeTypes>   
 
This release also fixes an issue in the calculation of node capacities. The rule for calculating 
capacity has changed to account for percentage value ( User  Services  Capacity = 
Node  Capacity  * User  Services  Capacity  Percentage ) 
 
Previously, if user provided an override  value  for node capacity in  NodeType,  the %  value  was 
ignored.  This could be surprising to some users.  
 Scenario 1  Scenario 2  Scenario 3  Scenario 4  
Node 
capacity 
auto-
detected 
value  100 100 100 100 
Node 
capacity 
user 
override  - 90 - 90 
User 
services 
capacity 
default in 
cluster 
manifest  0.7 0.7 0.7 0.7 
User 
services 
capacity 
default in 
Node Type  - - 0.5 0.5 
User 
services 
capacity - 
actual value  70 90 50 90 
  
  
 
  With this release, if user provides an override for the absolute capacity in  NodeType, the % value 
is NOT  ignored, and will further discount the available resources on the node.  
 
 Scenario 1  Scenario 2  Scenario 3  Scenario 4  
Node 
capacity 
auto-
detected 
value  
 100 100 100 100 
Node 
capacity 
user 
override  
 - 90 - 90 
User 
services 
capacity 
default in 
cluster 
manifest  
 0.7 0.7 0.7 0.7 
User 
services 
capacity 
default in 
Node Type  
 - - 0.5 0.5 
User 
services 
capacity - 
actual value  
 70 63 50 45 
  
 Service Fabric .NET SDK 
 
 
 
  Reliable Services and Reliable Actors X.Y.Z  
 Feature   Added replica -
level Service 
Fabric Events to 
be used with 
Reliable 
Collections and 
KeyValueStore.  
 
 Brief desc: Added replica -level Service Fabric Events for stateful services.  
How/When to Consume it: Explained in the first paragra ph in: 
https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -
diagnostics -event -generation -operational  
Documentation:  
https://docs.microsoft.com/azure/service -fabric/service -fabric -
diagnostics -event -generation -operational#replica -events  
   
 Service Fabric PowerShell and CLI  
  
  Versions  IssueType  Description  Resolution  
SFCTL     8 
 Feature   As of Service Fabric on 
Linux 6.5  in Azure, sfctl is 
installed on machines by 
default.  
 
 Brief desc: Latest  version SFCTL is installed o n Service Fabric  on Linux 
machines when creating a new cluster or  upgrading a cluster to 6.5.  
How/When to Consume it: Automatic.  
https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -cli 
  
 Repositories and Download Links  
The table below is an overview of the direct links to the packages associated with this release.  
Follow  this guidance for setting up your developer environment:  
• Linux: https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -get-started -linux  
• Mac: https://do cs.microsoft.com/en -us/azure/service -fabric/service -fabric -get-started -mac 
• Windows: https://docs.microsoft.com/en -us/azure/service -fabric/service -fabric -get-started  
Area  Package  Version  Repository  Direct Download Link  
Service 
Fabric 
Runtime  Ubuntu Developer Set -up 6.5.435 .1 N/A Cluster Runtime:  
https://apt -
mo.trafficmanager.net/repos/servicefab
ric/pool/main/s/servicefabric  
Service Fabric SDK for local cluster 
setup:  
https://apt -
mo.trafficmanager.net/repos/servicef
abric/pool/main/s/servicefabricsdkco
mmon/  
Container image:  
https://hub.docker.com/r/microsoft/ser
vice-fabric -onebox/  
Service 
Fabric 
Runtime  Windows Developer Set -up 6.5.639.9590  N/A https://download.microsoft.com/downl
oad/C/7/B/C7B7BA41 -B95A -4363 -
8B28 -
7075E9B10E99/MicrosoftServiceFabri
c.6.5.639.95 90.exe   
Service 
Fabric for 
Windows 
Server  Service Fabric Standalone 
Installer Package  6.5.639.9590  
 N/A https://download.microsoft.com/downl
oad/8/3/6/836E3E99 -A300 -4714 -
8278 -
96BC3E8B5528/6.5.639.9590/Microso
ft.Azure.ServiceFabric.WindowsServe
r.6.5.639.9590.zip    
 Area  Package  Version  Repository  Direct Download Link  
Service 
Fabric for 
Windows 
Server  Service Fabric Standalone 
Runtime  6.5.639.9590  N/A https://download.microsoft.com/downl
oad/B/0/B/B0BCCAC5 -65AA -4BE3 -
AB13 -
D5FF5890F4B5/6.5.639.9590/Microso
ftAzureServiceFabric.6.5.639.9590.cab    
.NET SDK  Windows .NET SDK  3.4.639  N/A https://download.microsoft.com/downl
oad/C/7/B/C7B7BA41 -B95A -4363 -
8B28 -
7075E9B10E99/MicrosoftServiceFabri
cSDK.3.4.639.msi   
.NET SDK  Microsoft.ServiceFabric  6.5.639  N/A https://www.nuget.org  
.NET SDK  Reliable Services and 
Reliable Actors  
• Microsoft.ServiceFa
bric. Services  
• Microsoft.ServiceFa
bric.Services.Remoti
ng 
• Microsoft.ServiceFa
bric.Services.Wcf  
• Microsoft.ServiceFa
bric.Actors  
• Microsoft.ServiceFa
bric.Actors.Wcf  3.4.639  https://github.com/Azure/service -
fabric -services -and-actors -dotnet  https://www.nuget.org  
.NET SDK  ASP.NET Core Service 
Fabric integration  
• Microsoft.ServiceFa
bric.Services.AspNe
tCore.*  3.4.639  https://github.com/Azure/service -
fabric -aspnetcore  https://www.nuget.org   
 Area  Package  Version  Repository  Direct Download Link  
.NET SDK  Data, Diagnostics and Fabric 
transport  
• Microsoft.ServiceFa
bric.Data  
• Microsoft.ServiceFa
bric.Data.Interfaces  
• Microsoft.ServiceFa
bric.Diagnostics.Inte
rnal 
Microsoft.ServiceFabric.Fab
ricTransport.Internal  3.4.639  N/A https://www.nuget.org  
.NET SDK  Microsoft.ServiceFabric.Dat
a.Extensions  1.4.639 N/A https://www.nuget.org  
 
Java SDK  Java SDK  1.0.5 N/A https://mvnr epository.com/artifact/com
.microsoft.servicefabric/sf -actors/1.0.5  
Visual 
Studio  Visual Studio 2017 Tools for 
Service Fabric  2.4.11024.1  N/A Included in Visual Studio 2017 Update 
7 (15.7) and above  
 Visual Studio 2015 Tools for 
Service Fabric  2.4.11116.1  N/A See localized download links below  
Eclipse  Service Fabric plug -in for 
Eclipse  2.0.7  N/A N/A 
Yeoman  Azure Service Fabric Java 
generator  1.0.7  https://github.com/Azure/generator
-azuresfjava  N/A  
Yeoman  Azure Service Fabric C# 
generator  1.0.9  https://github.com/Azure/generator
-azuresfcsharp  N/A  
Yeoman  Azure Service Fabric guest 
executables generator  1.0.1  https://github.com/Azure/generator
-azuresfguest  N/A  
Yeoman  Azure Service Fabric 
Container generators  1.0.1  https://github.com/Azure/generator
-azuresfcontainer  N/A  
CLI Service Fabric CLI  8.0.0 https://github.com/Azure/service -
fabric -cli  https://pypi.python.org/pypi/sfctl   
PowerShell  AzureRM.ServiceFabric  0.3.15 https://github.com/Azure/azure -
powershell/tree/preview/src/Resou
rceManager/ServiceFabric  https://www.powershellgallery.com/pa
ckages/AzureRM.ServiceFabric/0.3.15    
  
Visual Studio 2015 Tool for Service Fabric – localized download links  
NOTE:  The below download links are for the 2.4.11116.1  release of Visual Studio 2015 Tools for Service Fabric.  
 
https://download.microsoft.com/download/C/7/B/C 7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFabricTools.VS140.de -de.msi  
https://download.mic rosoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFabricTools.VS140.en -us.msi  
https://download.microsoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFabricTools.VS140.es -es.msi  
https://download.microsoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFabricTools.VS140.fr -fr.msi  
https://download.microsoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFabricTools.VS140.it -it.msi  
https://download.microsoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFabricTools.VS140.ja -jp.msi  
https://download.microsoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFabricTools.VS140.ko -kr.msi  
https://download.microsoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFabricTools.VS140.ru -ru.msi  
https://download.microsoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E99/MicrosoftAzureServiceFab ricTools.VS140.zh -cn.msi  
https://download.microsoft.com/download/C/7/B/C7B7BA41 -B95A -4363 -8B28 -7075E9B10E 99/MicrosoftAzureServiceFabricTools.VS140.zh -tw.msi