Documentation of AzureCLI@3 missing features

[jikuja]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

AzureCLI@3

Breaking task version

No response

Last working task version

No response

Regression Description

Documentation of AzureCLI@3 missing features that are available on task code and are present on AzureCLI@2 documentation:

Task READMEs

Those files do not mention workload identity federation at all.

AzureCLI@3:

azure-pipelines-tasks/Tasks/AzureCLIV3/Readme.md

Lines 54 to 59 in 958ebec

	* **Access service principal details in script**: Select this check box if you want to add service principal id , service principal key and tenantId of the Azure endpoint to the script's execution environment. You can use variables: `servicePrincipalId`, `servicePrincipalKey` and `tenantId` in your script. This is honored only when the Azure endpoint has Service Principal authentication scheme. \
	\
	Syntax to access environment variables based on script type.\
	*Powershell script:* `$env:servicePrincipalId`\
	*Batch script:* `%servicePrincipalId%` \
	*Shell script:* `$servicePrincipalId`

AzureCLI@2

azure-pipelines-tasks/Tasks/AzureCLIV2/Readme.md

Lines 47 to 52 in 958ebec

	* **Access service principal details in script**: Select this check box if you want to add service principal id , service principal key and tenantId of the Azure endpoint to the script's execution environment. You can use variables: `servicePrincipalId`, `servicePrincipalKey` and `tenantId` in your script. This is honored only when the Azure endpoint has Service Principal authentication scheme. \
	\
	Syntax to access environment variables based on script type.\
	*Powershell script:* `$env:servicePrincipalId`\
	*Batch script:* `%servicePrincipalId%` \
	*Shell script:* `$servicePrincipalId`

Learn documentation:

AzureCLI@2:

https://github.com/MicrosoftDocs/azure-devops-yaml-schema/blob/c152b5f93eec37731c1617a13160abe4b91e6c78/task-reference/azure-cli-v2.md?plain=1#L182-L192

• addSpnToEnvironment docs tells that client_assertion is available on environment variable

AzureCLI@3:

https://github.com/MicrosoftDocs/azure-devops-yaml-schema/blob/c152b5f93eec37731c1617a13160abe4b91e6c78/task-reference/azure-cli-v3.md?plain=1#L184-L197

• addSpnToEnvironment docs does not mention WIF at all

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Relevant log output

-

Full task logs with system.debug enabled

Repro steps

-