Merge pull request #278273 from tomvcassidy/versionsDependentToNodeType

versions dependent on nodetype

Author: prmerger-automator[bot]

articles/service-fabric/how-to-managed-cluster-app-deployment-template.md

@@ -7,7 +7,7 @@ author: tomvcassidy
 ms.service: service-fabric
 ms.custom: devx-track-arm-template
 services: service-fabric
-ms.date: 05/24/2023
+ms.date: 06/14/2024
 ---
 
 # Manage application lifecycle on a managed cluster using Azure Resource Manager
@@ -28,6 +28,9 @@ In this document, you will learn how to:
 > * Upgrade service fabric application resources by using Resource Manager.
 > * Delete service fabric application resources.
 
+> [!NOTE]
+> This document is part four of a four-part tutorial series, beginning with [deploying a Service Fabric managed cluster](tutorial-managed-cluster-deploy.md). As such, it's expected that you deployed your cluster before this step. However, if you intend to deploy your cluster and application together, in the same ARM or Bicep template, know that `versions` must have a dependency on `nodeType`. Otherwise, the deployment fails.
+
 ## Deploy Service Fabric application resources
 
 The high-level steps you take to deploy an application and its services by using the Resource Manager application resource model are: