Skip to content

Commit ac70388

Browse files
authored
Merge pull request #241348 from ntrogh/als-advanced-networking
[Azure Lab Services] Update advanced networking for clarity
2 parents 6e7eee8 + 31577b7 commit ac70388

19 files changed

+150
-79
lines changed

articles/lab-services/TOC.yml

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,9 @@
4242
- name: Migrate lab account role assignments
4343
displayName: RBAC, authorization, security, roles, permissions, admin, lab creator, lab account, migrate, upgrade
4444
href: concept-migrate-from-lab-accounts-roles.md
45+
- name: Supported networking topologies
46+
displayName: advanced, networking, vnet, subnet, hybrid, connectivity, VPN, ExpressRoute, peering, NAT, gateway, firewall, proxy, load balancer, Azure Bastion, Azure Firewall, Azure Application Gateway, Azure Front Door, Azure Traffic Manager, Azure Virtual WAN, Azure VPN Gateway, Azure ExpressRoute, Azure Private Link, Azure DNS, Azure DDoS Protection, Azure Firewall Manager, Azure Load Balancer, Azure Bastion, Azure Application Gateway, Azure Front Door, Azure Traffic Manager, Azure Virtual WAN, Azure VPN Gateway, Azure ExpressRoute, Azure Private Link, Azure DNS, Azure DDoS Protection, Azure Firewall Manager, Azure Load Balancer
47+
href: concept-lab-services-supported-networking-scenarios.md
4548
- name: Migrate from physical labs
4649
href: concept-migrating-physical-labs.md
4750
- name: Nested virtualization on a template VM
@@ -119,10 +122,6 @@
119122
href: migrate-to-2022-update.md
120123
- name: Create & configure lab plans (admin)
121124
items:
122-
- name: Request core limit increase
123-
href: how-to-request-capacity-increase.md?tabs=Labplans
124-
- name: Determine Usage and Quota
125-
href: how-to-determine-your-quota-usage.md
126125
- name: Create and manage lab plans
127126
items:
128127
- name: Create & manage lab plans (Azure portal)
@@ -137,11 +136,15 @@
137136
href: how-to-create-lab-plan-python.md
138137
- name: Add a lab creator
139138
href: add-lab-creator.md
140-
- name: Configure auto-shutdown settings
141-
href: how-to-configure-auto-shutdown-lab-plans.md
142-
- name: Connect to a virtual network
139+
- name: Connect a lab plan to a virtual network
143140
displayName: VNET, injection, advanced, networking, hybrid, on-premise
144141
href: how-to-connect-vnet-injection.md
142+
- name: Request core limit increase
143+
href: how-to-request-capacity-increase.md?tabs=Labplans
144+
- name: Determine Usage and Quota
145+
href: how-to-determine-your-quota-usage.md
146+
- name: Configure auto-shutdown settings
147+
href: how-to-configure-auto-shutdown-lab-plans.md
145148
- name: Create a lab with a shared resource
146149
href: how-to-create-a-lab-with-shared-resource.md
147150
- name: Specify Marketplace images for labs
@@ -175,7 +178,7 @@
175178
- name: Restrict VM sizes allowed for labs
176179
href: how-to-use-restrict-allowed-virtual-machine-sku-sizes-policy.md
177180
- name: Create & configure labs (educator)
178-
items:
181+
items:
179182
- name: Create and manage labs
180183
items:
181184
- name: Create and manage labs (website)

articles/lab-services/account-setup-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ To create a lab account, you need access to an Azure subscription that's already
3030

3131
It's important to know how many [virtual machines (VMs) and which VM sizes](./administrator-guide-1.md#vm-sizing) your school lab requires.
3232

