fixed blocking and non-blocking issues

Author: SGSneha

articles/migrate/deploy-appliance-script-government.md

@@ -29,7 +29,7 @@ You can use the script to deploy the Azure Migrate appliance on an existing phys
 - The server that will act as the appliance must be running Windows Server 2016 and meet other requirements for [VMware](migrate-appliance.md#appliance---vmware), [Hyper-V](migrate-appliance.md#appliance---hyper-v), and [physical servers](migrate-appliance.md#appliance---physical).
 - If you run the script on a server with Azure Migrate appliance already set up, you can choose to clean up the existing configuration and set up a fresh appliance of the desired configuration. When you execute the script, you will get a notification as shown below:
 
-    :::image type="content" source="./media/deploy-appliance-script/script-reconfigure-appliance.png" alt-text="Screenshot that shows how to reconfigure an appliance":::
+    :::image type="content" source="./media/deploy-appliance-script/script-reconfigure-appliance.png" alt-text="Screenshot that shows how to reconfigure an appliance.":::
 
 ## Set up the appliance for VMware
 
@@ -75,7 +75,7 @@ Check that the zipped file is secure, before you deploy it.
 
 5. Select from the scenario, cloud and connectivity options to deploy an appliance with the desired configuration. For instance, the selection shown below sets up an appliance to discover, assess and migrate **servers running in your VMware environment** to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure Government cloud**.
 
-    :::image type="content" source="./media/deploy-appliance-script-government/script-vmware-gov.png" alt-text="Screenshot that shows how to set up appliance with desired configuration for Vmware":::
+    :::image type="content" source="./media/deploy-appliance-script-government/script-vmware-gov-inline.png" alt-text="Screenshot that shows how to set up appliance with desired configuration for Vmware." lightbox="./media/deploy-appliance-script-government/script-vmware-gov-expanded.png":::
 
 6. The installer script does the following:
 
@@ -140,7 +140,7 @@ Check that the zipped file is secure, before you deploy it.
 
 5. Select from the scenario, cloud and connectivity options to deploy an appliance with the desired configuration. For instance, the selection shown below sets up an appliance to discover and assess **servers running in your Hyper-V environment** to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure Government cloud**.
 
-    :::image type="content" source="./media/deploy-appliance-script-government/script-hyperv-gov.png" alt-text="Screenshot that shows how to set up appliance with desired configuration for Hyper-V":::
+    :::image type="content" source="./media/deploy-appliance-script-government/script-hyperv-gov-inline.png" alt-text="Screenshot that shows how to set up appliance with desired configuration for Hyper-V." lightbox="./media/deploy-appliance-script-government/script-hyperv-gov-expanded.png":::
 
 6. The installer script does the following:
 
@@ -204,7 +204,7 @@ Check that the zipped file is secure, before you deploy it.
 
 5. Select from the scenario, cloud and connectivity options to deploy an appliance with the desired configuration. For instance, the selection shown below sets up an appliance to discover and assess **physical servers** _(or servers running on other clouds like AWS, GCP, Xen etc.)_ to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure Government cloud**.
 
-    :::image type="content" source="./media/deploy-appliance-script-government/script-physical-gov.png" alt-text="Screenshot that shows how to set up appliance with desired configuration for Physical servers":::
+    :::image type="content" source="./media/deploy-appliance-script-government/script-physical-gov-inline.png" alt-text="Screenshot that shows how to set up appliance with desired configuration for Physical servers." lightbox="./media/deploy-appliance-script-government/script-physical-gov-expanded.png":::
 
 6. The installer script does the following:
 

articles/migrate/deploy-appliance-script.md

@@ -74,15 +74,15 @@ Check that the zipped file is secure, before you deploy it.
 
 5. Select from the scenario, cloud and connectivity options to deploy an appliance with the desired configuration. For instance, the selection shown below sets up an appliance to discover, assess and migrate **servers running in your VMware environment** to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure public cloud**.
 
-    :::image type="content" source="./media/deploy-appliance-script/script-vmware-default.png" alt-text="Screenshot that shows how to set up Vmware appliance with desired configuration":::
+    :::image type="content" source="./media/deploy-appliance-script/script-vmware-default-inline.png" alt-text="Screenshot that shows how to set up Vmware appliance with desired configuration." lightbox="./media/deploy-appliance-script/script-vmware-default-expanded.png":::
 
 6. The installer script does the following:
 
-- Installs agents and a web application.
-- Install Windows roles, including Windows Activation Service, IIS, and PowerShell ISE.
-- Download and installs an IIS rewritable module.
-- Updates a registry key (HKLM) with persistent setting details for Azure Migrate.
-- Creates the following files under the path:
+ - Installs agents and a web application.
+ - Install Windows roles, including Windows Activation Service, IIS, and PowerShell ISE.
+ - Download and installs an IIS rewritable module.
+ - Updates a registry key (HKLM) with persistent setting details for Azure Migrate.
+ - Creates the following files under the path:
     - **Config Files**: %Programdata%\Microsoft Azure\Config
     - **Log Files**: %Programdata%\Microsoft Azure\Logs
 
@@ -131,7 +131,7 @@ Check that the zipped file is secure, before you deploy it.
 
 5. Select from the scenario, cloud and connectivity options to deploy an appliance with the desired configuration. For instance, the selection shown below sets up an appliance to discover and assess **servers running in your Hyper-V environment** to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure public cloud**.
 
-    :::image type="content" source="./media/deploy-appliance-script/script-hyperv-default.png" alt-text="Screenshot that shows how to set up Hyper-V appliance with desired configuration":::
+    :::image type="content" source="./media/deploy-appliance-script/script-hyperv-default-inline.png" alt-text="Screenshot that shows how to set up Hyper-V appliance with desired configuration." lightbox="./media/deploy-appliance-script/script-hyperv-default-expanded.png":::
 
 6. The installer script does the following:
 

articles/migrate/how-to-scale-out-for-migration.md

@@ -80,7 +80,7 @@ In **Download Azure Migrate appliance**, click  **Download**. You need to downlo
 
 5. Select from the scenario, cloud, configuration and connectivity options to deploy the desired appliance. For instance, the selection shown below sets up a **scale-out appliance** to initiate concurrent replications on servers running in your VMware environment to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure public cloud**.
 
-    :::image type="content" source="./media/how-to-scale-out-for-migration/script-vmware-scaleout.png" alt-text="Screenshot that shows how to set up scale-out appliance":::
+    :::image type="content" source="./media/how-to-scale-out-for-migration/script-vmware-scaleout-inline.png" alt-text="Screenshot that shows how to set up scale-out appliance." lightbox="./media/how-to-scale-out-for-migration/script-vmware-scaleout-expanded.png":::
 
 6. The installer script does the following:
 
@@ -121,6 +121,7 @@ Before you begin ensure that the [these Azure endpoints](migrate-appliance.md#pu
 
 1. Paste the **Azure Migrate project key** copied from the portal. If you do not have the key, go to **Server Assessment> Discover> Manage existing appliances**, select the primary appliance name, find the scale-out appliance associated with it and copy the corresponding key.
 1. You will need a device code to authenticate with Azure. Clicking on **Login** will open a modal with the device code as shown below.
+
 :::image type="content" source="./media/tutorial-discover-vmware/device-code.png" alt-text="Modal showing the device code":::
 
 1. Click on **Copy code & Login** to copy the device code and open an Azure Login prompt in a new browser tab. If it doesn't appear, make sure you've disabled the pop-up blocker in the browser.

articles/migrate/how-to-set-up-appliance-physical.md

@@ -75,7 +75,7 @@ Check that the zipped file is secure, before you deploy it.
 
 5. Select from the scenario, cloud and connectivity options to deploy an appliance with the desired configuration. For instance, the selection shown below sets up an appliance to discover and assess **physical servers** _(or servers running on other clouds like AWS, GCP, Xen etc.)_ to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure public cloud**.
 
-    :::image type="content" source="./media/tutorial-discover-physical/script-physical-default.png" alt-text="Screenshot that shows how to set up appliance with desired configuration":::
+    :::image type="content" source="./media/tutorial-discover-physical/script-physical-default.png" alt-text="Screenshot that shows how to set up appliance with desired configuration.":::
 
 6. The installer script does the following:
 

articles/migrate/how-to-use-azure-migrate-with-private-endpoints.md

@@ -131,7 +131,7 @@ Make sure the server meets the [hardware requirements](./migrate-appliance.md) f
 
 5. Select from the scenario, cloud and connectivity options to deploy an appliance with the desired configuration. For instance, the selection shown below sets up an appliance to discover and assess **servers running in your VMware environment** to an Azure Migrate project with **private endpoint connectivity** on **Azure public cloud**.
 
-    :::image type="content" source="./media/how-to-use-azure-migrate-with-private-endpoints/script-vmware-private.png" alt-text="Screenshot that shows how to set up appliance with desired configuration for private endpoint":::
+    :::image type="content" source="./media/how-to-use-azure-migrate-with-private-endpoints/script-vmware-private-inline.png" alt-text="Screenshot that shows how to set up appliance with desired configuration for private endpoint." lightbox="./media/how-to-use-azure-migrate-with-private-endpoints/script-vmware-private-expanded.png":::
 
 After the script has executed successfully, the appliance configuration manager will be launched automatically.
 

articles/migrate/media/deploy-appliance-script-government/script-hyperv-gov.png renamed to articles/migrate/media/deploy-appliance-script-government/script-hyperv-gov-expanded.png

@@ -55,7 +55,7 @@ Set up an account that the appliance can use to access the physical servers.
     1. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAppliance.
     1. Create a registry key ‘isSudo’ with DWORD value of 1.
 
-    :::image type="content" source="./media/tutorial-discover-physical/issudo-reg-key.png" alt-text="Screenshot that shows how to enable sudo support":::
+    :::image type="content" source="./media/tutorial-discover-physical/issudo-reg-key.png" alt-text="Screenshot that shows how to enable sudo support.":::
 
 - To discover the configuration and performance metadata from target server, you need to enable sudo access for the commands listed [here](migrate-appliance.md#linux-server-metadata). Make sure that you have enabled 'NOPASSWD' for the account to run the required commands without prompting for a password every time sudo command is invoked.
 - The following Linux OS distributions are supported for discovery by Azure Migrate using an account with sudo access:

articles/migrate/media/deploy-appliance-script-government/script-hyperv-gov-inline.png

@@ -30,7 +30,7 @@ Learn more about [assessments](concepts-assessment-calculation.md).
 
 VMware | Details
 --- | ---
-**vCenter Server** | Servers that you want to discover and assess must be managed by vCenter Server version 7.0, 6.7, 6.5, 6.0, or 5.5.<br /><br /> Discovering servers by providing ESXi host details in the appliance currently isn't supported. <br /><br /> IPv6 addresses are not supported for vCenter Server (for discovery and assesment of servers) and ESXi hosts (for replication of servers).
+**vCenter Server** | Servers that you want to discover and assess must be managed by vCenter Server version 7.0, 6.7, 6.5, 6.0, or 5.5.<br /><br /> Discovering servers by providing ESXi host details in the appliance currently isn't supported. <br /><br /> IPv6 addresses are not supported for vCenter Server (for discovery and assessment of servers) and ESXi hosts (for replication of servers).
 **Permissions** | The Azure Migrate: Discovery and assessment tool requires a vCenter Server read-only account.<br /><br /> If you want to use the tool for software inventory and agentless dependency analysis, the account must have privileges for guest operations on VMware VMs.
 
 ## Server requirements

articles/migrate/media/deploy-appliance-script-government/script-physical-gov.png renamed to articles/migrate/media/deploy-appliance-script-government/script-physical-gov-expanded.png

@@ -41,7 +41,7 @@ You are getting an error in the connectivity check on the appliance.
 **Remediation**
 
 1. Ensure that you can connect to the required [URLs](/azure/migrate/migrate-appliance#url-access) from the appliance
-1. Check if there is a proxy or firewall blocking access to these URLs. If you are required to create an allow list, make sure that you include all of the URLs.
+1. Check if there is a proxy or firewall blocking access to these URLs. If you are required to create an allowlist, make sure that you include all of the URLs.
 1. If there is a proxy server configured on-premises, make sure that you provide the proxy details correctly by selecting **Setup proxy** in the same step. Make sure that you provide the authorization credentials if the proxy needs them.
 1. Ensure that the server has not been previously used to set up the [replication appliance](/azure/migrate/migrate-replication-appliance) or that you have the mobility service agent installed on the server.
 
@@ -60,8 +60,8 @@ You are getting an error in the connectivity check on the appliance for aka.ms U
 
  If you have enabled the appliance for **private endpoint connectivity**, and don't want to allow access to this URL over internet, you can [disable auto-update](/azure/migrate/migrate-appliance#turn-off-auto-update), as the aka.ms link is required for this service.
 
->Note
->If you disable auto-update service, the services running on the appliance will not get the latest updates automatically. To get around this, [update the appliance services manually](/azure/migrate/migrate-appliance#manually-update-an-older-version).
+ >[!Note]
+ >If you disable auto-update service, the services running on the appliance will not get the latest updates automatically. To get around this, [update the appliance services manually](/azure/migrate/migrate-appliance#manually-update-an-older-version).
 
 ## Auto Update check failing during 'Set up prerequisites'
 
@@ -71,7 +71,7 @@ You are getting an error in the auto update check on the appliance.
 
 **Remediation**
 
-1. Make sure that you created an allow list for the [required URLs](/azure/migrate/migrate-appliance#url-access) and that no proxy or firewall setting is blocking them.
+1. Make sure that you created an allowlist for the [required URLs](/azure/migrate/migrate-appliance#url-access) and that no proxy or firewall setting is blocking them.
 1. If the update of any appliance component is failing, either rerun the prerequisites or [manually update the appliance services](/azure/migrate/migrate-appliance#manually-update-an-older-version).
 
 ## Time sync check failing during 'Set up prerequisites'
@@ -138,7 +138,7 @@ This usually happens when the Azure user account that was used to register the a
 **Remediation**
 
 1. Ensure that the currently logged in user account on the appliance has the required permissions on the Key Vault (mentioned in the error message). The user account needs permissions as mentioned [here](/azure/migrate/tutorial-discover-vmware#prepare-an-azure-user-account).
-2. Go to the Key Vault and ensure that your user account has an access policy with all the _Key, Secret and Certificate_ permissions assigned under Key vault Access Policy. Learn more [https://docs.microsoft.com/en-us/azure/key-vault/general/assign-access-policy-portal]
+2. Go to the Key Vault and ensure that your user account has an access policy with all the _Key, Secret and Certificate_ permissions assigned under Key vault Access Policy. Learn more [/azure/key-vault/general/assign-access-policy-portal]
 3. If you have enabled the appliance for **private endpoint connectivity**, ensure that the appliance is either hosted in the same VNet where the Key Vault has been created or it is connected to the Azure VNet (where Key Vault has been created) over a private link. Make sure that the Key Vault private link is resolvable from the appliance. Go to Azure Migrate: Discovery and assessment> Properties to find the details of private endpoints for resources like the Key Vault created during the Azure Migrate key creation. [Learn more](https://go.microsoft.com/fwlink/?linkid=2162447)
 4. If you have the required permissions and connectivity, re-try the registration on the appliance after some time.
 

articles/migrate/media/deploy-appliance-script-government/script-physical-gov-inline.png

@@ -95,7 +95,7 @@ Set up an account that the appliance can use to access the physical servers.
     1. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAppliance.
     1. Create a registry key ‘isSudo’ with DWORD value of 1.
 
-    :::image type="content" source="./media/tutorial-discover-physical/issudo-reg-key.png" alt-text="Screenshot that shows how to enable sudo support":::
+    :::image type="content" source="./media/tutorial-discover-physical/issudo-reg-key.png" alt-text="Screenshot that shows how to enable sudo support.":::
 
 - To discover the configuration and performance metadata from target server, you need to enable sudo access for the commands listed [here](migrate-appliance.md#linux-server-metadata). Make sure that you have enabled 'NOPASSWD' for the account to run the required commands without prompting for a password every time sudo command is invoked.
 - The following Linux OS distributions are supported for discovery by Azure Migrate using an account with sudo access:
@@ -160,7 +160,7 @@ To set up the appliance you:
 1. After the successful creation of the Azure resources, a **project key** is generated.
 1. Copy the key as you will need it to complete the registration of the appliance during its configuration.
 
-   ![Selections for Generate Key](./media/tutorial-assess-physical/generate-key-physical.png)
+  [ ![Selections for Generate Key.](./media/tutorial-assess-physical/generate-key-physical-inline.png)](./media/tutorial-assess-physical/generate-key-physical-expanded.png#lightbox)
 
 ### 2. Download the installer script
 
@@ -196,15 +196,15 @@ Check that the zipped file is secure, before you deploy it.
 
 5. Select from the scenario, cloud and connectivity options to deploy an appliance with the desired configuration. For instance, the selection shown below sets up an appliance to discover and assess **physical servers** _(or servers running on other clouds like AWS, GCP, Xen etc.)_ to an Azure Migrate project with **default _(public endpoint)_ connectivity** on **Azure public cloud**.
 
-    :::image type="content" source="./media/tutorial-discover-physical/script-physical-default.png" alt-text="Screenshot that shows how to set up appliance with desired configuration":::
+    :::image type="content" source="./media/tutorial-discover-physical/script-physical-default-inline.png" alt-text="Screenshot that shows how to set up appliance with desired configuration" lightbox="./media/tutorial-discover-physical/script-physical-default-expanded.png":::
 
 6. The installer script does the following:
 
-- Installs agents and a web application.
-- Install Windows roles, including Windows Activation Service, IIS, and PowerShell ISE.
-- Download and installs an IIS rewritable module.
-- Updates a registry key (HKLM) with persistent setting details for Azure Migrate.
-- Creates the following files under the path:
+ - Installs agents and a web application.
+ - Install Windows roles, including Windows Activation Service, IIS, and PowerShell ISE.
+ - Download and installs an IIS rewritable module.
+ - Updates a registry key (HKLM) with persistent setting details for Azure Migrate.
+ - Creates the following files under the path:
     - **Config Files**: %Programdata%\Microsoft Azure\Config
     - **Log Files**: %Programdata%\Microsoft Azure\Logs