[GH-ISSUE #3665] [Bug]: ZipDeploy Fails on Azure #1620

Closed
opened 2026-03-02 13:45:41 +03:00 by kerem · 5 comments
Owner

Originally created by @TetraAsh on GitHub (Feb 18, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3665

Required confirmations before submitting

  • I can reproduce this issue on the latest released versions of both CIPP and CIPP-API.
  • I have searched existing issues (both open and closed) to avoid duplicates.
  • I am not requesting general support; this is an actual bug report.

Issue Description

When deploying the templates they fail due to ZipDeploy ending in a conflict state
{
"code": "ResourceDeploymentFailure",
"target": "/subscriptions/xxxxxxxxxxxxxxxxxxxx/resourceGroups/CIPP/providers/Microsoft.Web/sites/cippeq7rt/extensions/ZipDeploy",
"message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
}

Deploying to Resource group in UK South.

Environment Type

Non-sponsored user

Front End Version

latest, cannot view due to deployment failure

Back End Version

latest, cannot view due to deployment failure

Relevant Logs / Stack Trace


Originally created by @TetraAsh on GitHub (Feb 18, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3665 ### Required confirmations before submitting - [x] **I can reproduce this issue on the latest released versions** of both CIPP and CIPP-API. - [x] **I have searched existing issues** (both open and closed) to avoid duplicates. - [x] I am **not** requesting general support; this is an actual bug report. ### Issue Description When deploying the templates they fail due to ZipDeploy ending in a conflict state { "code": "ResourceDeploymentFailure", "target": "/subscriptions/xxxxxxxxxxxxxxxxxxxx/resourceGroups/CIPP/providers/Microsoft.Web/sites/cippeq7rt/extensions/ZipDeploy", "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'." } Deploying to Resource group in UK South. ### Environment Type Non-sponsored user ### Front End Version latest, cannot view due to deployment failure ### Back End Version latest, cannot view due to deployment failure ### Relevant Logs / Stack Trace ```plaintext ```
kerem 2026-03-02 13:45:41 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 18, 2025):

Thank you for reporting a potential bug. If you would like to work on this bug, please comment:

I would like to work on this please!

Thank you for helping us maintain the project!

<!-- gh-comment-id:2665654898 --> @github-actions[bot] commented on GitHub (Feb 18, 2025): Thank you for reporting a potential bug. If you would like to work on this bug, please comment: > I would like to work on this please! Thank you for helping us maintain the project!
Author
Owner

@TetraAsh commented on GitHub (Feb 18, 2025):

Writing this out made me think, I set the resource group to West Europe and it worked first time.
Leaving this for future installers

<!-- gh-comment-id:2665668375 --> @TetraAsh commented on GitHub (Feb 18, 2025): Writing this out made me think, I set the resource group to West Europe and it worked first time. Leaving this for future installers
Author
Owner

@Kieran-staffs-tech commented on GitHub (Mar 12, 2025):

Getting the same issue in my deploy. Also using West Europe as the resource group. Unsure if you was able to resolve this or if you just deployed from scratch again? @TetraAsh

<!-- gh-comment-id:2718580640 --> @Kieran-staffs-tech commented on GitHub (Mar 12, 2025): Getting the same issue in my deploy. Also using West Europe as the resource group. Unsure if you was able to resolve this or if you just deployed from scratch again? @TetraAsh
Author
Owner

@xylphe commented on GitHub (Dec 3, 2025):

Same problem when deploying in Western Europe. Persists even after complete reinstallation.

<!-- gh-comment-id:3606108972 --> @xylphe commented on GitHub (Dec 3, 2025): Same problem when deploying in Western Europe. Persists even after complete reinstallation.
Author
Owner

@Paulusbremmer commented on GitHub (Jan 14, 2026):

I was having the same issue, downloaded the release from https://cippreleases.blob.core.windows.net/cipp-api/latest.zip and added it to my cloned github repo. Replaced the https://cippreleases.blob.core.windows.net/cipp-api/latest.zip zip with the location of the raw zip file on Github.

<!-- gh-comment-id:3748434020 --> @Paulusbremmer commented on GitHub (Jan 14, 2026): I was having the same issue, downloaded the release from https://cippreleases.blob.core.windows.net/cipp-api/latest.zip and added it to my cloned github repo. Replaced the https://cippreleases.blob.core.windows.net/cipp-api/latest.zip zip with the location of the raw zip file on Github.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#1620
No description provided.