33-
For guidance on structuring your labs and images, see the blog post [Moving from a physical lab to Azure Lab Services](https://techcommunity.microsoft.com/t5/azure-lab-services/moving-from-a-physical-lab-to-azure-lab-services/ba-p/1654931).
33+
For guidance on structuring your labs and images, see [Moving from a physical lab to Azure Lab Services](./concept-migrating-physical-labs.md).
3434

3535
For more information on how to structure labs, see the "Lab" section of [Azure Lab Services - Administrator guide](./administrator-guide-1.md#lab).
3636

articles/lab-services/administrator-guide.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -188,6 +188,8 @@ There are a few key points to highlight as part of this solution:
188188
- If you plan to use the [auto-shutdown settings](./cost-management-guide.md#automatic-shutdown-settings-for-cost-control), you'll need to unblock several Azure host names with the 3rd party software. The auto-shutdown settings use a diagnostic extension that must be able to communicate back to Lab Services. Otherwise, the auto-shutdown settings will fail to enable for the lab.
189189
- You may also want to have each student use a non-admin account on their VM so that they can't uninstall the content filtering software. Adding a non-admin account must be done when creating the lab.
190190

191+
Learn more about the [supported networking scenarios in Azure Lab Services](./concept-lab-services-supported-networking-scenarios.md), such as content filtering.
192+
191193
If your school needs to do content filtering, contact us via the [Azure Lab Services' Q&A](https://aka.ms/azlabs/questions) for more information.
192194

193195
## Endpoint management

articles/lab-services/class-type-arcgis.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,13 +23,13 @@ One type of licensing that ArcGIS Desktop offers is [concurrent use licenses](ht
2323
The license server is located in either your on-premises network or hosted on an Azure virtual machine within an Azure virtual network. After your license server is set up, you'll need to [Connect to your virtual network in Azure Lab Services](how-to-connect-vnet-injection.md) with your lab plan.
2424

2525
> [!IMPORTANT]
26-
> [Advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) must be enabled during the creation of your lab plan. It can't be added later.
26+
> [Advanced networking](how-to-connect-vnet-injection.md) must be enabled during the creation of your lab plan. It can't be added later.
2727
2828
For more information, see [Set up a license server as a shared resource](how-to-create-a-lab-with-shared-resource.md).
2929

3030
## Lab configuration
3131

32-
When you get an Azure subscription, you can create a new lab plan in Azure Lab Services. For more information about creating a new lab plan, see the tutorial on [how to set up a lab plan](./quick-create-resources.md). If you're using a ArcGIS License Manager on a license server, enable [advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) when creating your lab plan. You can also use an existing lab plan.
32+
When you get an Azure subscription, you can create a new lab plan in Azure Lab Services. For more information about creating a new lab plan, see the tutorial on [how to set up a lab plan](./quick-create-resources.md). If you're using a ArcGIS License Manager on a license server, enable [advanced networking](how-to-connect-vnet-injection.md) when creating your lab plan. You can also use an existing lab plan.
3333

3434
### Lab plan settings
3535

articles/lab-services/class-type-autodesk.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ You need to access a license server if you plan to use the Autodesk network lice
2929

3030
To use network licensing with Autodesk software, [AutoDesk provides detailed steps](https://knowledge.autodesk.com/customer-service/network-license-administration/install-and-configure-network-license) to install Autodesk Network License Manager on your license server. You can host the license server in your on-premises network, or on an Azure virtual machine (VM) within in an Azure virtual network.
3131

32-
After setting up your license server, you need to enable [advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) when you create the lab plan.
32+
After setting up your license server, you need to enable [advanced networking](how-to-connect-vnet-injection.md) when you create the lab plan.
3333

3434
Autodesk-generated license files embed the MAC address of the license server. If you decide to host your license server by using an Azure VM, it’s important to make sure that your license server’s MAC address doesn’t change. If the MAC address changes, you need to regenerate your licensing files. To prevent your MAC address from changing:
3535

@@ -39,7 +39,7 @@ Autodesk-generated license files embed the MAC address of the license server. I
3939
For more information, see [Set up a license server as a shared resource](./how-to-create-a-lab-with-shared-resource.md).
4040

4141
> [!IMPORTANT]
42-
> You must enable [advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) when creating your lab plan. You can't enable advanced networking for an existing lab plan.
42+
> You must enable [advanced networking](how-to-connect-vnet-injection.md) when creating your lab plan. You can't enable advanced networking for an existing lab plan.
4343
4444
## Lab configuration
4545

articles/lab-services/class-type-matlab.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,11 +28,11 @@ For detailed instructions on how to install a licensing server, see [Install Lic
2828
Assuming the license server is located in an on-premises network or a private network within Azure, you’ll need to [Connect to your virtual network in Azure Lab Services](how-to-connect-vnet-injection.md) when creating your [lab plan](./quick-create-resources.md).
2929

3030
> [!IMPORTANT]
31-
> [Advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) must be enabled during the creation of your lab plan. It can't be added later.
31+
> [Advanced networking](how-to-connect-vnet-injection.md) must be enabled during the creation of your lab plan. It can't be added later.
3232
3333
## Lab configuration
3434

35-
Once you have an Azure subscription, you can create a new lab plan in Azure Lab Services. For more information about creating a new lab plan, see the tutorial on [how to set up a lab plan](./quick-create-resources.md). If you're using a [Network License Manager](https://www.mathworks.com/help/install/administer-network-licenses.html) on a license server, enable [advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) when creating your lab plan. You can also use an existing lab plan.
35+
Once you have an Azure subscription, you can create a new lab plan in Azure Lab Services. For more information about creating a new lab plan, see the tutorial on [how to set up a lab plan](./quick-create-resources.md). If you're using a [Network License Manager](https://www.mathworks.com/help/install/administer-network-licenses.html) on a license server, enable [advanced networking](how-to-connect-vnet-injection.md) when creating your lab plan. You can also use an existing lab plan.
3636

3737
### Lab settings
3838

articles/lab-services/class-type-pltw.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ To use network licensing with Autodesk software, [PLTW provides detailed steps](
6565
After your license server is set up, you need to [Connect to your virtual network in Azure Lab Services](how-to-connect-vnet-injection.md) when creating your [lab plan](./quick-create-resources.md).
6666

6767
> [!IMPORTANT]
68-
> [Advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) must be enabled during the creation of your lab plan. It can't be added later.
68+
> [Advanced networking](how-to-connect-vnet-injection.md) must be enabled during the creation of your lab plan. It can't be added later.
6969
7070
Autodesk-generated license files embed the MAC address of the license server. If you decide to host your license server by using an Azure VM, it’s important to ensure that your license server’s MAC address doesn’t change. If the MAC address changes, you'll need to regenerate your licensing files. Following are the steps to prevent your MAC address from changing:
7171

@@ -78,7 +78,7 @@ For more information, see [Set up a license server as a shared resource](./how-t
7878

7979
Once you have Azure subscription, you can create a new lab plan in Azure Lab Services. For more information about creating a new lab plan, see the tutorial on [how to set up a lab plan](./quick-create-resources.md).
8080

81-
After you set up a lab plan, create a separate lab for each PLTW class session that your school offers. We also recommend that you create separate images for each type of PLTW class. For more information about how to structure your labs and images, see the blog post [Moving from a Physical Lab to Azure Lab Services](https://techcommunity.microsoft.com/t5/azure-lab-services/moving-from-a-physical-lab-to-azure-lab-services/ba-p/1654931).
81+
After you set up a lab plan, create a separate lab for each PLTW class session that your school offers. We also recommend that you create separate images for each type of PLTW class. For more information about how to structure your labs and images, see [Moving from a Physical Lab to Azure Lab Services](./concept-migrating-physical-labs.md).
8282

8383
### Lab plan settings
8484

articles/lab-services/class-type-rstudio-linux.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ If you choose to have a shared R Server for the students, the server should be s
2828
If you choose to use any external resources, you need to [Connect to your virtual network in Azure Lab Services](how-to-connect-vnet-injection.md) with your lab plan.
2929

3030
> [!IMPORTANT]
31-
> [Advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) must be enabled during the creation of your lab plan. It can't be added later.
31+
> [Advanced networking](how-to-connect-vnet-injection.md) must be enabled during the creation of your lab plan. It can't be added later.
3232
3333
### Lab plan settings
3434

articles/lab-services/class-type-rstudio-windows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ If you choose to have a shared R Server for the students, the server should be s
3737
If you choose to use any external resources, you’ll need to [Connect to your virtual network in Azure Lab Services](how-to-connect-vnet-injection.md) with your lab plan.
3838

3939
> [!IMPORTANT]
40-
> [Advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) must be enabled during the creation of your lab plan. It can't be added later.
40+
> [Advanced networking](how-to-connect-vnet-injection.md) must be enabled during the creation of your lab plan. It can't be added later.
4141
4242
### Lab plan settings
4343

articles/lab-services/class-type-solidworks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ SOLIDWORKS Network Licensing requires that you have installed and activated Soli
3131
1. After you set up the license server, follow these steps to [connect your lab plan to your virtual network in Azure Lab Services](how-to-connect-vnet-injection.md).
3232

3333
> [!IMPORTANT]
34-
> You need to enable [advanced networking](how-to-connect-vnet-injection.md#connect-the-virtual-network-during-lab-plan-creation) during the creation of your lab plan. You can't configure the lab plan's virtual network at a later stage.
34+
> You need to enable [advanced networking](how-to-connect-vnet-injection.md) during the creation of your lab plan. You can't configure the lab plan's virtual network at a later stage.
3535
3636
1. Verify that the appropriate ports are opened on your firewalls to allow communication between the lab virtual machines and the license server.
3737

0 commit comments

Comments
 (0)