Merge pull request #268777 from tomvcassidy/sfCustomerWarning

Updating various SF documents to include warnings for managed cluster configuration

Author: prmerger-automator[bot]

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

@@ -7,11 +7,10 @@ metadata:
   author: tomvcassidy
   ms.service: service-fabric
   services: service-fabric
-  ms.date: 07/11/2022
+  ms.date: 03/12/2024
 title: Service Fabric managed clusters frequently asked questions
 summary: Here are some frequently asked questions (FAQs) and answers for Service Fabric managed clusters.
 
-
 sections:
   - name: General
     questions:
@@ -28,20 +27,20 @@ sections:
       - question: |
           Can I do an in-place migration of my existing Service Fabric cluster to a managed cluster resource?
         answer: |
-          No. You will need to create a new Service Fabric cluster resource to use the new Service Fabric managed cluster resource type.
+          No, you need to create a new Service Fabric cluster resource to use the new Service Fabric managed cluster resource type.
 
       - question: |
           Is there an additional cost for Service Fabric managed clusters?
         answer: |
-          No. There is no additional cost associated with a Service Fabric managed cluster beyond the cost of the underlying compute, storage, and networking resources that are required for the cluster.
+          No, there's no additional cost associated with a Service Fabric managed cluster beyond the cost of the underlying compute, storage, and networking resources that are required for the cluster.
 
       - question: |
           Is there a new SLA introduced by the Service Fabric managed cluster resource?
         answer: |
           The SLA doesn't change from the current Service Fabric resource model.
 
       - question: |
