Merge pull request #291977 from MicrosoftDocs/repo_sync_working_branch

PhilKang0704 · web-flow · commit c475cf453d0c · 2024-12-16T13:13:36.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/sap/automation/configure-devops.md b/articles/sap/automation/configure-devops.md
@@ -488,7 +488,7 @@ s-password="<SAP Support user password>"
 
 az devops login
 
-az pipelines variable-group create --name SDAF-General --variables ANSIBLE_HOST_KEY_CHECKING=false Deployment_Configuration_Path=WORKSPACES Branch=main S-Username=$s-user S-Password=$s-password tf_varsion=1.3.0 --output yaml
+az pipelines variable-group create --name SDAF-General --variables ANSIBLE_HOST_KEY_CHECKING=false Deployment_Configuration_Path=WORKSPACES Branch=main S-Username=$s-user S-Password=$s-password tf_version=1.3.0 --output yaml
 
 ```
 
diff --git a/articles/sap/automation/integration-azure-monitor-sap.md b/articles/sap/automation/integration-azure-monitor-sap.md
@@ -81,7 +81,7 @@ create_ams_instance = true
 # ams_instance_name is an optional parameter and should only be used if the default naming is not acceptable
 ams_instance_name = "AMS-RESOURCE"
 
-# ams_laws_arm_id is a optional parameter to use an exisiting log analytics for the AMS instance
+# ams_laws_arm_id is a optional parameter to use an existing log analytics for the AMS instance
 ams_laws_arm_id = "/subscriptions/0000000-000000-0000000-0000000000/resourcegroups/rg-name/providers/microsoft.operationalinsights/workspaces/workspacename"
 
 ```
diff --git a/articles/sap/center-sap-solutions/quickstart-create-distributed-non-high-availability.md b/articles/sap/center-sap-solutions/quickstart-create-distributed-non-high-availability.md
@@ -36,7 +36,7 @@ After you deploy infrastructure and [install SAP software](install-software.md)
     ```
 
 - An Azure account with **Azure Center for SAP solutions administrator** and **Managed Identity Operator** role access to the subscriptions and resource groups in which you'll create the Virtual Instance for SAP solutions (VIS) resource.
-- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Subscription or atleast all resource groups (Compute, Network,Storage). If you wish to install SAP Software through the Azure Center for SAP solutions, also provide **Reader and Data Access** role to the identity on SAP bits storage account where you would store the SAP Media.
+- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Subscription or at least all resource groups (Compute, Network,Storage). If you wish to install SAP Software through the Azure Center for SAP solutions, also provide **Reader and Data Access** role to the identity on SAP bits storage account where you would store the SAP Media.
 - A [network set up for your infrastructure deployment](prepare-network.md).
 - Availability of minimum 4 cores of either Standard_D4ds_v4 or Standard_E4s_v3 SKUS which will be used during Infrastructure deployment and Software Installation
 - [Review the quotas for your Azure subscription](/azure/quotas/view-quotas). If the quotas are low, you might need to create a support request before creating your infrastructure deployment. Otherwise, you might experience deployment failures or an **Insufficient quota** error. 
diff --git a/articles/sap/center-sap-solutions/quickstart-create-high-availability-namecustom.md b/articles/sap/center-sap-solutions/quickstart-create-high-availability-namecustom.md
@@ -36,7 +36,7 @@ After you deploy infrastructure and [install SAP software](install-software.md)
     ```
 
 - An Azure account with **Azure Center for SAP solutions administrator** and **Managed Identity Operator** role access to the subscriptions and resource groups in which you create the Virtual Instance for SAP solutions (VIS) resource.
-- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Subscription or atleast all resource groups (Compute, Network,Storage). If you wish to install SAP Software through the Azure Center for SAP solutions, also provide **Reader and Data Access** role to the identity on SAP bits storage account where you would store the SAP Media.
+- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Subscription or at least all resource groups (Compute, Network,Storage). If you wish to install SAP Software through the Azure Center for SAP solutions, also provide **Reader and Data Access** role to the identity on SAP bits storage account where you would store the SAP Media.
 - A [network set up for your infrastructure deployment](prepare-network.md).
 - Availability of minimum 4 cores of either Standard_D4ds_v4 or Standard_E4s_v3, SKUS which will be used during Infrastructure deployment and Software Installation
 - [Review the quotas for your Azure subscription](/azure/quotas/view-quotas). If the quotas are low, you might need to create a support request before creating your infrastructure deployment. Otherwise, you might experience deployment failures or an **Insufficient quota** error. 
