[Doc]: Connect-AzAccount Parameter Sets Cannot Describe the Functions and Usages Properly

[msJinLei]

Type of issue

Other (describe below)

Feedback

Currently the parameter sets of Connect-AzAccount don't describe the usages and functions

For example

• In the default parameter set "UserWithSubscriptionId (Default)", subscription is optional and so why it is named as "WithSubscriptionId"? Further, UserWithCredential is also a user flow and with subscription .
• For the parameter sets ServicePrincipalWithSubscriptionId, ServicePrincipalCertificateWithSubscriptionId, ServicePrincipalCertificateFileWithSubscriptionId and AccessTokenWithSubscriptionId, what's the meaning for "WithSubscriptionId" as the "subscripiton" is optional for all the parameter sets?

Page URL

No response

Content source URL

https://github.com/Azure/azure-powershell/blob/main/src/Accounts/Accounts/help/Connect-AzAccount.md

Author

No response

Document Id

No response

[isra-fel]

Name of parameter sets is not exposed to cx. This is not urgent.

[msJinLei]

Name of parameter sets is not exposed to cx. This is not urgent.

@isra-fel Not just name. I propose to separate device code flow from "UserWithSubscriptionId" and merge "ServicePrincipalCertificateFileWithSubscriptionId" and "ServicePrincipalCertificateWithSubscriptionId"

[isra-fel]

Yes it probably makes sense to seperate the parameter sets according to auth flows, as it's more intuitive for users and developers - but we need to be careful not to cause breaking changes.