-          What is the difference between a Basic, and Standard SKU cluster?
+          What's the difference between a Basic, and Standard SKU cluster?
         answer: |
           Basic SKU clusters are intended to be used for testing and pre production environments with support for minimal configuration change. A Standard SKU cluster allows users to configure the cluster to specifically meet their needs. For more information, see [Service Fabric managed cluster SKUs](./overview-managed-cluster.md#service-fabric-managed-cluster-skus).
       
@@ -65,27 +64,27 @@ sections:
       - question: | 
           Can I change the Microsoft Entra tenant after initial deployment?
         answer: |
-          No. At this time you would need to create a new Service Fabric managed cluster resource.
+          No, you need to create a new Service Fabric managed cluster resource.
 
       - question: | 
           Can I transfer my subscription to a different Microsoft Entra tenant?
         answer: |
-          No. At this time you would need to create a new Service Fabric managed cluster resource after the subscription has been transferred to a different Microsoft Entra tenant.
+          No, you need to create a new Service Fabric managed cluster resource after the subscription has been transferred to a different Microsoft Entra tenant.
       
       - question: | 
           Can I move/migrate my cluster between Microsoft Entra tenants?
         answer: |
-          No. At this time you would need to create a new Service Fabric managed cluster resource under the new tenant.
+          No, you need to create a new Service Fabric managed cluster resource under the new tenant.
       
       - question: | 
           Can I move/migrate my cluster between subscriptions?
         answer: |
-          No. At this time you would need to create a new Service Fabric managed cluster resource under the new subscription.
+          No, you need to create a new Service Fabric managed cluster resource under the new subscription.
       
       - question: | 
           Can I move/migrate my cluster or cluster resources to other resource groups or rename them?
         answer: |
-          No. At this time you would need to create a new Service Fabric managed cluster resource under the new resource group/name.
+          No, you need to create a new Service Fabric managed cluster resource under the new resource group/name.
 
       - question: |
           I want to enable IPv6, is that possible?
@@ -127,6 +126,10 @@ sections:
         answer: |
           Connecting to a Service Fabric Explorer (SFX) endpoint on a managed cluster will result in a certificate error 'NET::ERR_CERT_AUTHORITY_INVALID' regardless of certificate being used or cluster configuration. This is because the cluster nodes are using the managed 'cluster' certificate when binding FabricGateway (19000) and FabricHttpGateway (19080) TCP ports and is by design.
           
+      - question: |
+          Can I manually make changes to a managed cluster's resources? 
+        answer: |
+          No, manually making changes to a managed cluster's resource isn't supported.
 
   - name: Applications
     questions:

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

@@ -6,7 +6,7 @@ ms.author: tomcassidy
 author: tomvcassidy
 ms.service: service-fabric
 services: service-fabric
-ms.date: 07/11/2022
+ms.date: 03/12/2024
 ---
 
 # Service Fabric managed cluster configuration options
@@ -29,6 +29,9 @@ In addition to selecting the [Service Fabric managed cluster SKU](overview-manag
 * Configure [Dedicated Hosts](how-to-managed-cluster-dedicated-hosts.md) with managed cluster
 * Use [Ephemeral OS disks](how-to-managed-cluster-ephemeral-os-disks.md) for node types in managed cluster
 
+> [!IMPORTANT]
+> Manually making changes to the resources in a managed cluster isn't supported.
+
 ## Next steps
 
 [Service Fabric managed clusters overview](overview-managed-cluster.md)

articles/service-fabric/how-to-managed-cluster-maintenance-control.md

@@ -2,18 +2,18 @@
 title: Configure maintenance control for Service Fabric managed cluster
 description: Learn how to configure maintenance control for Service Fabric managed cluster
 ms.topic: how-to
-ms.author: ashank
-author: ashank
+ms.author: tomcassidy
+author: tomvcassidy
 ms.service: service-fabric
 services: service-fabric
-ms.date: 05/31/2023
+ms.date: 03/12/2024
 ---
 
 # (Preview) Introduction to MaintenanceControl on Service Fabric managed clusters
 Service Fabric managed clusters have multiple background operations that are necessary to the keep all the cluster updated, thus ensuring security and reliability. Even though these operations are critical, but executing in the background can result in the service replica to move to a different node. This failover results in 
 undesired and unnecessary interruptions, if the maintenance operation executes during the peak business hours. With the support for MaintenanceControl in Service Fabric managed clusters, customers would be able to define a recurring (daily, weekly, monthly) and custom maintenance window for their SFMC cluster resource, 
 as per their needs. All background maintenance operations will be allowed to execute only during this maintenance window. MaintenanceControl is applicable to these background operations:
-* Automatic OSUpgrade
+* Automatic OS Upgrade
 * Automatic extension upgrade
 * Automatic SF runtime version updates
 * Automatic cluster certificate update
@@ -25,13 +25,9 @@ as per their needs. All background maintenance operations will be allowed to exe
 * Maintenance window configuration needs to be defined only for the Service Fabric managed cluster resource
 * The minimum supported window size is 5 hours
 
->[!NOTE]
->* This should only be enabled in the listed regions. In all other regions, configuring this will not have any impact on the maintenance operations. There is work underway to block creation of maintenance configuration for SFMC, where it is not supported right now.
->* Supported Regions: eastus, eastus2, westus, westus2, westus3, southcentralus, centralus, westeurope, northeurope, ukwest, uksouth, australiaeast, australiasoutheast, northcentralus, eastasia, southeastasia, japaneast, japanwest, southindia, westindia, centralindia, brazilsouth, koreacentral, koreasouth, centralcanada, eastcanada, francecentral, francesouth, australiacentral, australiacentral2, southafricawest, southafricanorth, uaecentral, uaenorth, switzerlandwest, switzerlandnorth, germanynorth, germanywestcentral, norwayeast, norwaywest, brazilsoutheast, jioindiawest, jioindiacentral, swedensouth, swedencentral, qatarcentral, polandcentral
-
 ## How does MaintenanceControl work for SFMC
 * Customers need to define a maintenance configuration that contains the schedule and the recurrence rule for the maintenance window, by creating a maintenance configuration resource with the maintenance RP. [More details](../virtual-machines/maintenance-and-updates.md)
-* Using this maintenance configuration, an assignment resource is created to assign the maintenance configuration to the SFMC cluster resource.
+* With this maintenance configuration, an assignment resource is created to assign the maintenance configuration to the SFMC cluster resource.
 * on the creation of the assignment resource, the maintenance RP notifies the ServiceFabric RP about the link and maintenance control is then enabled on the SFMC cluster. All background maintenance operations are blocked outside the maintenance window.
 * Whenever the maintenance window is activated as per the schedule in the maintenance configuration, the maintenance RP notifies the ServiceFabric RP that activates the maintenance window on corresponding SFMC cluster. All background operations are allowed to execute during this window.
 

articles/service-fabric/overview-managed-cluster.md

@@ -6,22 +6,22 @@ ms.author: tomcassidy
 author: tomvcassidy
 ms.service: service-fabric
 services: service-fabric
-ms.date: 07/11/2022
+ms.date: 03/12/2024
 ---
 
 # Service Fabric managed clusters
 
 Service Fabric managed clusters are an evolution of the Azure Service Fabric cluster resource model that streamlines your deployment and cluster management experience.
 
-The Azure Resource Model (ARM) template for traditional Service Fabric clusters requires you to define a cluster resource alongside a number of supporting resources, all of which must be "wired up"  correctly (upon deployment and throughout the lifecycle of the cluster) in order for the cluster and your services to function properly. In contrast, the encapsulation model for Service Fabric managed clusters consists of a single, *Service Fabric managed cluster* resource. All of the underlying resources for the cluster are abstracted away and managed by Azure on your behalf.
+The Azure Resource Model (ARM) template for traditional Service Fabric clusters requires you to define a cluster resource alongside a number of supporting resources, These resources must be configured correctly for the cluster and your services to function properly. In contrast, the encapsulation model for Service Fabric managed clusters consists of a single, *Service Fabric managed cluster* resource. All of the underlying resources for the cluster are abstracted away and managed by Azure on your behalf.
 
 **Service Fabric traditional cluster model**
 ![Service Fabric traditional cluster model][sf-composition]
 
 **Service Fabric managed cluster model**
 ![Service Fabric encapsulated cluster model][sf-encapsulation]
 
-In terms of size and complexity, the ARM template for a Service Fabric managed cluster is about 100 lines of JSON, versus some 1000 lines required to define a typical Service Fabric cluster:
+In terms of size and complexity, the ARM template for a Service Fabric managed cluster is about 100 lines of JSON, versus some 1,000 lines required to define a typical Service Fabric cluster:
 
 | Service Fabric resources | Service Fabric managed cluster resources |
 |----------|-----------|
@@ -49,27 +49,30 @@ Service Fabric managed clusters provide a number of advantages over traditional
 **Best practices by default**
 - Simplified reliability and durability settings
 
-There is no additional cost for Service Fabric managed clusters beyond the cost of underlying resources required for the cluster, and the same Service Fabric SLA applies for managed clusters.
+There's no extra cost for Service Fabric managed clusters beyond the cost of underlying resources required for the cluster, and the same Service Fabric Service Leval Agreement (SLA) applies for managed clusters.
 
 > [!NOTE]
 > There is no migration path from existing Service Fabric clusters to managed clusters. You will need to create a new Service Fabric managed cluster to use this new resource type.
 
+> [!IMPORTANT]
+> Manually making changes to the resources in a managed cluster isn't supported.
+
 ## Service Fabric managed cluster SKUs
 
 Service Fabric managed clusters are available in both Basic and Standard SKUs.
 
 | Feature | Basic | Standard |
 | ------- | ----- | -------- |
 | Network resource (SKU for [Load Balancer](../load-balancer/skus.md), [Public IP](../virtual-network/ip-services/public-ip-addresses.md)) | Basic | Standard |
-| Min node (VM instance) count | 3 | 5 |
+| Min node (virtual machine instance) count | 3 | 5 |
 | Max node count per node type | 100 | 1000 |
 | Max node type count | 1 | 50 |
 | Add/remove node types | No | Yes |
 | Zone redundancy | No | Yes |
 
 ## Feature support
 
-The capabilities of managed clusters will continue to expand. See [managed cluster configuration options documentation](how-to-managed-cluster-configuration.md) or managedClusters [Bicep & ARM templates](/azure/templates/microsoft.servicefabric/allversions) for more information.
+See [managed cluster configuration options documentation](how-to-managed-cluster-configuration.md) or managedClusters [Bicep & ARM templates](/azure/templates/microsoft.servicefabric/allversions) for more information.
 
 
 ## Next steps

articles/service-fabric/tutorial-managed-cluster-deploy.md

@@ -1,17 +1,17 @@
 ---
 title: Deploy a Service Fabric managed cluster
-description: In this tutorial, you will deploy a Service Fabric managed cluster for testing.
+description: In this tutorial, you deploy a Service Fabric managed cluster for testing.
 ms.topic: tutorial
 ms.author: tomcassidy
 author: tomvcassidy
 ms.service: service-fabric
 services: service-fabric
-ms.date: 07/14/2022
+ms.date: 03/12/2024
 ---
 
 # Tutorial: Deploy a Service Fabric managed cluster
 
-In this tutorial series we will discuss:
+In this tutorial series, we discuss:
 
 > [!div class="checklist"]
 > * How to deploy a Service Fabric managed cluster 
@@ -31,7 +31,7 @@ This part of the series covers how to:
 
 Before you begin this tutorial:
 
-* Create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) if you don't already have an Azure subscription
+* Create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) if you don't already have an Azure subscription.
 
 * Install the [Service Fabric SDK and PowerShell module](service-fabric-get-started.md).
 
