Merge pull request #118012 from sushantjrao/patch-2

Update best-practices-onboard-deploy.md

Author: Court72

articles/operator-service-manager/best-practices-onboard-deploy.md

@@ -38,7 +38,7 @@ NFDG represents the smallest component that you plan to reuse independently acro
 
 For Containerized Network Function Definition Versions (CNF NFDVs), the networkFunctionApplications list can only contain helm packages. It's reasonable to include multiple helm packages if they're always deployed and deleted together.
 
-For Virtualized Network Function Definition Versions (VNF NFDVs), the networkFunctionApplications list must contain one VhdImageFile and one ARM template. The ARM template should deploy a single VM. To deploy multiple VMs for a single VNF, make sure to use separate ARM templates for each VM. 
+For Virtualized Network Function Definition Versions (VNF NFDVs), the networkFunctionApplications list must contain at least one VhdImageFile and one ARM template. The ARM template should deploy a single VM. To deploy multiple VMs for a single VNF, make sure to use separate ARM templates for each VM. 
 
 The ARM template can only deploy ARM resources from the following Resource Providers:
 
@@ -50,6 +50,9 @@ The ARM template can only deploy ARM resources from the following Resource Provi
 - Microsoft.Authorization
 - Microsoft.ManagedIdentity
 
+>[!NOTE] 
+> For ARM templates containing anything beyond the above list, all PUT calls and Re-PUT on the VNF will result in validation error. 
+
 ### Common use cases that trigger Network Function Design Version minor or major version update
 
 - Updating CGS / CGV for an existing release that triggers changing the deployParametersMappingRuleProfile.