Merge pull request #232364 from ntrogh/als-remove-faq

[Azure Lab Services] Move info from FAQ into appropriate topics

Author: v-dirichards

.openpublishing.redirection.azure-productivity.json

@@ -144,6 +144,11 @@
       "source_path": "articles/lab-services/quick-create-lab-template.md",
       "redirect_url": "/azure/lab-services/how-to-create-lab-template",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/lab-services/classroom-labs-faq.yml",
+      "redirect_url": "/azure/lab-services/lab-services-overview",
+      "redirect_document_id": false
     }
   ]
 }

articles/lab-services/TOC.yml

@@ -320,5 +320,3 @@
     href: https://aka.ms/azlabs/questions
   - name: Tech community forum
     href: https://techcommunity.microsoft.com/t5/azure-lab-services/bd-p/AzureLabServices
-  - name: Frequently asked questions
-    href: classroom-labs-faq.yml

articles/lab-services/administrator-guide.md

@@ -268,6 +268,8 @@ Creating a compute gallery and attaching it to your lab plan is free. No cost is
 
 To store image versions, a compute gallery uses standard hard disk drive (HDD) managed disks by default.  We recommend using HDD-managed disks when using compute gallery with Lab Services.  The size of the HDD-managed disk that is used depends on the size of the image version that is being stored.  Lab Services supports image and disk sizes up to 128 GB.  To learn about pricing, see [Managed disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/).
 
+Azure Lab Services doesn't support attaching additional disks to a lab template or lab VM.
+
 #### Replication and network egress charges
 
 When you save an image version by using a lab template VM, Azure Lab Services first stores it in a source region.  However, you'll most likely need to replicate the source image version to one or more target regions.

articles/lab-services/classroom-labs-concepts.md

@@ -96,6 +96,8 @@ Example scenarios for using quotas are:
 
 When a lab user starts their lab VM, quota hours for the lab start counting. If a lab creator manually starts the lab VM for a user, quota hours aren't used for that student.
 
