Create VM with specific size
In the previous VM creation example, a size was not provided, which results in a default size. A VM size can be selected at creation time using az vm create and the --size argument.
Can the documentation specify what the "default size" is and how it it calculated?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@kskvarci Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@kskvarci The default VM size is provided from the Azure CLI or Azure PowerShell tools. It's something those development teams hard-code. Currently, the default size for the Azure CLI 2.0 is a _Standard_DS1_v2_. That decision was likely made as a good balance between cost and performance. Unfortunately, it isn't currently looking at what's available for your subscription or region - it's not dynamic, there's nothing being calculated.
The initial example was to show that you can just quickly create a VM without specifying a size. For most real scenarios, you would specify --size and provide the most appropriate SKU for your needs. As such, I'm hesitant to add in what the default size is, as that has changed within the tooling as different SKUs become available, and you'd typically be specifying a size.
If there are additional requests to detail the default size, we can revisit updating the docs, but for now #please-close
Most helpful comment
@kskvarci The default VM size is provided from the Azure CLI or Azure PowerShell tools. It's something those development teams hard-code. Currently, the default size for the Azure CLI 2.0 is a _Standard_DS1_v2_. That decision was likely made as a good balance between cost and performance. Unfortunately, it isn't currently looking at what's available for your subscription or region - it's not dynamic, there's nothing being calculated.
The initial example was to show that you can just quickly create a VM without specifying a size. For most real scenarios, you would specify
--sizeand provide the most appropriate SKU for your needs. As such, I'm hesitant to add in what the default size is, as that has changed within the tooling as different SKUs become available, and you'd typically be specifying a size.If there are additional requests to detail the default size, we can revisit updating the docs, but for now #please-close