Skip to content

Commit bd2d67d

Browse files
authored
Apply suggestions from PR review
1 parent b1a956b commit bd2d67d

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/lab-services/administrator-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -202,8 +202,8 @@ To obtain lab VMs with unique SID, create a lab without a template VM. You must
202202

203203
If you plan to use an endpoint management tool or similar software, we recommend that you don't use template VMs for your labs.
204204

205-
## AAD register/join, Hybrid AAD join, or AD domain join
206-
To make labs easy to set up and manage, Azure Lab Services is designed with *no* requirement to register/join lab VMs to either Active Directory (AD) or Azure Active Directory (AAD). As a result, Azure Lab Services *doesn’t* currently offer built-in support to register/join lab VMs. Although it's possible to AAD register/join, Hybrid AAD join, or AD domain join lab VMs using other mechanisms, we do *not* recommend that you attempt to register/join lab VMs to either AD or AAD due to product limitations.
205+
## Azure AD register/join, Hybrid Azure AD join, or AD domain join
206+
To make labs easy to set up and manage, Azure Lab Services is designed with *no* requirement to register/join lab VMs to either Active Directory (AD) or Azure Active Directory (Azure AD). As a result, Azure Lab Services *doesn’t* currently offer built-in support to register/join lab VMs. Although it's possible to Azure AD register/join, Hybrid Azure AD join, or AD domain join lab VMs using other mechanisms, we do *not* recommend that you attempt to register/join lab VMs to either AD or Azure AD due to product limitations.
207207

208208
## Pricing
209209

articles/lab-services/concept-lab-services-supported-networking-scenarios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ The following table lists common networking scenarios and topologies and their s
3535
| Use a connection broker, such as Parsec, for high-framerate gaming scenarios | Not recommended | This scenario isn’t directly supported with Azure Lab Services and would run into the same challenges as accessing lab VMs by private IP address. |
3636
| *Cyber field* scenario, consisting of a set of vulnerable VMs on the network for lab users to discover and hack into (ethical hacking) | Yes | This scenario works with advanced networking for lab plans. Learn about the [ethical hacking class type](./class-type-ethical-hacking.md). |
3737
| Enable using Azure Bastion for lab VMs | No | Azure Bastion isn't supported in Azure Lab Services. |
38-
| Set up line-of-sight to domain controller | Not recommended | Line-of-sight from a lab to a domain controller is required to Hybrid AAD join or AD domain join VMs; however, we currently do *not* recommend that lab VMs be AAD joined/registered, Hybrid AAD joined, or AD domain joined due to product limitations. |
38+
| Set up line-of-sight to domain controller | Not recommended | Line-of-sight from a lab to a domain controller is required to Hybrid Azure AD join or AD domain join VMs; however, we currently do *not* recommend that lab VMs be Azure AD joined/registered, Hybrid Azure AD joined, or AD domain joined due to product limitations. |
3939

4040
## Next steps
4141

0 commit comments

Comments
 (0)