Merge pull request #309548 from habibaum/standard-updates

prmerger-automator[bot] · web-flow · commit f26e2f5e8bbb · 2025-12-15T10:00:12.000Z
Standard updates
diff --git a/articles/migrate/troubleshoot-changed-block-tracking-replication.md b/articles/migrate/troubleshoot-changed-block-tracking-replication.md
@@ -151,7 +151,7 @@ The component trying to replicate data to Azure is either down or not responding
 
     1. Fetch the Key Vault URI from the list of resources in the Resource Group corresponding to Azure Migrate Project.
 
-    1. Open PowerShell in the Azure Migrate appliance and run the following command:
+    1. Go to PowerShell in the Azure Migrate appliance and run the following command:
     ```
     _test-netconnection Key Vault URI -P 443_
     ```
@@ -238,7 +238,7 @@ The possible causes include:
 
     1. Fetch the Key Vault URI from the list of resources in the Resource Group corresponding to Azure Migrate Project.
 
-    1. Open PowerShell in the Azure Migrate appliance and run the following command:
+    1. Go to PowerShell in the Azure Migrate appliance and run the following command:
 
     ```
     _test-netconnection Key Vault URI -P 443_
diff --git a/articles/migrate/troubleshoot-network-connectivity.md b/articles/migrate/troubleshoot-network-connectivity.md
@@ -330,7 +330,7 @@ This error might occur if the export/import/download request was not initiated f
 
 **Option 1** _(recommended)_:
   
-To resolve this error, retry the import/export/download operation from a client residing in a virtual network that is connected to Azure over a private link. You can open the Azure portal in your on-premises network or your appliance VM and retry the operation.
+To resolve this error, retry the import/export/download operation from a client residing in a virtual network that is connected to Azure over a private link. You can go to the Azure portal in your on-premises network or your appliance VM and retry the operation.
 
 **Option 2**:
 
diff --git a/articles/migrate/troubleshoot-replication-vmware.md b/articles/migrate/troubleshoot-replication-vmware.md
@@ -70,7 +70,7 @@ You can increase the NFC buffer size beyond 32 MB to increase concurrency. The s
    ```
 4. Change the value of `HostBufferSizeInMB` to the value that you set in the ESXi host. 
 5. Save and exit. 
-6. Restart the Azure Migrate gateway service that is running on the appliance. Open PowerShell and execute the following:
+6. Restart the Azure Migrate gateway service that is running on the appliance. Go to PowerShell and execute the following:
    - net stop asrgwy (wait for the service to stop) 
    - net start asrgwy  
 
diff --git a/articles/migrate/tutorial-app-containerization-aspnet-app-service.md b/articles/migrate/tutorial-app-containerization-aspnet-app-service.md
@@ -143,7 +143,7 @@ If you just created a free Azure account, you're the owner of your subscription.
 1. Select **Sign in** to sign in to your Azure account.
 
    You need a device code to authenticate with Azure. Selecting **Sign in** should open a window that contains the device code. If the window doesn't appear, make sure you've disabled the pop-up blocker in the browser.
-2. Select **Copy code and Sign in** to copy the device code and open an Azure sign-in prompt in a new browser tab:
+2. Select **Copy code and Sign in** to copy the device code and go to an Azure sign-in prompt in a new browser tab:
 
     ![Screenshot that shows the Device code for Azure Sign in window.](./media/tutorial-containerize-apps-aks/login-modal.png)
 
diff --git a/articles/migrate/tutorial-app-containerization-aspnet-kubernetes.md b/articles/migrate/tutorial-app-containerization-aspnet-kubernetes.md
@@ -81,7 +81,7 @@ If you just created a free Azure account, you're the owner of your subscription.
 
 1. Select **Access control (IAM)**.
 
