AMR accessPolicyAssignment stuck in 'Updating' state indefinitely — DELETE also rejected with Conflict

A single Microsoft.Cache/redisEnterprise/databases/accessPolicyAssignments resource has been frozen in provisioningState=Updating for >4 hours with no progress. All control-plane operations (PUT, DELETE) against this single resource are rejected with Conflict: Cannot perform another operation on the assignment if the Provisioning State is Updating. The parent cluster and database are healthy. Requesting state-machine reset on the affected resource.

Symptoms

• GET on the resource returns provisioningState: Updating. State has not changed across 5+ polls over ~4 hours.
• PUT (idempotent re-apply of same desired state): HTTP 409 Conflict, message above
• DELETE: HTTP 409 Conflict, message above (cannot even remove the resource to recreate it)
• Cluster and database remain Succeeded/Running; all other operations succeed normally
• ResourceHealth for the cluster: Available — "There aren't any known Azure platform problems affecting this Redis instance"

Timeline (UTC)

WhenEventMay 28, 15:30 / 19:26 / 19:29Successful APA writes (~15-17 s each)May 29, 21:02Successful APA write — last green operation(no Microsoft-initiated operations visible in activity log)Jun 01, 07:42****First Conflict failure — APA enters stuck UpdatingJun 01, 08:18 / 09:53 / 09:58 / 10:02 / 10:415 subsequent attempts (PUT and DELETE), all Conflict, immediate rejection without Accepted eventJun 01, 11:43 (ticket time)Still Updating, no change ### Correlation / Request IDs (most recent rejections) OperationTime (UTC)CorrelationIDRequestIDPUT (pipeline attempt 1)Jun 01 09:53:16bd5b22a0-f91f-44cb-a055-3f857956dcb5``255c6818-6f21-44f3-b824-b5d10cef4845PUT (pipeline attempt 2)Jun 01 09:58:0410e0d067-fe33-4c09-814f-d92e3923290a``bae27327-4d21-4ca1-a016-aa797d0f2140PUT (pipeline attempt 3)Jun 01 10:02:16d1ff56a5-5966-4790-941a-96fc4033fc36``5bbc6c7a-738e-452a-ace8-601153948176DELETE (manual recovery attempt)Jun 01 10:41:489ae1ca96-8b45-4416-8e44-796b7cbd7ad7``a4e7717e-3f96-4039-b03d-2f4f39fb970eAll return the same error: Cannot perform another operation on the assignment if the Provisioning State is Updating. All CLI or REST operations return Conflict errors:

Conflict({
  "error": {
    "code": "Conflict",
    "message": "Cannot perform another operation on the assignment if the Provisioning State is Updating CorrelationID=9ae1ca96-8b45-4416-8e44-796b7cbd7ad7 RequestID=a4e7717e-3f96-4039-b03d-2f4f39fb970e Timestamp=06/01/2026 10:41:48 (UTC)",
    "target": null
  }
})