@@ -62,14 +62,14 @@ New-AzResourceGroup -Name $resourceGroup -Location $location
 
 ### Create a Service Fabric managed cluster
 
-In this step, you will create a Service Fabric managed cluster using the New-AzServiceFabricManagedCluster PowerShell command. The following example creates a cluster named myCluster in the resource group named myResourceGroup. This resource group was created in the previous step in the eastus2 region.
+In this step, you create a Service Fabric managed cluster using the New-AzServiceFabricManagedCluster PowerShell command. The following example creates a cluster named myCluster in the resource group named myResourceGroup. This resource group was created in the previous step in the eastus2 region.
 
 For this step, provide your own values for the following  parameters:
 
 * **Cluster Name**: Enter a unique name for your cluster, such as *mysfcluster*.
-* **Admin Password**: Enter a password for the admin to be used for RDP on the underlying VMs in the cluster.
-* **Client Certificate Thumbprint**: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you do not have a certificate, follow [set and retrieve a certificate](../key-vault/certificates/quick-create-portal.md) to create a self-signed certificate.
-* **Cluster SKU**: Specify the [type of Service Fabric managed cluster](overview-managed-cluster.md#service-fabric-managed-cluster-skus) to deploy. *Basic* SKU clusters are meant for test deployments only, and do not allow for node type addition or removal.
+* **Admin Password**: Enter a password for the admin to be used for Remote Desktop Protocol (RDP) on the underlying VMs in the cluster.
+* **Client Certificate Thumbprint**: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you don't have a certificate, follow [set and retrieve a certificate](../key-vault/certificates/quick-create-portal.md) to create a self-signed certificate.
+* **Cluster SKU**: Specify the [type of Service Fabric managed cluster](overview-managed-cluster.md#service-fabric-managed-cluster-skus) to deploy. *Basic* SKU clusters are meant for test deployments only, and don't allow for node type addition or removal.
 
 ```powershell
 $clusterName = "<unique cluster name>"
@@ -82,7 +82,7 @@ New-AzServiceFabricManagedCluster -ResourceGroupName $resourceGroup -Location $l
 
 ### Add a primary node type to the Service Fabric managed cluster
 
-In this step, you will add a primary node type to the cluster that you have just created. Every Service Fabric cluster must have at least one primary node type.
+In this step, you add a primary node type to the cluster that you created. Every Service Fabric cluster must have at least one primary node type.
 
 For this step, provide your own values for the following  parameters:
 
@@ -105,6 +105,9 @@ This command may take a few minutes to complete.
 
 Once the deployment completes, find the Service Fabric Explorer value in the Service Fabric managed cluster resource overview page in Portal. When prompted for a certificate, use the certificate for which the client thumbprint was provided in the PowerShell command.
 
+> [!IMPORTANT]
+> Manually making changes to the resources in a managed cluster isn't supported.
+
 ## Next steps
 
 In this step we created and deployed our first Service Fabric managed cluster. To learn more about how to scale a cluster, see: