Change the Default VM Size in CLI [P0 | Issue 1 of 2] #31358
Description
Preconditions
- No need to upgrade Python SDK or the Python SDK is ready.
Related command
No response
Resource Provider
microsoft.compute/virtualmachines
Description of Feature or Work Requested
Note: this is the first of two requests from Azure Compute PM team with similar titles. This P0 request is more lightweight and requires immediate action to reduce customer impact.
We recently announced the retirement of Dv1/Dsv1/Dv2/Dsv2/Lsv1 on March 31, 2025. Although we have given customers a 3-year retirement timeline, we want to accelerate the customer migration/resize churn off these VM sizes. (See additional context on retirement here: https://azure.microsoft.com/en-us/updates/?id=485569)
We need to modify the default VM size of VM creation ASAP as we've officially started placing quota restrictions on Standard_DS_v2 family (and several others) per the retirement announcement.
Request: For all instances in CLI where default VM is a v2 or v3 VM family, change to Standard_D2as_v5
Why Standard_D2as_v5 specifically?
- D2as_v5 is the lowest size general purpose equivalent VM suitable for most applications
- There is minimal compatibility difference between v2, v3 and v5 VMs.
- Why not D2s_v5? We prefer recommending AMD as that is more cost efficient and widely available marginally.
- Why not D2ads_v5? the 2nd "d" means local storage is enabled. Azure Compute prefers customers to go diskless / remote storage as that enables a more seamless experience. Also, D2as_v5 is more cost effective.
- Why not v6 VMs? v6 VMs introduce NVMe storage requirement, which increases deployment failure likelihood.
- Why not v4 VMs? v4 VMs are considered Mature and will be considered for deprecation in a few years.
Minimum API Version Required
N/A
Swagger PR link / SDK link
N/A
Request Example
Example command: az vmss create -l westus3 -g cli2720rg --orchestration-mode Uniform --image $imageId -n tladclivmss35
Yields: Default: Standard_DS1_v2
Requested change: Standard_D2as_v5
Target Date
ASAP
PM Contact
@yulyang
Engineer Contact
Additional context
No response