Merge pull request #176330 from anantshankar17/master

Updates

Author: PRMerger12

articles/service-fabric/how-to-patch-cluster-nodes-windows.md

@@ -2,7 +2,7 @@
 title: Patch the Windows operating system in your Service Fabric cluster 
 description: Here's how to enable automatic OS image upgrades to patch Service Fabric cluster nodes running on Windows.
 ms.topic: how-to
-ms.date: 03/09/2021
+ms.date: 10/19/2021
 ---
 
 # Patch the Windows operating system in your Service Fabric cluster
@@ -14,7 +14,8 @@ Getting [automatic OS image upgrades on your Virtual Machine Scale Sets](../virt
 -	Service Fabric [durability level](../service-fabric/service-fabric-cluster-capacity.md#durability-characteristics-of-the-cluster) is Silver or Gold, and not Bronze.
 -	The Service Fabric extension on the scale set model definition must have TypeHandlerVersion 1.1 or above.
 -	Durability level should be the same at the Service Fabric cluster and Service Fabric extension on the scale set model definition.
-- An additional health probe or use of application health extension for Virtual Machine Scale Sets is not required.
+-	An additional health probe or use of application health extension for Virtual Machine Scale Sets is not required.
+-	Stateless nodetypes are the only exception, which have durability as Bronze, but automatic OS image upgrades can still be configured on them. Read more [here](https://docs.microsoft.com/azure/service-fabric/service-fabric-stateless-node-types).
 
 Ensure that durability settings are not mismatched on the Service Fabric cluster and Service Fabric extension, as a mismatch will result in upgrade errors. Durability levels can be modified per the guidelines outlined on [this page](../service-fabric/service-fabric-cluster-capacity.md#changing-durability-levels).
 

articles/service-fabric/service-fabric-stateless-node-types.md

@@ -4,11 +4,11 @@ description: Learn how to create and deploy stateless node types in Azure Servic
 author: peterpogorski
 
 ms.topic: conceptual
-ms.date: 04/16/2021
+ms.date: 10/19/2021
 ms.author: pepogors
 ---
 # Deploy an Azure Service Fabric cluster with stateless-only node types
-Service Fabric node types come with inherent assumption that at some point of time, stateful services might be placed on the nodes. Stateless node types relax this assumption for a node type, thus allowing node type to use other features such as faster scale out operations, support for Automatic OS Upgrades on Bronze durability and scaling out to more than 100 nodes in a single virtual machine scale set.
+Service Fabric node types come with inherent assumption that at some point of time, stateful services might be placed on the nodes. Stateless node types change this assumption for a node type, thus allowing the node type to use other features such as faster scale out operations, support for Automatic OS Upgrades on Bronze durability and scaling out to more than 100 nodes in a single virtual machine scale set.
 
 * Primary node types cannot be configured to be stateless
 * Stateless node types are only supported with Bronze Durability Levels
@@ -68,7 +68,7 @@ To enable stateless node types, you should configure the underlying virtual mach
 
 * The value  **singlePlacementGroup** property, which should be set to **false** if you require to scale to more than 100 VMs.
 * The Scale set's **upgradeMode** should be set to **Rolling**.
-* Rolling Upgrade Mode requires Application Health Extension or Health probes configured. Configure health probe with default configuration for Stateless Node types as suggested below. Once applications are deployed to the node type, Health Probe/Health extension ports can be changed to monitor application health.
+* Rolling Upgrade Mode requires Application Health Extension or Health probes configured. For more details on configuring the health probes or the application health extension refer to this [doc](https://docs.microsoft.com/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade#how-does-automatic-os-image-upgrade-work). Configure health probe with the default configuration for Stateless Node types as suggested below. Once the applications are deployed to the node type, Health Probe/Health extension ports can be changed to monitor the actual application health.
 
 >[!NOTE]
 > While using AutoScaling with Stateless node types, after scale down operation, node state is not automatically cleaned up. In order to cleanup the NodeState of Down Nodes during AutoScale, using [Service Fabric AutoScale Helper](https://github.com/Azure/service-fabric-autoscale-helper) is advised.