Merge pull request #274842 from tomvcassidy/patch-2

adding api version prereq to tls 1.3 doc

Author: prmerger-automator[bot]

articles/service-fabric/how-to-migrate-transport-layer-security.md

@@ -28,6 +28,9 @@ If you only use certificates and don't need to define endpoints for your cluster
     * For managed clusters, you can follow the steps outlined in the [Modify the OS SKU for a node type section of the Service Fabric managed cluster node types how-to guide](how-to-managed-cluster-modify-node-type.md#modify-the-os-sku-for-a-node-type).
     * For classic clusters, you can follow the steps outlined in [Scale up a Service Fabric cluster primary node type](service-fabric-scale-up-primary-node-type.md).
 1. Determine if you use token-based authentication. You can check in the portal or review your cluster's manifest in the Service Fabric Explorer. If you do use token-based authentication, Microsoft Entra ID settings appear in the cluster manifest.
+1. Use the correct API version for deployments, depending on your cluster type:
+    * For managed clusters, use `2023-12-01-preview` or higher
+    * For classic clusters, use `2023-11-01-preview` or higher
 
 Once you complete these prerequisite steps, you're ready to enable TLS 1.3 on your Service Fabric clusters.
 
@@ -128,4 +131,4 @@ You can follow the steps in the appropriate quickstart for the type of Service F
 
 There aren't any specific steps you need to complete after migrating your cluster to TLS 1.3. However, some useful related articles are including in the following links:
 * [X.509 Certificate-based authentication in Service Fabric clusters](cluster-security-certificates.md)
-* [Manage certificates in Service Fabric clusters](cluster-security-certificate-management.md)
+* [Manage certificates in Service Fabric clusters](cluster-security-certificate-management.md)