diff --git a/articles/sap/center-sap-solutions/quickstart-install-distributed-non-high-availability.md b/articles/sap/center-sap-solutions/quickstart-install-distributed-non-high-availability.md
@@ -29,7 +29,7 @@ After you [deploy infrastructure](deploy-s4hana.md) and install SAP software wit
 ## Prerequisites
 - An Azure subscription.
 - An Azure account with **Azure Center for SAP solutions administrator** and **Managed Identity Operator** role access to the subscriptions and resource groups in which you'll create the Virtual Instance for SAP solutions (VIS) resource.
-- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Subscription or atleast all resource groups (Compute, Network,Storage). 
+- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Subscription or at least all resource groups (Compute, Network,Storage). 
 - A storage account where you would store the SAP Media
 - **Reader and Data Access** role to the **User-assigned managed identity** on the storage account where you would store the SAP Media.
 - A [network set up for your infrastructure deployment](prepare-network.md).
diff --git a/articles/sap/center-sap-solutions/quickstart-install-high-availability-namecustom-cli.md b/articles/sap/center-sap-solutions/quickstart-install-high-availability-namecustom-cli.md
@@ -29,7 +29,7 @@ After you [deploy infrastructure](deploy-s4hana.md) and install SAP software wit
 ## Prerequisites
 - An Azure subscription.
 - An Azure account with **Azure Center for SAP solutions administrator** and **Managed Identity Operator** role access to the subscriptions and resource groups in which you'll create the Virtual Instance for SAP solutions (VIS) resource.
-- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Subscription or atleast all resource groups (Compute, Network,Storage). 
+- A **User-assigned managed identity** which has **Azure Center for SAP solutions service role** access on the Subscription or at least all resource groups (Compute, Network,Storage). 
 - A storage account where you would store the SAP Media
 - **Reader and Data Access** role to the **User-assigned managed identity** on the storage account where you would store the SAP Media.
 - A [network set up for your infrastructure deployment](prepare-network.md).
