Documentation incorrectly states false is an option for enable-purge-protection on keyvault create

[neilmca-inc]

Documentation stats that false is an option for the --enable-purge-protection switch on az keyvault create

enable-purge-protection

If you try this you get the following error...

The property "enablePurgeProtection" cannot be set to false

---

Document Details

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

• ID: 226e5769-f6c8-a480-db78-727fb96348ec
• Version Independent ID: 8ee06a2a-6eda-11be-3c8e-6ad948be207e
• Content: az keyvault
• Content Source: latest/docs-ref-autogen/keyvault.yml
• Service: key-vault
• GitHub Login: @rloutlaw
• Microsoft Alias: routlaw

[yonzhan]

keyvault

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.

Issue Details

---

Documentation stats that false is an option for the --enable-purge-protection switch on az keyvault create

enable-purge-protection

If you try this you get the following error...

The property "enablePurgeProtection" cannot be set to false

---

Document Details

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

• ID: 226e5769-f6c8-a480-db78-727fb96348ec
• Version Independent ID: 8ee06a2a-6eda-11be-3c8e-6ad948be207e
• Content: az keyvault
• Content Source: latest/docs-ref-autogen/keyvault.yml
• Service: key-vault
• GitHub Login: @rloutlaw
• Microsoft Alias: routlaw

Author:	neilmca-inc
Assignees:	evelyn-ys
Labels:	KeyVault, Service Attention, customer-reported, Auto-Assign
Milestone:	Backlog

[jlichwa]

It is in our backlog. The default is false, so as a workaround you can skip this parameter with same result as a workaround.