-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Without the paramater '--protected-settings' the command could not work #25512
Copy link
Copy link
Closed
Labels
Auto-AssignAuto assign by botAuto assign by botComputeaz vm/vmss/image/disk/snapshotaz vm/vmss/image/disk/snapshotService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.bugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
Milestone
Metadata
Metadata
Assignees
Labels
Auto-AssignAuto assign by botAuto assign by botComputeaz vm/vmss/image/disk/snapshotaz vm/vmss/image/disk/snapshotService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.bugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
[Enter feedback here]
I do multiple test in my lab and I found, if I did not add this parameter '--protected-settings' the extension could not install successfully.
I must add this paramter even though with a empty value it could still work.
eg:
az vm extension set --name "VMAccessAgent" --publisher "Microsoft.Compute" --vm-name 2022windows -g 2022 --protected-settings "{}"
Could you please help to check if there are some issues with this command? As in the Powershell environment we do not need to add this paramter.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.