[Question]: Does AzurePowerShell@5 support federated workload identities?

[YousefImran]

Task name

Azure PowerShell

Task version

5

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

Windows Server 2022

Question

I am questioning the possibility of a:
1. Bug
2. Or insufficient documentation.

**The problem**: I switched to using federated workload identities for Azure Resources service connections in my Azure DevOps instance (online services). Since then, this task has been failing with the following **error**:

`Exception calling ".ctor" with "3" argument(s): "Method not found: 'Newtonsoft. Json. JsonSerializerSettings System. Net. Http. Formatting. BaseJsonMediaTypeFormatter.getSerializerSettings()'."`

Doing some research, it was mentioned that `AzureCopy@v5` (as another task example) (in the task's official documentation) does not support federated workload identities and people who received the same error on `AzureCopy@v5` was due to that lack of support for federated identities. However, AzurePowerShell@v5 doesn't mention anything of the sort but it seems to be similar problem. The **challenge** here is that we have been getting banner messages from Microsoft pushing towards using Azure federated workload identities, but we've been unlucky so far due to this issue and I'd like to get clarifications:
1. Is it a bug?
2. Or does AzurePowerShell@v5 does not support federated workload identities?

[YousefImran]

The issue seems to be related to an old Az module version on the build machine. I have used another build machine with latest Az version and used the same inline verification PowerShell Core script on an AzurePowerShell@5 task and did not encounter this error.
I don't know which Az module version will trigger this error, but I hope this help.
Closing on that basis.