changes

Author: v-thepet

articles/devtest-labs/devtest-lab-shared-ip.md

@@ -7,35 +7,37 @@ ms.date: 11/08/2021
 
 # Understand shared IP addresses in Azure DevTest Labs
 
-Azure DevTest Labs virtual machines (VMs) can share the same public IP address, to minimize the number of public IPs you need to access lab VMs.  This article describes how shared IPs work and how to configure shared IP options.
+Azure DevTest Labs virtual machines (VMs) can share a public IP address, to minimize the number of public IPs you need to access lab VMs.  This article describes how shared IPs work, and how to configure shared IP addresses.
 
 ## Shared IP settings
 
-Azure DevTest Labs creates labs in virtual networks that can have one or more subnets. The default subnet has **Enable shared public IP** set to **Yes**.  This configuration creates one public IP address for the entire subnet. For more information about configuring virtual networks and subnets, see [Configure a virtual network in Azure DevTest Labs](devtest-lab-configure-vnet.md).
+Azure DevTest Labs creates labs in virtual networks, which can have one or more subnets. The default subnet has **Enable shared public IP** set to **Yes**.  This configuration creates one public IP address for the entire subnet. Any VMs in this subnet default to using a shared IP.
 
-![New lab subnet](media/devtest-lab-shared-ip/lab-subnet.png)
+For more information about configuring virtual networks and subnets, see [Configure a virtual network in Azure DevTest Labs](devtest-lab-configure-vnet.md).
+
+![Screenshot that shows the Shared I P setting on the Lab Subnet page.](media/devtest-lab-shared-ip/lab-subnet.png)
 
 For existing labs, you can check or set this option by selecting **Configuration and policies** in the lab's left navigation, and then selecting **Virtual networks** under **External resources**. Select a virtual network from the list to see the shared IP settings for its subnets.
 
 To change the setting, select a subnet from the list, and then change **Enable shared public IP** to **Yes** or **No**.
 
-Any VMs you create in this subnet default to using a shared IP.  When creating the VM, you can access this setting on the **Advanced settings** page next to **IP address**.
+When creating a VM, you can access this setting on the **Advanced settings** page next to **IP address**.
 
-![New VM](media/devtest-lab-shared-ip/new-vm.png)
+![Screenshot that shows the Shared I P setting in Advanced Settings when creating a new V M.](media/devtest-lab-shared-ip/new-vm.png)
 
 - **Shared:** All VMs you create as **Shared** go into the same resource group. The resource group has one assigned IP address that all VMs in the resource group use.
 - **Public:** Every public VM has its own IP address and resource group.
 - **Private:** Every private VM uses a private IP address. You can't connect to these VMs from the internet by using Remote Desktop protocol (RDP).
 
-When you add a VM with shared IP to a subnet, DevTest Labs automatically adds the VM to a load balancer and assigns the VM a TCP port number on the public IP address. The port number forwards to the RDP port on the VM.
+When you add a VM with shared IP to a subnet, DevTest Labs automatically adds the VM to a load balancer and assigns the VM a TCP port number on the public IP address. The port number forwards to the secure shell (SSH) port on the VM.
 
 ## Use a shared IP
 
-- **Linux users:** Secure shell (SSH) connect to the VM by using the IP address or fully qualified domain name, followed by a colon, followed by the port number. For example, the following screenshot shows an RDP connection address of `mydevtestlab597975021002.eastus.cloudapp.azure.com:50661`.
+- **Windows users:** Select the **Connect** button on the VM **Overview** page to download a pre-configured RDP file and access the VM.
 
-  ![VM example](media/devtest-lab-shared-ip/vm-info.png)
+- **Linux users:** Secure shell (SSH) connects to the VM by using the IP address or fully qualified domain name, followed by a colon, followed by the port number. For example, the following screenshot shows an SSH connection address of `contosolab21000000000000.westus3.cloudapp.azure.com:65013`.
 
-- **Windows users:** Select the **Connect** button on the Azure portal to download a pre-configured RDP file and access the VM.
+  ![Screenshot that shows the R D P and S S H connection options on a VM Overview page.](media/devtest-lab-shared-ip/vm-info.png)
 
 ## Next steps
 

articles/devtest-labs/import-virtual-machines-from-another-lab.md

@@ -20,27 +20,25 @@ Here are some scenarios where you might need to import VMs from one lab into ano
 
 The import process imports the VMs from the source lab into the destination lab. You can optionally rename the VM in the process. The import process includes all dependencies like disks, schedules, and network settings.
 
-The process is a copy operation, not a move operation, and can take a long time. The import time depends on the following factors:
+The process is a copy operation, not a move operation, and can take a long time. The import time partly depends on the following factors:
 
 - Number and size of the disks attached to the source machine
 - Distance between the source and destination regions
 
-When the process finishes, the source VM is shut down, and the new VM is running in the destination lab.
+When the import finishes, the process shuts down the source VM and starts the new VM running in the destination lab.
 
-There are several requirements and constraints for importing VMs from one lab to another lab:
+There are several requirements and constraints for importing VMs from one lab to another:
 
 - You can import VMs across subscriptions and across regions, but both subscriptions must be associated with the same Azure Active Directory tenant.
 - VMs can't be in a claimable state in the source lab.
 - You must be the owner of the VM in the source lab, and the owner of the destination lab.
-- Currently, this feature is supported only through Powershell and REST API.
+- Currently, this feature is supported only through PowerShell and REST API.
 
-## Use PowerShell
+## Use PowerShell to import one or all lab VMs
 
 Download and run [ImportVirtualMachines.ps1](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/Scripts/ImportVirtualMachines). You can use the script to import a single VM or all VMs from the source lab into the destination lab.
 
-### Use PowerShell to import a single VM or all lab VMs
-
-Executing this PowerShell script requires identifying the source VM and the destination lab, and optionally supplying a new name to use for the destination VM.
+To run this PowerShell script, identify the source and destination subscriptions and labs, and the source VM. Optionally, supply a new name for the destination VM.
 
 ```powershell
 ./ImportVirtualMachines.ps1 -SourceSubscriptionId "<ID of the subscription that contains the source lab>"`
@@ -50,13 +48,13 @@ Executing this PowerShell script requires identifying the source VM and the dest
                             -DestinationDevTestLabName "<Name of the destination lab>"`
                             -DestinationVirtualMachineName "<Optional: specify a new name for the imported VM in the destination lab>"
 ```
-If you don't specify a the source VM, the script automatically imports all VMs in the source lab.
+If you don't specify a source VM, the script automatically imports all VMs in the source lab.
 
 ## Use HTTP REST to import a VM
 
 The REST call is simple. You provide the information to identify the source and destination resources. The operation takes place on the destination lab resource.
 
-```REST
+```rest-api
 POST https://management.azure.com/subscriptions/<DestinationSubscriptionID>/resourceGroups/<DestinationResourceGroup>/providers/Microsoft.DevTestLab/labs/<DestinationLab>/ImportVirtualMachine?api-version=2017-04-26-preview
 {
    sourceVirtualMachineResourceId: "/subscriptions/<SourceSubscriptionID>/resourcegroups/<SourceResourceGroup>/providers/microsoft.devtestlab/labs/<SourceLab>/virtualmachines/<NameofVMTobeImported>",