Feature - New VM sizes#71
Merged
Merged
Conversation
Contributor
Author
…g VM information to TRE users
GamblingFool
left a comment
Contributor
There was a problem hiding this comment.
Great work on this PR!
The updates are well-structured and clearly address the issues outlined in the previous discussions. I appreciate the attention to detail and the thorough testing that has been conducted.
GamblingFool
approved these changes
Jun 22, 2026
GamblingFool
left a comment
Contributor
There was a problem hiding this comment.
Great work on this PR!
The updates are well-structured and clearly address the issues outlined in the previous discussions. I appreciate the attention to detail and the thorough testing that has been conducted.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Run ID: e20aee7f
What is being addressed
Introduce new VM sizes to aid in the battle against compute quota in Azure
How is this addressed
Current offering
Notes during development
Fasv6 (Standard_F*as_v6) sizes have been removed from the VM size options. The Fasv6 series requires NVMe disk controller support in the OS image. The current OUH images (Windows 10, Windows 11, and the OUH Server 2019 Data Science VM) were built with SCSI disk controllers and are not compatible, causing a 400 InvalidParameter error on deployment.
Expands the CPU VM size options available to researchers across both the Windows and Linux VM bundles.
The Dasv5 series (AMD EPYC) has been extended to cover 4, 8, 16, and 32 CPU sizes, providing an AMD-based alternative across the full size range and spreading quota load away from the Intel Dsv5 series.
Issues
Current GPU quota position in UK South:
A10 (NVadsA10_v5): Quota exhausted. No new A10 VMs can be deployed until quota frees up or is increased.
T4 (NCasT4_v3): Quota request unsuccessful.
H100 (NCadsH100_v5): Available. Retained in the bundle for essential workloads only due to cost (£7.70–£15.90/hr).
NVadsV710 (AMD ROCm): Available but requires unique VM image and set up and pre-qualification of researcher workload; not suitable as a general GPU offering.
Updates
A10 quota request — outcome
Next actions:
New VM sizes