Release pipeline failed after clone

(1) Share

Report

Posted on by Jan M.

3,301

After cloning a release pipeline there is a permission issue. The pipeline uploads the package to LCS and sets LCSAssetId for deployment a the second stage. Upload works fine.

On task Set LCSAssetId there is the error: Access denied: User xx does not have manage releases permission. This happens on the invoke method: $updatedef = Invoke-RestMethod -Uri $url -Method Put -Body $json -ContentType "application/json" -Headers @{Authorization = "Bearer $env:SYSTEM_ACCESSTOKEN”}.

Change pipeline permission to Allow (from Allow inherit) of edit/mange release, but doesn't help. Any idea where the permission must be set? Should clone not just copy all?

Thanks for help.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

Sagar121 1,151 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

You can check LCS connection. Check if the new pipeline have same LCS connection.

Was this reply helpful? Yes No
Jan M. 3,301 on at

Like (0)

Report
Copy link

Link copied!

LCS connection is fine, as the update task to LCS works well.

Was this reply helpful? Yes No
Verified answer

Jan M. 3,301 on at

Like (1)

Report
Copy link

Link copied!

Solution: Release Pipeline Security - Project Collection Build Service - Mange releases > Allow

This permission was not copied by cloning.

1 people found this reply helpful.

Was this reply helpful? Yes No