Update SAP workload deployment checklist

Revised support contract recommendation and clarified escalation paths for Microsoft support regarding SAP workloads.

Author: msftrobiro

articles/sap/workloads/deployment-checklist.md

@@ -92,7 +92,7 @@ Further included in same technical document(s) should be:
   - Azure resource naming strategy
   - Security operations for Azure resources and workloads within
 - Security concept for protecting your SAP workload. This should include all aspects – networking and perimeter monitoring, application and database security, operating systems securing, and any infrastructure measures required, such as encryption. Identify the requirements with your compliance and security teams.
-- Microsoft recommends either Professional Direct, Premier or Unified Support contract. Identify your escalation paths and contacts for support with Microsoft. For SAP support requirements, see [SAP note 2015553](https://launchpad.support.sap.com/#/notes/2015553).
+- Identify your escalation paths and contacts for support with Microsoft. Consult [SAP note 2015553](https://launchpad.support.sap.com/#/notes/2015553) for the required Microsoft support contract to run SAP workloads in Azure.
 - The number of Azure subscriptions and core quota for the subscriptions. [Open support requests to increase quotas of Azure subscriptions](/azure/azure-portal/supportability/regional-quota-requests) as needed.
 - Data reduction and data migration plan for migrating SAP data into Azure. For SAP NetWeaver systems, SAP has guidelines on how to limit the volume of large amounts of data. See [this SAP guide](https://wiki.scn.sap.com/wiki/download/attachments/247399467/DVM_%20Guide_7.2.pdf?version=1&modificationDate=1549365516000&api=v2) about data management in SAP ERP systems. Some of the content also applies to NetWeaver and S/4HANA systems in general.
 - An automated deployment approach. Many customers start with scripts, using a combination of PowerShell, CLI, Ansible and Terraform.