Skip to content

Wording for --license-type is vague #16541

@JiandongRuan

Description

@JiandongRuan

I ran into an issue with enabling Azure Hybrid Benefit on VMSS. It took Azure support 2+ weeks to figure out what's going on. Eventually, the issue was resolved with the help from Azure dev team.

If the documentation of "--license-type" were clear, the Azure support ticket could have been avoided.

Current wording:

"To enable Azure Hybrid Benefit for Windows Server, use 'Windows_Server'"

This give people incorrect impression that Azure Hybrid Benefit will be enabled on the existing VMs in the VMSS after the license type is set on the VMSS. But this is not the case. Users are still required to run the following commands in order for the changes to be applied on the existing VMs.

az vmss update-instances -g "__replaced_with_rg_name__" -n "__replace_with_vmss_name" --instance-ids "*"

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

  • ID: 0408c294-207a-2b72-7b93-e09121602b75
  • Version Independent ID: 852cb67b-70c6-b811-3b0a-5d5b84b8a911
  • Content: az vmss
  • Content Source: latest/docs-ref-autogen/vmss.yml
  • Service: virtual-machine-scale-sets
  • GitHub Login: @rloutlaw
  • Microsoft Alias: routlaw

Metadata

Metadata

Assignees

Labels

Computeaz vm/vmss/image/disk/snapshotquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions