Skip to content

Commit f72bdab

Browse files
author
Lauren Dunlap
committed
content feedback and toc
1 parent f3168bc commit f72bdab

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

articles/lab-services/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
items:
55
- name: Azure Lab Services retirement guide
66
href: retirement-guide.md
7+
- name: Find and delete lab resources
8+
href: find-delete-resources.md
79
- name: What is Azure Lab Services?
810
href: lab-services-overview.md
911
expanded: true

articles/lab-services/retirement-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ To ensure that you have the resources you require when you need them, you should
131131
- Be flexible on the region where you're requesting capacity, if possible.
132132
- Make incremental requests for VM cores rather than making large, bulk requests. Break requests for large number of cores into smaller requests for extra flexibility in how those requests are fulfilled.
133133

134-
### Should I request the same amount of Azure subscription core limits with my preferred transition solution?
134+
### Should I request the same number of Azure subscription core limits with my preferred transition solution?
135135
Make sure to review your lab usage trends and not assume you require the same volume of core limits. Keep in mind, the recommended transition solutions allow for more efficient use of lab resources which can reduce the overall number of cores needed. For example, multi-session VDI offerings enable multiple users to share the same VM.
136136

137137
## Related content

0 commit comments

Comments
 (0)