Skip to content

[Question]: AzureFileCopyV1-V5 Support for workload identity federation #19114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 of 4 tasks
fontexD opened this issue Oct 16, 2023 · 6 comments
Closed
1 of 4 tasks

Comments

@fontexD
Copy link

fontexD commented Oct 16, 2023

Task name

workload identity federation support for filecopy to blob

Task version

1.0

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 10

Question

when we try to update our authentication with workload identity federation we get the error the error its not supported , is there any work on this or any workaround so we can move away from service-princicals ? into using workload identity federation
@v-mohithgc
Copy link
Contributor

Hi thanks for reporting! We are working on more prioritized issues at the moment, but will get back to this one soon.

@alexvanderberkel
Copy link

Hi guys,

is there any progress on this issue? Microsoft is advertising to migrate over to workload identities but should also support all pipelines tasks. An update on this task would be good to have. Thanks.

@cyclelabs-ryanberger
Copy link

Hi all, any update on this? We are also facing this issue and are going to have to resort back to using a service principal (secret) for AzureFileCopy tasks in ADO pipelines. Thanks!

@m-soltani
Copy link

I would like to stress the importance of having this feature implemented. We have the same situation as @ryanberger-az mentioned above.

@ffloimair
Copy link

WTH. Once again Microsoft is urging customers to move to Workload Identity federation only for the customer to find out that they are not prepared. How can it be that this task has not got any attention 5 months after it has been reported?
Sorry guys but this is unprofessional behavior.

@v-mohithgc
Copy link
Contributor

The AzureFileCopyV6 task resolves this issue. It also uses Azure RBAC to access blob storage instead. This requires the identity of the service connection used to have the appropriate RBAC role e.g. Storage Blob Data Contributor. See Assign an Azure role for access to blob data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants