Merge pull request #291993 from MicrosoftDocs/main

12/16 11:00 AM IST Publish

Author: PhilKang0704

articles/migrate/vmware/tutorial-migrate-vmware-agent.md

@@ -1,9 +1,8 @@
 ---
 title: Migrate VMware vSphere VMs with agent-based the Migration and modernization tool
 description: Learn how to run an agent-based migration of VMware vSphere VMs with Azure Migrate.
-author: vijain
-ms.author: vijain
-ms.manager: kmadnani
+author: piyushdhore-microsoft 
+ms.author: piyushdhore
 ms.topic: tutorial
 ms.service: azure-migrate
 ms.date: 09/26/2024
@@ -70,9 +69,6 @@ Assign the Virtual Machine Contributor role to the account, so that you have per
 
 If you are following the least privilege principle, assign the **Application Developer** Microsoft Entra role to the user registering the Replication Appliance. Follow the [Assign administrator and non-administrator roles to users with Microsoft Entra ID](../../active-directory/fundamentals/active-directory-users-assign-role-azure-portal.md) guide to do so.
 
-> [!IMPORTANT]
-> If the user registering the Replication Appliance is a Microsoft Entra Global Administrator, that user already has the required permissions.
-
 ### Set up an Azure network
 
 [Set up an Azure network](/azure/virtual-network/manage-virtual-network). On-premises machines are replicated to Azure managed disks. When you fail over to Azure for migration, Azure VMs are created from these managed disks, and joined to the Azure network you set up.

articles/operator-nexus/howto-configure-network-fabric.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
 
 ```
 

articles/sap/automation/configure-devops.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"
 
 ```

articles/sap/automation/integration-azure-monitor-sap.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. 

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 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. 

articles/sap/center-sap-solutions/quickstart-create-high-availability-namecustom.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).

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).

articles/sap/center-sap-solutions/quickstart-install-high-availability-namecustom-cli.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

articles/sap/center-sap-solutions/soft-stop-sap-and-hana-database.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