diff --git a/articles/sap/center-sap-solutions/soft-stop-sap-and-hana-database.md b/articles/sap/center-sap-solutions/soft-stop-sap-and-hana-database.md
@@ -33,7 +33,7 @@ Using the [Azure PowerShell](/powershell/module/az.workloads), [CLI](/cli/azure/
 Currently, you can initiate a soft stop operation from the Azure PowerShell, Azure Command-Line Interface (Azure CLI) and REST API interfaces. You must use the stop operation along with a soft stop timeout value in seconds to initiate a soft stop. Once you initiate soft stop on VIS and the operation is successfully triggered on the SAP system, then monitor the Health and Status of the VIS to check if the system has stopped. 
 
 > [!NOTE]
-> When attempting to soft stop an SAP system or applicaton server instance using Azure Center for SAP solutions, soft stop timeout value must be greater than 0 and less than 82800 seconds. 
+> When attempting to soft stop an SAP system or application server instance using Azure Center for SAP solutions, soft stop timeout value must be greater than 0 and less than 82800 seconds. 
 
 
 ### Soft stop system in PowerShell
diff --git a/articles/sap/monitor/provider-ha-pacemaker-cluster.md b/articles/sap/monitor/provider-ha-pacemaker-cluster.md
@@ -95,7 +95,7 @@ Example: cd /var/lib/pcp/pmdas/hacluster
     sudo systemctl enable pmproxy
     ```
 
-1. Data gets collected in the system by PCP. You can export the data by using `pmproxy` via URL `http://<ipaddress of the serrver>:44322/metrics?names=ha_cluster`. 
+1. Data gets collected in the system by PCP. You can export the data by using `pmproxy` via URL `http://<ipaddress of the server>:44322/metrics?names=ha_cluster`. 
 To check if the metrics are fetched via URL on the server where the hacluster is installed, Run the following command on the server.
     
     ```bash
diff --git a/articles/sap/workloads/businessobjects-deployment-guide-windows.md b/articles/sap/workloads/businessobjects-deployment-guide-windows.md
@@ -247,7 +247,7 @@ Follow the latest guide by SAP to prepare servers for the installation of the BI
 
 To install the BI platform on a Windows host, sign in with a user that has local administrative privileges.
 
-Go to the media of the SAP BusinsessObjects BI platform, and run `setup.exe`.
+Go to the media of the SAP BusinessObjects BI platform, and run `setup.exe`.
 
 Follow the instructions in the [SAP Business Intelligence Platform Installation Guide for Windows](https://help.sap.com/viewer/df8899896b364f6c880112f52e4d06c8/4.3.1/en-US/46ae62456e041014910aba7db0e91070.html) that are specific to your version. Here are a few points to note while you install the SAP BOBI platform on Windows:
 
diff --git a/articles/sap/workloads/dbms-guide-ibm.md b/articles/sap/workloads/dbms-guide-ibm.md
@@ -90,7 +90,7 @@ IBM Db2 for SAP NetWeaver Applications is supported on any VM type listed in SAP
 Following is a baseline configuration for various sizes and uses of SAP on Db2 deployments from small to x-large.  
 
 >[!IMPORTANT]
-> The VM types listed below are examples that meet the vCPU and memory critiera of each of the categories. The storage configuration is based on Azure premium storage v1. Premium SSD v2 and Azure Ultra disk is fully supported with IBM Db2 as well and can be used for deployments. Use the values for capacity, burst throughput, and burst IOPS to define the Ultra disk or Premium SSD v2 configuration. You can limit the IOPS for the /db2/```<SID>```/log_dir at around 5000 IOPS. Adjust the throughput and IOPS to the specific workload if these baseline recommendations don't meet the requirements
+> The VM types listed below are examples that meet the vCPU and memory criteria of each of the categories. The storage configuration is based on Azure premium storage v1. Premium SSD v2 and Azure Ultra disk is fully supported with IBM Db2 as well and can be used for deployments. Use the values for capacity, burst throughput, and burst IOPS to define the Ultra disk or Premium SSD v2 configuration. You can limit the IOPS for the /db2/```<SID>```/log_dir at around 5000 IOPS. Adjust the throughput and IOPS to the specific workload if these baseline recommendations don't meet the requirements
 
 #### Extra small SAP system: database size 50 - 200 GB: example Solution Manager
 | VM Size / Examples |Db2 mount point |Azure Premium Disk |# of Disks |IOPS |Through-<br />put [MB/s] |Size [GB] |Burst IOPS |Burst Through-<br />put [GB] | Stripe size | Caching |
diff --git a/articles/sap/workloads/dbms-guide-sapase.md b/articles/sap/workloads/dbms-guide-sapase.md
@@ -62,7 +62,7 @@ Separate disks are recommended for Data devices and Log Devices.  The system dat
 ![Storage configuration for SAP ASE](./media/dbms-guide-sap-ase/sap-ase-disk-structure.png)
 
 ### File systems, stripe size & IO balancing 
-SAP ASE writes data sequentially into disk storage devices unless configured otherwise. This means an empty SAP ASE database with four devices wwrites data into the first device only.  The other disk devices are only written into when the first device is full.  The amount of READ and WRITE IO to each SAP ASE device is likely to be different. To balance disk IO across all available Azure disks, either Windows Storage Spaces or Linux LVM2 needs to be used. On Linux, it's recommended to use XFS file system to format the disks. The LVM stripe size should be tested with a performance test. 128 KB stripe size is a good starting point. On Windows, the NTFS Allocation Unit Size (AUS) should be tested. 64 KB can be used as a starting value. 
+SAP ASE writes data sequentially into disk storage devices unless configured otherwise. This means an empty SAP ASE database with four devices writes data into the first device only.  The other disk devices are only written into when the first device is full.  The amount of READ and WRITE IO to each SAP ASE device is likely to be different. To balance disk IO across all available Azure disks, either Windows Storage Spaces or Linux LVM2 needs to be used. On Linux, it's recommended to use XFS file system to format the disks. The LVM stripe size should be tested with a performance test. 128 KB stripe size is a good starting point. On Windows, the NTFS Allocation Unit Size (AUS) should be tested. 64 KB can be used as a starting value. 
 
 It's recommended to configure Automatic Database Expansion as described in the article [Configuring Automatic Database Space Expansion in SAP Adaptive Server Enterprise](https://blogs.sap.com/2014/07/09/configuring-automatic-database-space-expansion-in-sap-adaptive-server-enterprise/)  and [SAP support note #1815695](https://launchpad.support.sap.com/#/notes/1815695). 
 
diff --git a/articles/sap/workloads/dbms-guide-sqlserver.md b/articles/sap/workloads/dbms-guide-sqlserver.md
@@ -48,7 +48,7 @@ There's some SQL Server in IaaS specific information you should know before cont
 
 
 ## New M-series VMs and SQL Server
-Azure released a few new families of M-series SKUs under the family of Mv3. Some of the VM types in this family should't be used for SQL Server, including SQL Server 2022 without disabling SMT (Hyperthreading) in the Windows Server guest OS. Reason is the number of NUMA nodes presented into the Windows Server guest OS which with larger than 64 vCPUs is too large for SQL Server to accomodate. By disabling SMT in the Windows Server guest OS, the number of vCPUs is getting reduced. So, that the number of vCPUs is less than 64 in each NUMA node. The way how to disable SMT is described [here](https://learn.microsoft.com/sql/sql-server/compute-capacity-limits-by-edition-of-sql-server?view=sql-server-ver16#disable-smt-in-an-azure-virtual-machine). The specific VM types are:
+Azure released a few new families of M-series SKUs under the family of Mv3. Some of the VM types in this family should't be used for SQL Server, including SQL Server 2022 without disabling SMT (Hyperthreading) in the Windows Server guest OS. Reason is the number of NUMA nodes presented into the Windows Server guest OS which with larger than 64 vCPUs is too large for SQL Server to accommodate. By disabling SMT in the Windows Server guest OS, the number of vCPUs is getting reduced. So, that the number of vCPUs is less than 64 in each NUMA node. The way how to disable SMT is described [here](/sql/sql-server/compute-capacity-limits-by-edition-of-sql-server?view=sql-server-ver16&preserve-view=true#disable-smt-in-an-azure-virtual-machine). The specific VM types are:
 - M176(d)s_3_v3 - disable SMT or use M176bds_4_v3 or M176bds_4_v3 as alternative
 - M176(d)s_4_v3 - disable SMT or use M176bds_4_v3 as alternative
 - M624(d)s_12_v3 - disable SMT or use M416ms_v2 as alternative
diff --git a/articles/sap/workloads/get-started.md b/articles/sap/workloads/get-started.md
@@ -57,7 +57,7 @@ In the SAP workload documentation space, you can find the following areas:
 - November 19, 2024: Update parameter `enque/encni/set_so_keepalive` to uppercase, as the parameter is case sensitive. Updated in [SAP workloads on Azure: planning and deployment checklist](deployment-checklist.md),[HA for SAP NW on Azure VMs on RHEL multi-SID guide](./high-availability-guide-rhel-multi-sid.md), [Azure VMs high availability for SAP NW on RHEL with Azure NetApp Files](./high-availability-guide-rhel-netapp-files.md),[Azure VMs high availability for SAP NW on RHEL with NFS on Azure Files](./high-availability-guide-rhel-nfs-azure-files.md),[HA for SAP NW on Azure VMs on RHEL for SAP applications](./high-availability-guide-rhel.md),[Azure VMs high availability for SAP NetWeaver on SLES multi-SID guide](./high-availability-guide-suse-multi-sid.md), [Azure VMs high availability for SAP NW on SLES with NFS on Azure Files](./high-availability-guide-suse-netapp-files.md),[Azure VMs high availability for SAP NW on SLES with NFS on Azure Files](./high-availability-guide-suse-nfs-azure-files.md), [Azure VMs high availability for SAP NetWeaver on SLES for SAP Applications with simple mount and NFS](./high-availability-guide-suse-nfs-simple-mount.md),[Azure VMs high availability for SAP NetWeaver on SLES](./high-availability-guide-suse.md),[HA for SAP NetWeaver on Azure VMs on Windows with Azure NetApp Files(SMB)](./high-availability-guide-windows-netapp-files-smb.md),[SAP ASCS/SCS instance multi-SID high availability with Windows server failover clustering and Azure shared disk](./sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md),[SAP ASCS/SCS installation on Windows with file share](sap-high-availability-installation-wsfc-file-share.md),[SAP ASCS/ERS installation on Windows with shared disk](sap-high-availability-installation-wsfc-shared-disk.md).
 - November 5, 2024: Add missing step to start HANA [High availability of SAP HANA on Azure VMs on RHEL](./sap-hana-high-availability-rhel.md).
 - November 1, 2024: Adding HANA high-availability hook ChkSrv for [dying indexserver for RHEL based cluster setups](./sap-hana-high-availability-rhel.md#implement-sap-hana-system-replication-hooks).
-- October 29, 2024: some changes on disk caching and smaller updates in [Azure Virtual Machines Oracle DBMS deployment for SAP workload](./dbms-guide-oracle.md). Plus fixing some typoes in HANA storage configuration documents
+- October 29, 2024: some changes on disk caching and smaller updates in [Azure Virtual Machines Oracle DBMS deployment for SAP workload](./dbms-guide-oracle.md). Plus fixing some typos in HANA storage configuration documents
 - October 28, 2024: Added information on RedHat support and the configuration of Azure fence agents for VMs in the Azure Government cloud to the document [Set up Pacemaker on Red Hat Enterprise Linux in Azure](./high-availability-guide-rhel-pacemaker.md).
 - October 25, 2024: Adding documentation link to [SQL Server Azure Virtual Machines DBMS deployment for SAP NetWeaver](./dbms-guide-sqlserver.md) that describes how to disable SMT to be able to use some Mv3 SKUs where SQL Server would have a problem with too large NUMA nodes.
 - October 16, 2024: Included ordering constraints in [High availability of SAP HANA scale-up with Azure NetApp Files on RHEL](./sap-hana-high-availability-netapp-files-red-hat.md) to ensure SAP resources on a node stop before any of the NFS mounts.
diff --git a/articles/sap/workloads/hana-vm-premium-ssd-v2.md b/articles/sap/workloads/hana-vm-premium-ssd-v2.md
@@ -43,7 +43,7 @@ Not having Azure Write Accelerator support or support by other caches makes the
 ## Production recommended storage solution based on Azure premium storage
 
 > [!NOTE]
-> The configurations suggested below keep the HANA minimum KPIs, as listed in [SAP HANA Azure virtual machine storage configurations](./hana-vm-operations-storage.md) in mind. Our tests so far gave no indications that with the values listed, SAP HCMT tests would fail in throughput or latency. That stated, not all variations possible and combinations around stripe sets stretched across multiple disks or different stripe sizes were tested. Tests condcuted with striped volumes across multiple disks were done with the stripe sizes documented in [SAP HANA Azure virtual machine storage configurations](./hana-vm-operations-storage.md). 
+> The configurations suggested below keep the HANA minimum KPIs, as listed in [SAP HANA Azure virtual machine storage configurations](./hana-vm-operations-storage.md) in mind. Our tests so far gave no indications that with the values listed, SAP HCMT tests would fail in throughput or latency. That stated, not all variations possible and combinations around stripe sets stretched across multiple disks or different stripe sizes were tested. Tests conducted with striped volumes across multiple disks were done with the stripe sizes documented in [SAP HANA Azure virtual machine storage configurations](./hana-vm-operations-storage.md). 
 
 
 > [!NOTE]
diff --git a/articles/sap/workloads/high-availability-guide-rhel-ibm-db2-luw.md b/articles/sap/workloads/high-availability-guide-rhel-ibm-db2-luw.md
diff --git a/articles/sap/workloads/high-availability-zones.md b/articles/sap/workloads/high-availability-zones.md
diff --git a/articles/sap/workloads/proximity-placement-scenarios.md b/articles/sap/workloads/proximity-placement-scenarios.md
diff --git a/articles/sap/workloads/sap-hana-availability-overview.md b/articles/sap/workloads/sap-hana-availability-overview.md
diff --git a/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-shared-disk.md b/articles/sap/workloads/sap-high-availability-infrastructure-wsfc-shared-disk.md
diff --git a/articles/sap/workloads/sap-high-availability-installation-wsfc-shared-disk.md b/articles/sap/workloads/sap-high-availability-installation-wsfc-shared-disk.md
diff --git a/articles/sap/workloads/vm-extension-for-sap-standard.md b/articles/sap/workloads/vm-extension-for-sap-standard.md
