Skip to content

Commit 2c7d119

Browse files
committed
Update after review
1 parent 9457273 commit 2c7d119

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/lab-services/concept-lab-accounts-versus-lab-plans.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ By using lab plans, you can unlock several new capabilities:
2828

2929
**[Per-customer assigned capacity](capacity-limits.md#per-customer-assigned-capacity)**. You don't have to share capacity with others anymore. If your organization has requested more quota, Azure Lab Services allocates it just for you.
3030

31-
**[Advanced networking](how-to-connect-vnet-injection.md)**. Virtual network peering replaces advanced networking. If you have a lab plan with advanced networking, Azure Lab Services creates lab virtual machines in your virtual network. In your Azure subscription, you can create a virtual network in the same region as the lab plan, and delegate a subnet to Azure Lab Services.
31+
**[Advanced networking](how-to-connect-vnet-injection.md)**. Advanced networking with virtual network injection replaces virtual network peering. In your Azure subscription, you can create a virtual network in the same region as the lab plan, and delegate a subnet to Azure Lab Services.
3232

3333
**[Improved auto-shutdown](how-to-configure-auto-shutdown-lab-plans.md)**. Auto-shutdown settings are now available for Windows and Linux operating systems. Learn more about the [supported Linux distributions](./how-to-enable-shutdown-disconnect.md#supported-linux-distributions-for-automatic-shutdown).
3434

@@ -66,7 +66,7 @@ Lab accounts and labs have a parental relationship. Moving to a sibling relatio
6666

6767
## Known issues
6868

69-
- When using virtual network injection, use caution in making changes to the virtual network and subnet. Changes may cause the lab VMs to stop working. For example, deleting your virtual network causes all the lab VMs to stop working. We plan to improve this experience in the future, but for now make sure to delete labs before deleting networks.
69+
- When using virtual network injection, use caution in making changes to the virtual network, subnet, and resources created by Lab Services attached to the subnet. Also, labs using advanced networking must be deleted before deleting the virtual network.
7070

7171
- Moving lab plan and lab resources from one Azure region to another isn't supported.
7272

articles/lab-services/how-to-manage-vm-pool.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ To start individual lab VMs:
6969
1. Alternately, select multiple VMs using the checks to the left of the **Name** column, and then select the **Start** button at the top of the page.
7070

7171
> [!NOTE]
72-
> When you start a lab VM, it doesn't affect the available [quota hours](./classroom-labs-concepts.md#quota) for the lab user. Make sure to stop all lab VMs manually or use a [schedule](how-to-create-schedules.md) to avoid unexpected costs.
72+
> When you start a lab VM *from the virtual machine pool page*, it doesn't affect the available [quota hours](./classroom-labs-concepts.md#quota) for the lab user. Make sure to stop all lab VMs manually or use a [schedule](how-to-create-schedules.md) to avoid unexpected costs.
7373
7474
## Manually stop lab VMs
7575

0 commit comments

Comments
 (0)