Solution skill
Unable to create VM with standard security
Complete solution
Shows how to fix unable to create VM with standard security. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For "The value of parameter securityProfile.securityType is invalid.": after downgrading the cli via brew install --build-from-source azure-cli.rb with the file being taken from https://github.com/Homebrew/homebrew-core/blob/4ebae799157b908501142a9752101fd0e69722ba/Formula/a/azure-cli.rb the cli version is v2.70.0 and works properly with security type of Standard. ### Related command ``bash az vm create --name="az-cli-test" --image="MicrosoftWindowsServer:WindowsServer:2022-datacenter-azure-edit What works: Resolved in Azure CLI v2.72.0.
The value of parameter securityProfile.securityType is invalid.Steps
- What was reported:
Issue Azure/azure-cli#31191 (closed, 44 comments): ### Describe the bug Hi there, After upgrading to az v2.71.0, my az vm create commands fail with The value of parameter securityProfile.securityType is invalid.. After downgrading the cli via brew install --build-from-source azure-cli.rb with the file being taken from https://github.com/Homebrew/homebrew-core/blob/4ebae799157b908501142a9752101fd0e69722ba/Formula/a/azure-cli.rb the cli version is v2.70.0 and works properly with security type of Standard. ### Related command ```bash az vm create --name="az-cli-test" --image="MicrosoftWindowsServer:WindowsServer:2022-datacenter-azure-edit
- What works:
Resolved in Azure CLI v2.72.0. You do not need --security-type=Standard on every deployment, only for Gen2 VM/VMSS from PIR or Marketplace images when you need to bypass the Trusted Launch default. Gen1 images, compute gallery images, managed images, and VM sizes without Trusted Launch support do not need the flag.
When to use
You are seeing this: What was reported: Issue Azure/azure-cli#31191 (closed, 44 comments): ### Describe the bug Hi there, After upgrading to az v2.71.0, my az vm create commands fail with The value of parameter securityProfile.securityType is invalid.. Use this skill when you run into "Unable to create VM with standard security".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: az v2.71.0, is v2.70.0, CLI v2.72.0. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/Homebrew/homebrew-core/blob/4ebae799157b908501142a9752101fd0e69722ba/Formula/a/azure-cli.rb
Evidence
In the GitHub issue, the reporter asked: Unable to create VM with standard security. The working answer that came out of the thread: Resolved in Azure CLI v2.72.0. You do not need --security-type=Standard on every deployment, only for Gen2 VM/VMSS from PIR or Marketplace images when you need to bypass the Trusted Launch default. Gen1 images, compute gallery images, managed images, and VM sizes without Trusted Launch support do not need the flag. Source: https://github.com/Azure/azure-cli/issues/31191
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_sOGHLzzHirJ671uqxybDxw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Unable to create VM with standard security <span>— Vectle</span></a>