Merge pull request #188414 from craftyhouse/sfmc-2022-01-01-release

Sfmc 2022 01 01 release

Author: jborsecnik

articles/service-fabric/faq-managed-cluster.yml

@@ -6,7 +6,7 @@ metadata:
   ms.author: micraft
   author: craftyhouse
   ms.service: service-fabric
-  ms.date: 8/23/2021
+  ms.date: 2/14/2022
   ms.custom: references_regions
 
 title: Service Fabric managed clusters frequently asked questions
@@ -61,27 +61,27 @@ sections:
       - question: |
           I want to have an internal-only load balancer, is that possible?
         answer: |
-          This is supported with the 2021-07-01-preview release. See [Configure network settings for Service Fabric managed clusters](./how-to-managed-cluster-networking.md#byolb)
+          Yes, you can configure internal-only load balancer. See [Configure network settings for Service Fabric managed clusters](./how-to-managed-cluster-networking.md#byolb)
       
       - question: | 
-          Can I change the  Azure AD tenant after initial deployment?
+          Can I change the Azure AD tenant after initial deployment?
         answer: |
           No. At this time you would need to create a new Service Fabric managed cluster resource.
 
       - question: |
           I want to enable IPv6, is that possible?
         answer: |
-          This is supported with the 2021-07-01-preview release. See [Configure network settings for Service Fabric managed clusters](./how-to-managed-cluster-networking.md#ipv6)
+          Yes, see [Configure network settings for Service Fabric managed clusters](./how-to-managed-cluster-networking.md#ipv6)
 
       - question: |
           I want to use an existing VNet for a Service Fabric managed cluster, can I do that?
         answer: |
-          This is supported with the 2021-07-01-preview release. See [Configure network settings for Service Fabric managed clusters](./how-to-managed-cluster-networking.md#byolb)
+          Yes, see [Configure network settings for Service Fabric managed clusters](./how-to-managed-cluster-networking.md#byolb)
 
       - question: |
           Can I autoscale my cluster?
         answer: |
-          Autoscaling is [available](./how-to-managed-cluster-autoscale.md)
+          Yes, you can enable [autoscaling](./how-to-managed-cluster-autoscale.md)
 
       - question: |
           Can I deploy my cluster across availability zones?

articles/service-fabric/how-to-managed-cluster-autoscale.md

@@ -2,15 +2,15 @@
 title: Configure autoscaling for Service Fabric managed cluster nodes
 description: Learn how to configure autoscaling policies on Service Fabric managed cluster.
 ms.topic: how-to
-ms.date: 10/25/2021
+ms.date: 2/14/2022
 ---
 
-# Introduction to Autoscaling on Service Fabric managed clusters (preview)
+# Introduction to Autoscaling on Service Fabric managed clusters
 [Autoscaling](../azure-monitor/autoscale/autoscale-overview.md) gives great elasticity and enables addition or reduction of nodes on demand on a secondary node type. This automated and elastic behavior reduces the management overhead and potential business impact by monitoring and optimizing the amount of nodes servicing your workload. You configure rules for your workload and let autoscaling handle the rest. When those defined thresholds are met, autoscale rules take action to adjust the capacity of your node type. Autoscaling can be enabled, disabled, or configured at any time. This article provides an example deployment, how to enable or disable autoscaling, and how to configure an example autoscale policy.
 
 
 **Requirements and supported metrics:**
-* In order to use autoscaling on managed clusters, you need to be using API version `2021-07-01-preview` or later.
+* The Service Fabric managed cluster resource apiVersion should be **2022-01-01** or later.
 * The cluster SKU must be Standard.
 * Can only be configured on a secondary node type in your cluster.
 * After enabling autoscale for a node type, configure `vmInstanceCount` property to `-1` when redeploying the resource.
@@ -134,7 +134,7 @@ The following example will set a policy for `nodeType2Name` to be at least 3 nod
                                 "metricTrigger": {
                                   "metricName": "Percentage CPU",
                                   "metricNamespace": "",
-                                  "metricResourceUri": "[concat('/subscriptions/',subscription().subscriptionId,'/resourceGroups/SFC_', reference(resourceId('Microsoft.ServiceFabric/managedClusters', parameters('clusterName')), '2021-07-01-preview').clusterId,'/providers/Microsoft.Compute/virtualMachineScaleSets/',parameters('nodeType2Name'))]",
+                                  "metricResourceUri": "[concat('/subscriptions/',subscription().subscriptionId,'/resourceGroups/SFC_', reference(resourceId('Microsoft.ServiceFabric/managedClusters', parameters('clusterName')), '2022-01-01').clusterId,'/providers/Microsoft.Compute/virtualMachineScaleSets/',parameters('nodeType2Name'))]",
                                   "timeGrain": "PT1M",
                                   "statistic": "Average",
                                   "timeWindow": "PT30M",
@@ -153,7 +153,7 @@ The following example will set a policy for `nodeType2Name` to be at least 3 nod
                                 "metricTrigger": {
                                   "metricName": "Percentage CPU",
                                   "metricNamespace": "",
-                                  "metricResourceUri": "[concat('/subscriptions/',subscription().subscriptionId,'/resourceGroups/SFC_', reference(resourceId('Microsoft.ServiceFabric/managedClusters', parameters('clusterName')), '2021-07-01-preview').clusterId,'/providers/Microsoft.Compute/virtualMachineScaleSets/',parameters('nodeType2Name'))]",
+                                  "metricResourceUri": "[concat('/subscriptions/',subscription().subscriptionId,'/resourceGroups/SFC_', reference(resourceId('Microsoft.ServiceFabric/managedClusters', parameters('clusterName')), '2022-01-01').clusterId,'/providers/Microsoft.Compute/virtualMachineScaleSets/',parameters('nodeType2Name'))]",
                                   "timeGrain": "PT1M",
                                   "statistic": "Average",
                                   "timeWindow": "PT30M",

articles/service-fabric/how-to-managed-cluster-enable-disk-encryption.md

@@ -2,15 +2,15 @@
 title: Enable Disk Encryption for Service Fabric managed cluster nodes
 description: Learn how to enable disk encryption for Azure Service Fabric managed cluster nodes in Windows using an ARM template.
 ms.topic: how-to
-ms.date: 11/8/2021 
+ms.date: 2/14/2022 
 ms.custom: devx-track-azurepowershell
 ---
 # Enable disk encryption for Service Fabric managed cluster nodes
 
 Service Fabric managed clusters support two disk encryption options to help safeguard your data to meet your organizational security and compliance commitments. The recommended option is Encryption at host, but also supports Azure Disk Encryption. Review the [disk encryption options](../virtual-machines/disk-encryption-overview.md) and make sure the selected option meets your needs.
 
 
-## Enable encryption at host (preview)
+## Enable encryption at host
 
 This encryption method improves on [Azure Disk Encryption](how-to-managed-cluster-enable-disk-encryption.md) by supporting all OS types and images, including custom images, for your VMs by encrypting data in the Azure Storage service. This method does not use your VMs CPU nor does it impact your VMs performance enabling workloads to use all of the available VMs SKU resources.
 

articles/service-fabric/how-to-managed-cluster-managed-disk.md

@@ -2,7 +2,7 @@
 title: Select managed disk types for Service Fabric managed cluster nodes
 description: Learn how to select managed disk types for Service Fabric managed cluster nodes and configure in an ARM template.
 ms.topic: how-to
-ms.date: 11/19/2021
+ms.date: 2/14/2022
 ---
 
 # Select managed disk types for Service Fabric managed cluster nodes
@@ -24,7 +24,7 @@ Azure Service Fabric manged clusters support the following managed disk types:
     * Premium SSD locally redundant storage. Best for production and performance sensitive workloads.
 
 >[!NOTE]
-> Any temp disk associated with VM Size will *not* be used for storing any Service Fabric or application related data
+> Any temp disk associated with VM Size will *not* be used for storing any Service Fabric or application related data by default. [Stateless node types](how-to-managed-cluster-stateless-node-type.md) do support temp disks if required.
 
 ## Specifying a Service Fabric managed cluster disk type
 

articles/service-fabric/how-to-managed-cluster-modify-node-type.md

@@ -2,7 +2,7 @@
 title: Configure or modify a Service Fabric managed cluster node type
 description: This article walks through how to modify a managed cluster node type
 ms.topic: how-to
-ms.date: 12/10/2021 
+ms.date: 2/14/2022 
 ---
 
 # Service Fabric managed cluster node types
@@ -192,15 +192,15 @@ You can choose to enable automatic OS image upgrades to the virtual machines run
 
 To enable automatic OS upgrades:
 
-* Use the `2021-05-01` (or later) version of *Microsoft.ServiceFabric/managedclusters* and *Microsoft.ServiceFabric/managedclusters/nodetypes* resources
+* Use apiVersion `2021-05-01` or later version of *Microsoft.ServiceFabric/managedclusters* and *Microsoft.ServiceFabric/managedclusters/nodetypes* resources
 * Set the cluster's property `enableAutoOSUpgrade` to *true*
 * Set the cluster nodeTypes' resource property `vmImageVersion` to *latest*
 
 For example:
 
 ```json
     {
-      "apiVersion": "2021-05-01",
+      "apiVersion": "[variables('sfApiVersion')]",
       "type": "Microsoft.ServiceFabric/managedclusters",
       ...
       "properties": {
@@ -209,7 +209,7 @@ For example:
       },
     },
     {
-      "apiVersion": "2021-05-01",
+      "apiVersion": "[variables('sfApiVersion')]",
       "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
        ...
       "properties": {
@@ -339,7 +339,7 @@ Service Fabric managed cluster does not support in-place modification of the VM
 * [Delete old node type via portal or PowerShell](how-to-managed-cluster-modify-node-type.md#remove-a-node-type). To remove a primary node type you will have to use PowerShell.
 
 
-## Configure multiple managed disks (preview)
+## Configure multiple managed disks
 Service Fabric managed clusters by default configure one managed disk. By configuring the following optional property and values, you can add more managed disks to node types within a cluster. You are able to specify the drive letter, disk type, and size per disk.
 
 Configure more managed disks by declaring `additionalDataDisks` property and required parameters in your Resource Manager template as follows:
@@ -348,7 +348,7 @@ Configure more managed disks by declaring `additionalDataDisks` property and req
 * Lun must be unique per disk and can not use reserved lun 0
 * Disk letter cannot use reserved letters C or D and cannot be modified once created. S will be used as default if not specified.
 * Must specify a [supported disk type](how-to-managed-cluster-managed-disk.md)
-* The Service Fabric managed cluster resource apiVersion must be **2021-11-01-preview** or later.
+* The Service Fabric managed cluster resource apiVersion should be **2022-01-01** or later.
 
 ```json
      {
@@ -369,12 +369,12 @@ Configure more managed disks by declaring `additionalDataDisks` property and req
 
 See [full list of parameters available](/azure/templates/microsoft.servicefabric/2021-11-01-preview/managedclusters)
 
-## Configure the Service Fabric data disk drive letter (preview)
+## Configure the Service Fabric data disk drive letter
 Service Fabric managed clusters by default configure a Service Fabric data disk and automatically configure the drive letter on all nodes of a node type. By configuring this optional property and value, you can specify and retrieve the Service Fabric data disk letter if you have specific requirements for drive letter mapping.
 
 **Feature Requirements**
 * Disk letter cannot use reserved letters C or D and cannot be modified once created. S will be used as default if not specified.
-* The Service Fabric managed cluster resource apiVersion must be **2021-11-01-preview** or later.
+* The Service Fabric managed cluster resource apiVersion should be **2022-01-01** or later.
 
 ```json
      {