[Doc]: Get-AzKeyVaultCertificate → "save as pfx" example broken

[odegroot]

Description

"Example 2: Get cert and save it as pfx" does not work on my machine.

Specifically, the following command does nothing.

# Write to a file
[System.IO.File]::WriteAllBytes("cert.pfx", $secretByte)

I was able to fix the problem by using the following command instead (source):

Set-Content -Path "cert.pfx" -Value $secretByte -AsByteStream

Perhaps this would be a nice improvement to the docs?

---

Document Details

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

• ID: 45cbf981-0e5a-cf19-bc73-882d61da8001
• Version Independent ID: 63263710-e864-310a-6a42-c618857872b0
• Content: Get-AzKeyVaultCertificate (Az.KeyVault)
• Content Source: src/KeyVault/KeyVault/help/Get-AzKeyVaultCertificate.md
• Service: key-vault
• GitHub Login: @mikefrobbins
• Microsoft Alias: mirobb

[dingmeng-xue]

@CaptainFanZzz , please look into this issue. Please adjust example and ensure it works on Windows PowerShell and PowerShell 7 both.

[BethanyZhou]

Hi @odegroot , thank you for reporting. I have updated the example with a more concise way. Please have a try.

[odegroot]

Thank you, but I don't believe this is right. (link to updated example)

When I try this, $secret contains a long Base64 string. Simply writing it to a .pfx-file does not yield anything valid. I do need the Base64-decode step.

Note that the example output (-----BEGIN PRIVATE KEY-----) is not a pfx either, that's PEM-formatted.

Additionally, for brevity, we can skip the first step: all we use from $cert is $cert.Name which is the same as $certName anyway. We can just input the $certName into Get-AzKeyVaultSecret directly.

$cert = Get-AzKeyVaultCertificate -VaultName $vaultName -Name $certName

I have created a PR that addresses these comments: #19003