Answer accepted by question author
Hi @Divesh Harisinghani
Thankyou for reaching microsoft Q&A!
The Azure Synapse workspace pln-ppe-ds-syn-wus2 entered a Failed provisioning state after a workspace write operation did not complete successfully. As a result, subsequent ARM/Bicep update attempts were blocked with validation errors indicating that the workspace was in a non-terminal failed state. Existing PPE artifacts within the workspace needed to be preserved, and workspace deletion was not a viable option.
The issue was caused by a backend control-plane provisioning failure during a workspace update operation. Internal provisioning workflows encountered service-side orchestration and resource configuration errors, preventing the workspace from reaching a terminal provisioning state. Consequently, the workspace remained stuck in a failed state and could not accept further update operations.
The backend engineering team performed a control-plane recovery and state repair on the existing workspace. The failed provisioning state was cleared without deleting the workspace or impacting existing artifacts. Following the recovery, the workspace provisioning state returned to a healthy condition.
The workspace is now writable again, and ARM/Bicep deployment operations can proceed successfully. Existing workspace resources and PPE artifacts were preserved throughout the recovery process.