+The quota applies to a lab for each lab user individually, for the entire duration of the lab.
+
 A lab can use either quota time, [scheduled time](#schedule), or a combination of both.
 
 ## Next steps

articles/lab-services/classroom-labs-faq.yml

@@ -25,6 +25,8 @@ By default, access to a lab is restricted. Only users that are in the list of la
 
 You can [add users from an Azure Active Directory (Azure AD) group](#add-users-to-a-lab-from-an-azure-ad-group), or [manually add a list of users by email](#add-users-manually). If you enable Azure Lab Services integration with [Microsoft Teams](./how-to-manage-labs-within-teams.md) or [Canvas](./how-to-manage-labs-within-canvas.md), Azure Lab Services automatically grants user access to the lab and assigns a lab VM based on their membership in Microsoft or Canvas. In this case, you don't have to specify the lab user list, and users don't have to register for the lab.
 
+Azure Lab Services supports up to 400 users per lab.
+
 ## Prerequisites
 
 - To manage users for the lab, your Azure account needs one of the following permissions:

articles/lab-services/how-to-configure-student-usage.md

@@ -1,8 +1,13 @@
 ---
-title: Connect to a peer network in Azure Lab Services | Microsoft Docs
-description: Learn how to connect your lab network with another network as a peer. For example, connect your on-premises organization/university network with Lab's virtual network in Azure.  
+title: Connect to a peer network
+titleSuffix: Azure Lab Services
+description: Learn how to connect your lab network with another network as a peer for lab accounts in Azure Lab Services. For example, connect your on-premises organization/university network with Lab's virtual network in Azure.  
+services: lab-services
+ms.service: lab-services
+author: ntrogh
+ms.author: nicktrog
 ms.topic: how-to
-ms.date: 06/26/2020
+ms.date: 03/28/2023
 ---
 
 # Connect your lab's network with a peer virtual network in Azure Lab Services
@@ -30,46 +35,49 @@ Certain on-premises networks are connected to Azure Virtual Network either throu
 
 ## Configure at the time of lab account creation
 
-During the new [lab account creation](tutorial-setup-lab-account.md), you can pick an existing virtual network that shows in the **Peer virtual network** dropdown list on the **Advanced** tab.  The list will only show virtual networks in the same region as the lab account. The selected virtual network is connected (peered) to labs created under the lab account.  All the virtual machines in labs that are created after the making this change will have access to the resources on the peered virtual network.
+During the new [lab account creation](tutorial-setup-lab-account.md), you can pick an existing virtual network that shows in the **Peer virtual network** dropdown list on the **Advanced** tab.  The list only shows virtual networks in the same region as the lab account. The selected virtual network is connected (peered) to labs created under the lab account.  All the virtual machines in labs that are created after the making this change have access to the resources on the peered virtual network.
 
-![Select VNet to peer](./media/how-to-connect-peer-virtual-network/select-vnet-to-peer.png)
+![Screenshot that shows how to create a lab account in the Azure portal, highlighting the peer virtual network setting.](./media/how-to-connect-peer-virtual-network/select-vnet-to-peer.png)
 
 ### Address range
 
-There is also an option to provide **Address range** for virtual machines for the labs.  The **address range** property applies only if a **peer virtual network** is enabled for the lab. If the address range is provided, all the virtual machines in the labs under the lab account will be created in that address range. The address range should be in CIDR notation (for example, 10.20.0.0/20) and not overlap with any existing address ranges.  When providing an address range, it's important to think about the number of *labs* that will be created and provide an address range to accommodate that. Lab Services assumes a maximum of 512 virtual machines per lab.  For example, an ip range with '/23' can create only one lab.  A range with a '/21' will allow for the creation of four labs.
+There's also an option to provide an address range for virtual machines for the labs.  The address range setting applies only if you enable a peer virtual network for the lab. If the address range is provided, all the virtual machines in the labs under the lab account are created in that address range. The address range should be in CIDR notation (for example, 10.20.0.0/20) and shouldn't overlap with any existing address ranges.
 
-If the **Address range** is not specified, Lab Services will use the default address range given to it by Azure when creating the virtual network to be peered with your virtual network.  The range is often something like 10.x.0.0/16.  This may lead to ip range overlap, so make sure to either specify an address range in the lab settings or check the address range of your virtual network being peered.
+When you provide an address range, it's important to think about the number of *labs* that you create. Azure Lab Services assumes a maximum of 512 virtual machines per lab. For example, an IP range with '/23' can create only one lab.  A range with a '/21' allows for the creation of four labs.
+
+If the address range isn't specified, Azure Lab Services uses the default address range given to it by Azure when creating the virtual network to be peered with your virtual network.  The range is often something like 10.x.0.0/16.  This large range might lead to IP range overlap, so make sure to either specify an address range in the lab settings or check the address range of your virtual network being peered.
 
 > [!NOTE]
 > Lab creation can fail if the lab account is peered to a virtual network but has too narrow of an IP address range. You can run out of space in the address range if there are too many labs in the lab account (each lab uses 512 addresses). 
+>
+> For example, if you have a block of /19, this address range can accommodate 8192 IP addresses and 16 labs (8192/512 = 16 labs). In this case, lab creation fails on the 17th lab creation.
 > 
 > If the lab creation fails, contact your lab account owner/admin and request for the address range to be increased. The admin can increase the address range using steps mentioned in the [Specify an address range for VMs in a lab account](#specify-an-address-range-for-vms-in-the-lab-account) section. 
 
 ## Configure after the lab account is created
 
 The same property can be enabled from the **Labs configuration** tab of the **Lab Account** page if you didn't set up a peer network at the time of lab account creation. Change made to this setting applies only to the labs that are created after the change. As you can see in the image, you can enable or disable **Peer virtual network** for labs in the lab account.
 
-![Enable or disable VNet peering after the lab is created](./media/how-to-connect-peer-virtual-network/select-vnet-to-peer-existing-lab.png)
+![Screenshot that shows the lab settings page for a lab account in the Azure portal, highlighting the enable peer virtual network option.](./media/how-to-connect-peer-virtual-network/select-vnet-to-peer-existing-lab.png)
 
-When you select a virtual network for the **Peer virtual network** field, the **Allow lab creator to pick lab location** option is disabled. That's because labs in the lab account must be in the same region as the lab account for them to connect with resources in the peer virtual network.
+When you select a virtual network for the **Peer virtual network** field, the **Allow lab creator to pick lab location** option is disabled. Labs in the lab account must be in the same region as the lab account for them to connect with resources in the peer virtual network.
 
 > [!IMPORTANT]
 > The peered virtual network setting applies only to labs that are created after the change is made, not to the existing labs.
 
-
 ## Specify an address range for VMs in the lab account
 The following procedure has steps to specify an address range for VMs in the lab. If you update the range that you previously specified, the modified address range applies only to VMs that are created after the change was made. 
 
 Here are some restrictions when specifying the address range that you should keep in mind. 
 
 - The prefix must be smaller than or equal to 23. 
-- If a virtual network is peered to the lab account, the provided address range cannot overlap with address range from peered virtual network.
+- If a virtual network is peered to the lab account, the provided address range can't overlap with address range from peered virtual network.
 
-1. On the **Lab Account** page, select **Labs settings** on the left menu.
-2. For the **Address range** field, specify the address range for VMs that will be created in the lab. The address range should be in the classless inter-domain routing (CIDR) notation (example: 10.20.0.0/23). Virtual machines in the lab will be created in this address range.
+1. On the **Lab Account** page, select **Lab settings** on the left menu.
+2. For the **Address range** field, specify the address range for VMs that are created in the lab. The address range should be in the classless inter-domain routing (CIDR) notation (example: 10.20.0.0/23). Virtual machines in the lab are created in this address range.
 3. Select **Save** on the toolbar. 
 
-    ![Configure address range](./media/how-to-manage-lab-accounts/labs-configuration-page-address-range.png)
+    ![Screenshot that shows the lab settings page for a lab account in the Azure portal, highlighting the option to configure an address range.](./media/how-to-manage-lab-accounts/labs-configuration-page-address-range.png)
 
 ## Next steps