Merge pull request #179077 from v-thepet/dtl4

Refresh Shared IP and Import VMs

Author: GitHubber17

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

@@ -1,41 +1,45 @@
 ---
 title: Understand shared IP addresses
-description: Learn how Azure DevTest Labs uses shared IP addresses to minimize the public IP addresses required to access your lab VMs.
+description: Learn how Azure DevTest Labs uses shared IP addresses to minimize the public IP addresses you need to access your lab VMs.
 ms.topic: how-to
-ms.date: 06/26/2020
+ms.date: 11/08/2021
 ---
 
 # Understand shared IP addresses in Azure DevTest Labs
 
-Azure DevTest Labs lets lab VMs share the same public IP address to minimize the number of public IP addresses required to access your individual lab VMs.  This article describes how shared IPs work and their related configuration 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 setting
+## Shared IP settings
 
-When you create a lab, it's created in a subnet of a virtual network.  By default, this subnet is created with **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).
+You create a DevTest Labs lab in a virtual network, 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 the 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).
 
-For existing labs, you can enable this option by selecting **Configuration and policies > Virtual Networks**. Then, select a virtual network from the list and choose **ENABLE SHARED PUBLIC IP** for a selected subnet. You can also disable this option in any lab if you don't want to share a public IP address across lab VMs.
+![Screenshot that shows the Shared I P setting on the Lab Subnet page.](media/devtest-lab-shared-ip/lab-subnet.png)
 
-Any VMs created in this lab default to using a shared IP.  When creating the VM, this setting can be observed in the **Advanced settings** page under **IP address configuration**.
+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.
 
-![New VM](media/devtest-lab-shared-ip/new-vm.png)
+To change the setting, select a subnet from the list, and then change **Enable shared public IP** to **Yes** or **No**.
 
-- **Shared:** All VMs created as **Shared** are placed into one resource group (RG). A single IP address is assigned for that RG and all VMs in the RG will use that IP address.
-- **Public:** Every VM you create has its own IP address and is created in its own resource group.
-- **Private:** Every VM you create uses a private IP address. You can't connect to this VM directly from the internet with Remote Desktop.
+When creating a VM, you can access this setting on the **Advanced settings** page next to **IP address**.
 
-Whenever a VM with shared IP enabled is added to the subnet, DevTest Labs automatically adds the VM to a load balancer and assigns a TCP port number on the public IP address, forwarding to the RDP port on the VM.  
+![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)
 
-## Using the shared IP
+- **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).
 
-- **Linux users:** SSH to the VM by using the IP address or fully qualified domain name, followed by a colon, followed by the port. For example, in the image below, the RDP address to connect to the VM is `mydevtestlab597975021002.eastus.cloudapp.azure.com:50661`.
+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.
 
-  ![VM example](media/devtest-lab-shared-ip/vm-info.png)
+## Use a shared IP
 
