Skip to content

Commit dedf531

Browse files
committed
another article
1 parent ec3addb commit dedf531

File tree

5 files changed

+128
-121
lines changed

5 files changed

+128
-121
lines changed

articles/devtest-labs/TOC.yml

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,8 @@
7171
href: devtest-lab-auto-shutdown.md
7272
- name: Set auto startup for lab VMs
7373
href: devtest-lab-auto-startup-vm.md
74+
- name: Manage lab storage account
75+
href: encrypt-storage.md
7476
- name: Scale your lab
7577
href: devtest-lab-scale-lab.md
7678
- name: Manage virtual machine bases
@@ -200,12 +202,8 @@
200202
href: devtest-lab-mandatory-artifacts.md
201203
- name: Troubleshoot issues with applying artifacts
202204
href: devtest-lab-troubleshoot-apply-artifacts.md
203-
- name: Encrypt lab resources
204-
items:
205-
- name: Encrypt storage used by a lab
206-
href: encrypt-storage.md
207-
- name: Encrypt OS disks using customer-managed keys
208-
href: encrypt-disks-customer-managed-keys.md
205+
- name: Encrypt OS disks using customer-managed keys
206+
href: encrypt-disks-customer-managed-keys.md
209207
- name: Integrate with CI/CD
210208
items:
211209
- name: Integrate labs into your Azure Pipelines CI/CD pipeline

articles/devtest-labs/devtest-lab-reference-architecture.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ This DevTest Labs enterprise reference architecture has the following components
4848

4949
- [Azure networking topology](../networking/fundamentals/networking-overview.md) to control how lab resources access and communicate with on-premises networks and the internet.
5050

51-
This architecture shows a common way enterprises network DevTest Labs. The labs connect via [peered virtual networks](../virtual-network/virtual-network-peering-overview.md) in a [hub-spoke configuration](/azure/architecture/reference-architectures/hybrid-networking/hub-spoke), through the ExpressRoute or site-to-site VPN connection, to the on-premises network.
51+
This architecture shows a common way that enterprises network DevTest Labs. The labs connect via [peered virtual networks](../virtual-network/virtual-network-peering-overview.md) in a [hub-spoke configuration](/azure/architecture/reference-architectures/hybrid-networking/hub-spoke), through the ExpressRoute or site-to-site VPN connection, to the on-premises network.
5252

5353
Because DevTest Labs uses Azure Virtual Network directly, there are no restrictions on how you set up the networking infrastructure.
5454

@@ -63,7 +63,7 @@ DevTest Labs has no built-in quotas or limits, but other Azure resources that la
6363
Two strategies can help you stay under resource group limits:
6464

6565
- [All VMs go in the same resource group](resource-group-control.md). This strategy helps you meet the resource group limit, but it affects the resource-type-per-resource-group limit.
66-
- Use shared Public IPs. If VMs are allowed to have public IP addresses, put all VMs of the same size and region into the same resource group. This configuration helps meet both resource group quotas and resource-type-per-resource-group quotas.
66+
- [Use shared Public IPs](devtest-lab-shared-ip.md). If VMs are allowed to have public IP addresses, put all VMs of the same size and region into the same resource group. This configuration helps meet both resource group quotas and resource-type-per-resource-group quotas.
6767

6868
- Resources per resource group per resource type. The default limit for [resources per resource group per resource type is 800](../azure-resource-manager/management/azure-subscription-service-limits.md#resource-group-limits). Putting all VMs in the same resource group hits this limit much sooner, especially if the VMs have many extra disks.
6969

0 commit comments

Comments
 (0)