Enable-Bitlocker parameter presentation is unclear

[RichMath]

When the -Pin parameter is used and the -EncryptionMethod parameter is omitted, the interpretation of the cmdlet fails with:

Enable-BitLocker : Parameter set cannot be resolved using the specified named parameters.
At line:1 char:1
+ enable-bitlocker -whatif:$true -MountPoint X: -TpmAndPinProtecctor
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Enable-BitLocker], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameterSet,Enable-BitLocker

This is the parameter set:

Enable-BitLocker
      [-MountPoint] <String[]>
      -TpmAndPinProtector
      [-Pin] <SecureString>[-EncryptionMethod <BitLockerVolumeEncryptionMethodOnEnable>]
      [-HardwareEncryption][-SkipHardwareTest]
      [-UsedSpaceOnly]
      [-WhatIf]
      [-Confirm]
      [<CommonParameters>]

Is the rightmost "]" in the wrong place? Should the "-EncryptionMethod" parameter name be enclosed in "[" and "]" making both the <SecureString> and <BitLockerVolumeEncryptionMethodOnEnable> mandatory parameters? In the description of the -EncryptionMethod paramter says the parameter is "Named", not positional. That would seem to mean that if "-Pin" is used (even as a positional parameter) the -EncryptionMethod parameter name must be used.

Document Details

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

• ID: 9a1effb3-f98f-ce90-f31d-0ac05f7a1b91
• Version Independent ID: 3428c627-8703-752e-fbdf-52526f281f57
• Content: Enable-BitLocker (BitLocker)
• Content Source: docset/winserver2022-ps/bitlocker/Enable-BitLocker.md
• Product: w10
• GitHub Login: @JasonGerend
• Microsoft Alias: jgerend

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!