-- **Windows users:** Select the **Connect** button on the Azure portal to download a pre-configured RDP file and access the VM.
+- **Windows users:** Select the **Connect** button on the VM **Overview** page to download a pre-configured RDP file and access the VM.
+
+- **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`.
+
+  ![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
 
-* [Define lab policies in Azure DevTest Labs](devtest-lab-set-lab-policy.md)
-* [Configure a virtual network in Azure DevTest Labs](devtest-lab-configure-vnet.md)
+- [Define lab policies in Azure DevTest Labs](devtest-lab-set-lab-policy.md)
+- [Configure a virtual network in Azure DevTest Labs](devtest-lab-configure-vnet.md)

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

@@ -1,66 +1,60 @@
 ---
 title: Import virtual machines from another lab
-description: This article describes how to import virtual machines from another lab into the current lab in Azure DevTest Labs.
+description: Learn how to import virtual machines from one lab to another in Azure DevTest Labs.
 ms.topic: how-to
-ms.date: 06/26/2020
+ms.date: 11/08/2021
 ---
 
-# Import virtual machines from another lab in Azure DevTest Labs
-This article provides information about how to import virtual machines from another lab into your lab.
+# Import virtual machines from one lab to another
+
+This article discusses and describes how to import virtual machines (VMs) from one DevTest Labs lab to another lab.
 
 ## Scenarios
-Here are some scenarios where you need to import VMs from one lab into another lab:
+Here are some scenarios where you might need to import VMs from one lab into another lab:
 
-- An individual on the team is moving to another group within the enterprise and wants to take the developer desktop to the new team’s DevTest Labs.
-- The group has hit a [subscription-level quota](../azure-resource-manager/management/azure-subscription-service-limits.md) and wants to split up the teams into a few subscriptions
-- The company is moving to Express Route (or some other new networking topology) and the team wants to move the Virtual Machines to use this new infrastructure
+- An individual is moving from one group to another and wants to take their developer desktop to the new team's lab.
+- The group has hit a [subscription-level quota](../azure-resource-manager/management/azure-subscription-service-limits.md) and wants to split up the teams into more than one Azure subscription.
+- The company is moving to Azure ExpressRoute or some other new networking topology, and the team wants to move the VMs to use the new infrastructure.
 
-## Solution and constraints
-This feature enables you to import VMs in one lab (source) into another lab (destination). You can optionally give a new name for the destination VM in the process. The import process includes all the dependencies like disks, schedules, network settings, and so on.
+## Requirements and constraints
 
-The process does take some time and is impacted by the following factors:
+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.
 
-- Number/size of the disks that are attached to the source machine (since it’s a copy operation and not a move operation)
-- Distance to the destination (For example, East US region to Southeast Asia).
+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:
 
-Once the process is complete, the source Virtual Machine remains shutdown and the new one is running in the destination lab.
+- Number and size of the disks attached to the source machine
+- Distance between the source and destination regions
 
-There are two key constraints to be aware of when planning to import VMs from one lab in to another lab:
+When the import finishes, the process shuts down the source VM and starts the new VM running in the destination lab.
 
-- Virtual Machine imports across subscriptions and across regions are supported, but the subscriptions must be associated to the same Azure Active Directory tenant.
-- Virtual Machines must not be in a claimable state in the source lab.
-- You're the owner of the VM in the source lab and owner of the lab in the destination lab.
-- Currently, this feature is supported only through Powershell and REST API.
+There are several requirements and constraints for importing VMs from one lab to another:
 
-## Use PowerShell
-Download ImportVirtualMachines.ps1 file from the [GitHub](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 in the source lab into the destination lab.
+- 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.
 
-### Use PowerShell to import a single VM
-Executing this powershell script requires identifying the source VM and the destination lab, and optionally supplying a new name to use for the destination machine:
+## Use PowerShell to import one or all lab VMs
 
-```powershell
-./ImportVirtualMachines.ps1 -SourceSubscriptionId "<ID of the subscription that contains the source lab>" `
-                            -SourceDevTestLabName "<Name of the source lab>" `
-                            -SourceVirtualMachineName "<Name of the VM to be imported from the source lab> " `
-                            -DestinationSubscriptionId "<ID of the subscription that contians the destination lab>" `
-                            -DestinationDevTestLabName "<Name of the destination lab>" `
-                            -DestinationVirtualMachineName "<Optional: specify a new name for the imported VM in the destination lab>"
-```
+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 all VMs in the source lab
-If the Source Virtual Machine isn’t specified, the script automatically imports all VMs in the DevTest Labs.  For example:
+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>" `
-                            -SourceDevTestLabName "<Name of the source lab>" `
-                            -DestinationSubscriptionId "<ID of the subscription that contians the destination lab>" `
-                            -DestinationDevTestLabName "<Name of the destination lab>"
+./ImportVirtualMachines.ps1 -SourceSubscriptionId "<ID of the subscription that contains the source lab>"`
+                            -SourceDevTestLabName "<Name of the source lab>"`
+                            -SourceVirtualMachineName "<Name of the VM to import from the source lab>" `
+                            -DestinationSubscriptionId "<ID of the subscription that contains the destination lab>"`
+                            -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 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 give enough information to identify the source and destination resources. Remember that the operation takes place on the destination lab resource.
 
-```REST
+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.
+
+```http
 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>",
@@ -69,7 +63,6 @@ POST https://management.azure.com/subscriptions/<DestinationSubscriptionID>/reso
 ```
 
 ## Next steps
-See the following articles:
 
 - [Set policies for a lab](devtest-lab-set-lab-policy.md)
-- [Frequently asked questions](devtest-lab-faq.yml)
+- [DevTest Labs frequently asked questions](devtest-lab-faq.yml)