-1. Select **Add** > **Add role assignment** to open the **Add role assignment** page.
+1. Select **Add** > **Add role assignment** to go to the **Add role assignment** page.
 
 1. Assign the following role. For detailed steps, see [Assigning Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
 
diff --git a/articles/migrate/tutorial-app-containerization-java-kubernetes.md b/articles/migrate/tutorial-app-containerization-java-kubernetes.md
@@ -87,7 +87,7 @@ If you just created a free Azure account, you're the owner of your subscription.
 
 1. Select **Access control (IAM)**.
 
-1. Select **Add** > **Add role assignment** to open the **Add role assignment** page.
+1. Select **Add** > **Add role assignment** to go to the **Add role assignment** page.
 
 1. Assign the following role. For detailed steps, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
 
@@ -153,7 +153,7 @@ If you just created a free Azure account, you're the owner of your subscription.
 Select **Sign in** to log in to your Azure account.
 
 1. You'll need a device code to authenticate with Azure. Selecting on sign in will open a modal with the device code.
-2. Select **Copy code & sign in** to copy the device code and open an Azure sign in prompt in a new browser tab. If it doesn't appear, make sure you've disabled the pop-up blocker in the browser.
+2. Select **Copy code & sign in** to copy the device code and go to an Azure sign in prompt in a new browser tab. If it doesn't appear, make sure you've disabled the pop-up blocker in the browser.
 
     ![Modal showing device code.](./media/tutorial-containerize-apps-aks/login-modal.png)
 
@@ -290,4 +290,4 @@ To troubleshoot any issues with the tool, you can look at the log files on the W
 - Containerizing ASP.NET web apps and deploying them on Windows containers on AKS. [Learn more](./tutorial-app-containerization-aspnet-kubernetes.md)
 - Containerizing ASP.NET web apps and deploying them on Windows containers on Azure App Service. [Learn more](./tutorial-app-containerization-aspnet-app-service.md)
 - What are solutions for running Oracle WebLogic Server on the Azure Kubernetes Service? [Learn more](/azure/virtual-machines/workloads/oracle/weblogic-aks)
-- Open Liberty and WebSphere Liberty on AKS. [Learn more](/azure/developer/java/ee/websphere-family#open-liberty-and-websphere-liberty-on-aks)
+- Go to Liberty and WebSphere Liberty on AKS. [Learn more](/azure/developer/java/ee/websphere-family#open-liberty-and-websphere-liberty-on-aks)
diff --git a/articles/migrate/tutorial-discover-aws.md b/articles/migrate/tutorial-discover-aws.md
@@ -61,7 +61,7 @@ Set up an account that the appliance can use to access AWS instances.
 - Azure Migrate uses password authentication when discovering AWS instances. AWS instances don't support password authentication by default. Before you can discover instance, you need to enable password authentication.
     - For Windows servers, allow WinRM port 5985 (HTTP). This allows remote WMI calls.
     - For Linux servers:
-        1. Sign into each Linux  machine.
+        1. Sign into each Linux machine.
         2. Open the sshd_config file: vi /etc/ssh/sshd_config
         3. In the file, locate the **PasswordAuthentication** line, and change the value to **yes**.
         4. Save the file and close it. Restart the ssh service.
diff --git a/articles/migrate/tutorial-discover-gcp.md b/articles/migrate/tutorial-discover-gcp.md
@@ -190,7 +190,7 @@ In the configuration manager, select **Set up prerequisites**, and then complete
 
     1. For the appliance to run auto-update, paste the project key that you copied from the portal. If you don't have the key, go to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage existing appliances**. Select the appliance name you provided when you generated the project key, and then copy the key that's shown.
 	2. The appliance will verify the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server.
-    3. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure Login prompt in a new browser tab. Make sure you've disabled the pop-up blocker in the browser to see the prompt.
+    3. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and go to an Azure Login prompt in a new browser tab. Make sure you've disabled the pop-up blocker in the browser to see the prompt.
     
         :::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and sign in.":::
     4. In a new tab in your browser, paste the device code and sign in by using your Azure username and password. Signing in with a PIN isn't supported.
@@ -264,7 +264,7 @@ Select **Start discovery**, to kick off discovery of the successfully validated
 
 After discovery finishes, you can verify that the servers appear in the portal.
 
-1. Open the Azure Migrate dashboard.
+1. Go to the Azure Migrate dashboard.
 2. In **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment** page, select the icon that displays the count for **Discovered servers**.
 
 ## Next steps
diff --git a/articles/migrate/tutorial-discover-hyper-v.md b/articles/migrate/tutorial-discover-hyper-v.md
@@ -179,7 +179,7 @@ In the configuration manager, select **Set up prerequisites**, and then complete
 
 1. For the appliance to run auto-update, paste the project key that you copied from the portal. If you don't have the key, go to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage existing appliances**. Select the appliance name you provided when you generated the project key and then copy the key that's shown. 
 1. The appliance will verify the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server. 
-1. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure Login prompt in a new browser tab. Make sure you've disabled the pop-up blocker in the browser to see the prompt.
+1. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and go to Azure Login prompt in a new browser tab. Make sure you've disabled the pop-up blocker in the browser to see the prompt.
     
     :::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and log in.":::
 1. In a new tab in your browser, paste the device code and sign in by using your Azure username and password. Signing in with a PIN isn't supported.
diff --git a/articles/migrate/tutorial-discover-import.md b/articles/migrate/tutorial-discover-import.md
@@ -61,7 +61,7 @@ If you just created a free Azure account, you're the owner of your subscription.
 
 1. Select **Access control (IAM)**.
 
-1. Select **Add** > **Add role assignment** to open the **Add role assignment** page.
+1. Select **Add** > **Add role assignment** to go to the **Add role assignment** page.
 
 1. Assign the following role. For detailed steps, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
 
diff --git a/articles/migrate/tutorial-discover-physical.md b/articles/migrate/tutorial-discover-physical.md
@@ -291,7 +291,7 @@ Select **Start discovery** to begin discovering the validated servers. After dis
 ### Verify servers in the portal
 
 After discovery finishes, you can verify that the servers appear in the portal.
-1.	Open the Azure Migrate dashboard.
+1.	Go to the Azure Migrate dashboard.
 2.	In **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment** page, select the icon that displays the count for discovered servers.
 
 ## View License support status
diff --git a/articles/migrate/tutorial-discover-vmware.md b/articles/migrate/tutorial-discover-vmware.md
@@ -168,7 +168,7 @@ To set up the appliance for the first time:
 1. Select or enter the language, time zone, and password for the appliance.
 1. Open a browser on any computer that can connect to the appliance. Then, open the URL of the appliance configuration manager: `https://appliance name or IP address: 44368`.
 
-     Or you can open the configuration manager from the appliance server desktop by selecting the shortcut for the configuration manager.
+     Or you can go to the configuration manager from the appliance server desktop by selecting the shortcut for the configuration manager.
 1. Accept the license terms and read the third-party information.
 
 #### Set up prerequisites and register the appliance
@@ -186,7 +186,7 @@ In the configuration manager, select **Set up prerequisites**, and then complete
     :::image type="content" source="./media/tutorial-discover-vmware/prerequisites.png" alt-text="Screenshot that shows setting up the prerequisites in the appliance configuration manager.":::
 1. For the appliance to run auto-update, paste the project key that you copied from the portal. If you don't have the key, go to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage existing appliances**. Select the appliance name you provided when you generated the project key and then copy the key that's shown.
 1. The appliance will verify the key and start the auto-update service, which updates all the services on the appliance to their latest versions. When the auto-update has run, you can select **View appliance services** to see the status and versions of the services running on the appliance server.
-1. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and open an Azure sign in prompt in a new browser tab. Ensure you've disabled the pop-up blocker in the browser to see the prompt.
+1. To register the appliance, you need to select **Login**. In **Continue with Azure Login**, select **Copy code & Login** to copy the device code (you must have a device code to authenticate with Azure) and go to an Azure sign in prompt in a new browser tab. Ensure you've disabled the pop-up blocker in the browser to see the prompt.
 
     :::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Screenshot that shows where to copy the device code and sign in."::: 
 
@@ -294,7 +294,7 @@ To start vCenter Server discovery, select **Start discovery**. After the discove
 * Discovery of installed applications might take longer than 15 minutes. The duration depends on the number of discovered servers. For 500 servers, it takes approximately one hour for the discovered inventory to appear in the Azure Migrate project in the portal.
 * [Software inventory](how-to-discover-applications.md) identifies web server role existing on discovered servers. If a server is found to have web server role enabled, Azure Migrate will perform web apps discovery on the server. Web apps configuration data is updated once every 24 hours.
 * During software inventory, the added server credentials are iterated against servers and validated for agentless dependency analysis. When the discovery of servers is finished, in the portal, you can enable agentless dependency analysis on the servers. Only the servers on which validation succeeds can be selected to enable [agentless dependency analysis](how-to-create-group-machine-dependencies-agentless.md).
-* Along with software inventory, pending updates for Windows and Linux servers are gathered. No additional permissions are required for identifying pending updates. Software and pending updates metadata is processed further to generate [Insights](/azure/migrate/insights-overview?view=migrate), that provides security risks in the datacenter.
+* Along with software inventory, pending updates for Windows and Linux servers are gathered. No additional permissions are required for identifying pending updates. Software and pending updates metadata is processed further to generate [Insights](/azure/migrate/insights-overview), that provides security risks in the datacenter.
 * Web apps and SQL Server instances and databases data begin to appear in the portal within 24 hours after you start discovery.
 * By default, Azure Migrate uses the most secure way of connecting to SQL instances that is, Azure Migrate encrypts communication between the Azure Migrate appliance and the source SQL Server instances by setting the TrustServerCertificate property to `true`. Additionally, the transport layer uses TLS to encrypt the channel and bypass the certificate chain to validate trust. Hence, the appliance server must be set up to trust the certificate's root authority. However, you can modify the connection settings, by selecting **Edit SQL Server connection properties** on the appliance. [Learn more](/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine) to understand what to choose.
 
